You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If the first storage cell has the max type of items, if you feed an item that is not among those types into it, it will void it.
To Reproduce
Steps to reproduce the behavior:
Drive Slot 1's drive has max types filled, but item space to spare
(Optional) Have any additional drives that spare room for types and items
Hook a hopper up to the side of the Terminal
Feed a new item that doesn't appear in the first drive's storage.
Item is permanently gone.
Expected behavior
Hoppers shouldn't feed items into the terminal if it detects if Max Types nor Max Items is met by what they contain.
Errors
No errors in the console
Versions
MC: 1.19.3
PaperMC: 445
Java: Unknown, host (Bisect) doesn't provide any info.
Additional context
This was discovered with a 64k drive.
Unable to test it since this is on an active server, but we have modified the hopper settings to be more friendly to the server from the antics of our crazed builders. I do not know if this modification to the spigot.yml config is related to it. But even if it is, this kind of change should be accounted for by plugin makers.
Those settings:
The text was updated successfully, but these errors were encountered:
Describe the bug
If the first storage cell has the max type of items, if you feed an item that is not among those types into it, it will void it.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Hoppers shouldn't feed items into the terminal if it detects if Max Types nor Max Items is met by what they contain.
Errors
No errors in the console
Versions
MC: 1.19.3
PaperMC: 445
Java: Unknown, host (Bisect) doesn't provide any info.
Additional context
This was discovered with a 64k drive.
Unable to test it since this is on an active server, but we have modified the hopper settings to be more friendly to the server from the antics of our crazed builders. I do not know if this modification to the spigot.yml config is related to it. But even if it is, this kind of change should be accounted for by plugin makers.
Those settings:
The text was updated successfully, but these errors were encountered: