Simple Storage Network

Simple Storage Network

Mods
57M Downloads

Priority System Fails when Chest Overflows

deadlypandaghost opened this issue · 2 comments

commented

Minecraft Version: 1,18.2

Forge Version: 40.1.93

Mod Version: SimpleStorageNetwork-1.18.2-1.6.2.jar

Single Player or Server: Server

Describe problem (what you were doing; what happened; what should have happened): Playing vault hunters for 1.18.2. Using SSN connected to 2 containers with different priority. When the higher priority container overflows, then is emptied, it will be treated as lower priority until priorities are reset.

Steps to Reproduce

  1. Have SSN connected to 2+ output chests with different priority filtered link cables
  2. Input items until higher priority chest is filled. Then add 1 more stack.
  3. Remove items from higher priority chest.
  4. Add items in storage network. Note items not added to high priority chest.

Log file link:

Video/images/gifs (direct upload or link):

commented

I'm experience something similar in combination with Storage Drawers. I'm playing the Techopolis 2 pack.

Minecraft: 1.19.2
Forge: 43.3.2
Mod: 1.9.2-1.6.4

It seems to send items first to a chest instead of the Storage Drawer Controller. Also, when I first login back to the game, it will starts to fill the only chest I have available in the network and it either has to go full or I need to change the order on the link cable. It's a bit annoying as this is an action I need to manually do with each login.

Other than that, I like the mod. 👍🏻 Great starter network before AE2 og RS is available.

commented

I believe what I am experiencing is a variation on this same bug.

MC Version: 1.19.2
Forge Version: 43.3.2
Mod Version: 1.7.0
Single Player

My observation of the bug make it appear as if the behavior is this: when an item enters the network, a destination container is chosen for that item type and stored in memory. If a new container is added to the network with a higher priority (lower priority value), the network does not check priority for the item until some change has been made to its current destination container, either the priority value is updated or the container becomes unavailable (full, or broken/moved). The item-container priority table should probably be invalidated on container addition to the network as well.