MC-8340Comparators do not update their state when blocking or unblocking a chest with a block on top
I found this bug where comparators dont output any signal from a chest, when the chest has a block on top. I'm not sure if it's intended, but I thought I might as well post it. It allows for a cool clock like in the third screenshot, However the clock creates major lag spikes on servers after 1 minute or so, more lag than it should.
Since I don't seem to be able to upload screenshots, I uploaded them to imgur:
http://imgur.com/advoWtp
http://imgur.com/Fyh17O0
http://imgur.com/9q6GdZb
Linked Issues
is duplicated by2
Normal
Low
Created Issue:
Comparators do not output any signal from chests when chest has a block on top
Environment
Mac OSX - Snow Leopard - 32bit
I found this bug where comparators dont output any signal from a chest, when the chest has a block on top. I'm not sure if it's intended, but I thought I might as well post it. It allows for a cool clock like in the third screenshot, However the clock creates major lag spikes on servers after 1 minute or so, more lag than it should.
I found this bug where comparators dont output any signal from a chest, when the chest has a block on top. I'm not sure if it's intended, but I thought I might as well post it. It allows for a cool clock like in the third screenshot, However the clock creates major lag spikes on servers after 1 minute or so, more lag than it should.
I found this bug where comparators dont output any signal from a chest, when the chest has a block on top. I'm not sure if it's intended, but I thought I might as well post it. It allows for a cool clock like in the third screenshot, However the clock creates major lag spikes on servers after 1 minute or so, more lag than it should.
Since I don't seem to be able to upload screenshots, I uploaded them to imgur:
http://imgur.com/advoWtp
http://imgur.com/Fyh17O0
http://imgur.com/9q6GdZb
This issue has not been fixed as of 13w07a. The screenshot from 05/Feb/13 might show that the comparator has not updated. My set-up is shown in two new pictures. The chest is half-full so the comparator should be lit-
which it is when the chest is not blocked from opening. Next I place a block above the chest and the comparator remains on. But if I force the comparator to update by momentarily applying a signal to it's side the lights go off and stay off. When I remove the block above the chest the comparator output remains off until I either push the button again or simply open and close the chest-then the comparator lights up again. Because of the long redstone path, pushing the button when the chest is not blocked makes no difference because the low signal strength from the button is less than the signal from the half-full chest. Pushing the button only serves to force the comparator to update.
The block above the chest prevents the comparator from reporting that it is not empty.
This issue has not been fixed as of 13w07a. The screenshot from 05/Feb/13 might show that the comparator has not updated. My set-up is shown in two new pictures. The chest is half-full so the comparator should be lit-
which it is when the chest is not blocked from opening. Next I place a block above the chest and the comparator remains on. But if I force the comparator to update by momentarily applying a signal to it's side the lights go off and stay off. When I remove the block above the chest the comparator output remains off until I either push the button again or simply open and close the chest-then the comparator lights up again. Because of the long redstone path, pushing the button when the chest is not blocked makes no difference because the low signal strength from the button is less than the signal from the half-full chest. Pushing the button only serves to force the comparator to update.
This issue has not been fixed as of 13w07a. My set-up is shown in two new pictures. The chest is half-full so the comparator should be lit-
which it is when the chest is not blocked from opening. Next I place a block above the chest and the comparator remains on. But if I force the comparator to update by momentarily applying a signal to it's side the lights go off and stay off. When I remove the block above the chest the comparator output remains off until I either push the button again or simply open and close the chest-then the comparator lights up again. Because of the long redstone path, pushing the button when the chest is not blocked makes no difference because the low signal strength from the button is less than the signal from the half-full chest. Pushing the button only serves to force the comparator to update. (The screenshot from 05/Feb/13 makes it appear that the problem was fixed but it might simply be that the comparator has not updated.)
Comparators do notoutput any signal from chests whenchesthasa block ontopComparators do not update their state when blocking or unblocking a chest with a block ontop
relates to
relates to
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
relates to
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Mac OSX - Snow Leopard - 32bit
relates to
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
relates to
![[Helper] Jack McKalling](../../../data/avatars/users/92859.png){kind=small}
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
Comparators do not update their state when blocking or unblocking a chest with a block on top
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Can confirm in 1.20.4
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
is duplicated by
is duplicated by
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
Relates to MC-8340.
![[Mojang] Panda](../../../data/avatars/users/41658.png){kind=small}
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
This is already tracked in MC-8340
Thank you for your report!
We're tracking this issue in MC-8340, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Attached screenshots to issue.
thanks ^^
It seems like this has been fixed, see the new screenshot.
This issue has not been fixed as of 13w07a. My set-up is shown in two new pictures. The chest is half-full so the comparator should be lit, which it is when the chest is not blocked from opening. Next I place a block above the chest and the comparator remains on. But if I force the comparator to update by momentarily applying a signal to it's side the lights go off and stay off. When I remove the block above the chest the comparator output remains off until I either push the button again or simply open and close the chest; then the comparator lights up again. Because of the long redstone path, pushing the button when the chest is not blocked makes no difference because the low signal strength from the button is less than the signal from the half-full chest. Pushing the button only serves to force the comparator to update. (The screenshot from 05/Feb/13 makes it appear that the problem was fixed but it might simply be that the comparator has not updated.)
Confirmed to still occur on 13w07a with all block updates (not just redstone). Reopened.
Still occurring in 13w11a
This turned out to be a really useful 'bug' so how about not fixing it and resolving it as 'works as intended'
Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
This is still in 1.8.2-pre6, but fixing this bug would be very sad because lot of contraptions already made use of this
Please don't repeat the horrible mistake of
MC-108and leave this extremely glitchy behavior in the game just because a few people find it useful. Bugs should be fixed, not left in the game to confuse and irritate every player that tries to build something. There are already enough inconsistent behaviors in the game, as more and more start to accumulate, the game will eventually become unplayable. It's just not worth it.Is this now WAI because hoppers also can't interact with blocked chests?
Confirmed in 1.15.2 and 20w21a.
Still an issue in 1.16.1, items can go into a chest via hoppers when a block is on top, but items can't be detected inside a chest when a block is on top.
moosefreak, that is MC-100302.
Can confirm in 20w48a.