Redstone elements that are in a chunk that is very far away behave strangely when toggled on or off while the chunk containing those elements is not loaded.
See this video for more details: http://www.youtube.com/watch?v=e_MM97ifASw
Just for clarification: I do know that no game elements will be updated in unloaded chunks. I do know that - by default - only the chunks in a radius of 10 chunks around a player are usually loaded. However, the video will show that something about my last two statements cannot be right.
Related issues
Comments
migrated
migrated
As far as I can tell, this is NOT a duplicate of MC-3259. Usually the redstone signal propagation should come to a complete stop at the chunk border. However, in this case the redstone signal seems to propagate "a bit" into the unloaded chunk (to be precise: to the half of the chunk). And that makes this a completely new problem since a forced block update on the chunk border (e.g. via an everlooping Minecart and a detection rail) won't make the redstone cable work properly again as they used to.
Could someone therefore please reopen this issue?
migrated
Added your video to the description of MC-3259.
Duplicate of MC-3259.