Functional Storage

Functional Storage

25M Downloads

[1.20.1] Storage Drawers not holding (some) Mob-drops to capacity with upgrades

Nick-77ab2 opened this issue · 3 comments

commented

DO NOT REPORT AN ISSUE IF YOU HAVEN'T TESTED THE ISSUE WITH THE LATEST VERSION IN CURSEFORGE

Functional Storage Version: 1.2.3 (Issue not in the 1.2.4 changelog) also 1.2.4 (checked in solo world)

Titanium Version: 3.8.22

Crashlog If Applicable (Upload to pastebin/gist):

Cannot place any more slimeballs in any 1x1 or 2x2 drawer past numbers around this amount (some 2x2's stop around 700, some around 900). Not sure what's going on but I'm pretty sure this isn't intended.

I checked with cobblestone and it seems fine, just weirdly slimeballs. Same occurs with spidereyes after checking. The issue might be mob-drop related.

Edit: Rotten flesh is fine, so are eggs. After waiting a bit I got one of the drawers to accept more slimeballs, and then it went back to the state of not accepting any more. This seems to actually be on some sort of cycle. I've even got one stuck at 64 slimeballs and i cannot place more in until the "cycle" goes back to allowing me to place them there.

Screenshot_1567
Screenshot_1568
Screenshot_1569

commented

Are the items in the drawers or the ones you trying to insert have random nbt?

I don't believe they do, I haven't messed with the slimeballs. The same slimeballs that couldn't be placed into a drawer at one point could be at a later point, again only up to a certain value before it stopped allowing more to be placed in. (same with the spidereyes)

commented

Are the items in the drawers or the ones you trying to insert have random nbt?

commented

@

Are the items in the drawers or the ones you trying to insert have random nbt?

Checking more into this, yes something is adding an nbt tag to these items. They
stacked in the AE storage system i had setup and apparently pulled out first. After looking through the tags both in my server and on a test world (forgot about f3+h) and checking the data I resulted in this:
Server, slimeballs with issues:
!1

local test slimeballs no issues:
!2

Problematic nbt tag:
Screenshot_1578

So yes you were right. Just manually removing the tagged slimeballs now 🥲