Tin Svagelj
Assigned
Reported
Comments
Can confirm this bug is still present in latest version of the game. @karstvgl gave correct steps to replicate this bug. It should be fixed now considering it can be caused from within the game. @Dinnerbone said no before because it was caused by third party tools, now it is caused by Minecraft commands. Anyone not seeing this is a bug is an oblivious fool (unless someone from Mojang says they don't consider it a bug). I don't see what mods are doing with this?! When this issue was said to be invalid it was because third party tools were used to create it, now it's a very valid issue - code shouldn't break like this. An AI would be doing a better job at keeping track of bugs than mods here (apparently). This is not a hateful comment, it is merely constructive criticism.
Actually, this is /fill command not doing its job right. Fill command doesn't destroy old tile entities, just their blocks and since MC has custom renderers for some tile entities, old renderer remains.
As old tile entity remains in the same place and when placing another you create a new one, you end up with two tile entities in the same place and a new block which actually opens new GUI.
This is /fill and similar commands not (re)moving tile entities as they are supposed to.
Also, the reason this glitch resets after restarting the world is because Minecraft tries to validate tile entities when they load and see if their block is still there (which fill doesn't) and destroys them if their block doesn't exist.
It is weird however that /fill does work below 63. This is probably another bug that has to do with chunk update inconsistencies.
Bug still occurring in version 1.8.7!
@Dinnerbone
This should be considered a bug. You can access this feature within the game without using third party programs and it causes a crash.
Is it really such a problem to extend an array to prevent crashing?
It is a bug, maps don't keep their names after player spends experience renaming them. Furnaces keep their names, enchanting tables keep their names, chests keep their names, but maps don't. This is a bug. It is also one of those 1-minute-fix bugs.
I don't see why this shouldn't be fixed?!
Actually fixing the game crashing and not working as it should (either prevent GUI from opening or fix the inventory array size).
Map making.
Could be added to Vanilla (but regular horses would have much smaller storage)
I believe those three reasons are enough. This isn't a hard-to-fix problem, it's just a single number or if statement.