[MC-8670] Comparators Require Block Update after Chunk Unload Created: 29/Jan/13  Updated: 27/Mar/17  Resolved: 29/Jan/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w03a, Snapshot 13w04a
Fix Version/s: None

Type: Bug
Reporter: 'Patch' Miller Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MC-7771 Comparator not updating status after ... Resolved
Confirmation Status: Unconfirmed

 Description   

I've been using comparators to sense the inventory of hoppers to create a basic sorting system. Simple stuff. I've noticed, however, that if the chunk that the Comparator is in becomes unloaded, the comparator is frozen in its state and will not update if the amount of items in the inventory changes. It will only update when the comparator recieves a block update.

What I expected to happen was...:
When I came back to the chunk with the comparator, I expected that it would work without my having to update it.

What actually happened was...:
The comparator would not detect inventory changes unless it was updated.

Steps to Reproduce
1) Place a chest with a comparator coming out the back of it. Set up some redstone to indicate inventory level.
2) Place one item in the chest.
3) Leave the area and travel far enough away for the chunk to unload. Logging out and in will not cause the unload.
4) Remain outside the area for a few minutes, then return to the comparator.
5) Place several stacks of items in the chest. You will note that the comparator's signal does not update.
6) Place a block beside the comparator, causing an update. The comparator's signal strength will nwo correctly display.



 Comments   
Comment by Tails [ 29/Jan/13 ]

Duplicate of MC-7771, please use the search function to see if your bug has already been submitted. Currently over 50% of tickets are being closed as duplicate.

Comment by Tails [ 29/Jan/13 ]

Please do not mark unreleased versions as affected. You do not have access to this yet.

Generated at Sun Jan 12 12:18:33 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.