MC-37428Chest does not open when doubled. If placed singlely, its fine however. (Large chests do not work)
In the Linux version of Minecraft, when two chests are placed next to each other to create a large chest, the chest does not open when the use button is clicked. However, once a chest is taken away to make the other normal, that chest can be used once more to store things.
As a result, chests must be placed separately to work.
What I expected to happen was...:
The chest to open as a large chest when right clicked.
What actually happened w as...:
The chest did nothing when clicked.
Steps to Reproduce: (LINUX VERSION – 1.7.2)
1. Make 2 chests
2. ... Put them next to each other
3. ...Attempt to open it
Environment
Linux
Created Issue:
Chest does not open when doubled. If placed singlely, its fine however. (Large chests do not work)
In the Linux version of Minecraft, when two chests are placed next to each other to create a large chest, the chest does not open when the use button is clicked. However, once a chest is taken away to make the other normal, that chest can be used once more to store things.
As a result, chests must be placed separately to work.What I expected to happen was...:
The chest to open as a large chest when right clicked.What actually happened w as...:
The chest did nothing when clicked.Steps to Reproduce: (LINUX VERSION – 1.7.2)
1. Make 2 chests
2. ... Put them next to each other
3. ...Attempt to open itEnvironment
Linux
Cannot confirm.
Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report (minecraft/crash-reports/crash-<DATE>-client.txt) here.
Here is the crash report:
question for mods:
Why always attaching a crash report when the crash isn't caused by the bug? Where can you see a chest bug in a manual crash report? Do you just want to see if we didn't mod the .jar to filter bad issue entries?
No, to see your system specs, driver version, memory allocation etc. The "modded" flag comes piggybacked with the important information.
BTW: Your Java is outdated:
Gallium driver is not very stable, install AMD drivers instead:
For some reason, this bug now only happens some of the time, but if I moved the chest to a different location, it worked again (as a large chest).
Thanks for the help though!
It could maybe depends on 'f' value
Is this still a concern in the latest Minecraft version 14w02c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
It's all good now, no problems
Was there a block above the chest???