MC-8194Redstone signal propagates very strangely in unloaded chunks
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.
Linked Issues
Created Issue:
Redstone signal propagates very strangely in unloaded chunks
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.putlocker.com/file/0F3BA12F2AD4257F
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.
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.putlocker.com/file/0F3BA12F2AD4257F (Sorry for the ads; please click them away if you don't have an ad blocker.)
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.
duplicates
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
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.putlocker.com/file/0F3BA12F2AD4257F (Sorry for the ads; please click them away if you don't have an ad blocker.)
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.
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: [link removed] (Sorry for the ads; please click them away if you don't have an ad blocker.)
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.
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: [link removed] (Sorry for the ads; please click them away if you don't have an ad blocker.)
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.
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: [link removed] (Sorry for the ads; please click them away if you don't have an ad blocker.)
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.
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: [link removed] (Sorry for the ads; please click them away if you don't have an ad blocker.)
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.
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: [Will upload as an attachment in a few minutes.]
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.
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: [Will upload as an attachment in a few minutes.]
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.
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.
In the latest version (13w04a) the behavior is even stranger. I filed an issue as MC-8194 which seems to be related to this issue. (However, it's not an actual duplicate... a mod changed the status too quickly unfortunately. 
)
I did some more experiments concerncing this issue. I managed to create a pretty simple showcase where you can get some redstone components to get "stuck" easily:
Create a setup like in "chunk-middle-problem-01-basic-setup-repeaters.png". (Note: Make sure to build everything inside a single chunk - marking the edges helps!) Set the command block on the very right to teleport you very far away (at least 10 chunks). Set all other command blocks to trigger "say" commands as shown on the screenshot. Edit: Make sure that the random chunk where you build this is very far away from the spawn as the chunks around the spawn will constantly stay loaded. The problem won't appear there! Teleporting 10000 blocks away from the spawn should bring you far away enough for this.
Stand inside the chunk and then push the button. You'll notice that even though you were teleported away (which means that the teleportation command block must have got fired), not all command blocks in the chunk got fired. Only the "say" command blocks 1-7 were fired (as you can see on the chat window).
When returning to the chunk, you'll see something like in chunk-middle-problem-02-repeaters-behavior.png. All repeaters "behind the chunk's middle" got stuck - which explains why the command blocks were not fired. (Side note: I had actually discovered this chunk middle problem in a different context before and reported it in MC-8194. The teleportation issue is a new context and therefore another problem type though.)
You can also build other kinds of signal transmission methods as shown in the following screenshots - with similar strange effects. (Only the "wire only" transmission method seems to work. The shuffled command block firing order you encounter there might not be considered a real bug because all redstone wire elements could be expected to get fired at the very same time - which makes the firing order undefined and therefore allows a random order.)
Duplicate of
MC-3259.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?
Added your video to the description of
MC-3259.