When running a redstone wire outside out of loaded chunks, the signal fails to propagate.
Expected Behaviour: Redstone propagates through unloaded chunks as it has always done and returns after a bit of repeater delay.
Actual Behaviour: Redstone propagates until the chunk-loading boundary and stops there. (See image, in one imagine you can see the whole "circuit", in the other one you can see that the lever is flicked but despite waiting a while, the signal fails to return and ends where the chunk-loading boundary is. In the 3rd image you can see the area of interest zoomed in with optifine.)
I'm not sure if this is intended behaviour, but even if this is not a bug, please change it back as it was normal behaviour before the 1.14 update and not "technically undefined behaviour" and many builds rely on this mechanic.
EDIT: All these images were taken on a "vanilla" server and vanilla client with a server render distance of 10 chunks. However, the last picture was taken (again on a vanilla server) with an OptiFine client for zooming functionality reasons.
Linked issues
Attachments
Comments 6
Tryashtar, I added the world. For some reason, you spawn in under the world. The circuitry is located at around [X: 187 Y: 56 Z: -697].
I don't know the exact version this stopped working, I suppose it's 1.14 because the last time I built some redstone business was in 1.13.2 and everything worked fine there. I have not tested this world in 1.13.2, though.
Don't mind the world, I am building a Redstone Computer with a friend and that's how I stumbled across the buggy❓ redstone mechanism.
EDIT: Also, this world was created on a spigot server but then I verified that this bug happens on a vanilla server too. Also, I looked up the issue and found numerous confirmations on gaming.stackexchange.com and reddit.com of other people experiencing similar problems:
https://gaming.stackexchange.com/questions/351561/what-are-the-rules-range-for-chunk-loading-in-single-player (
In 1.14 it doesn't load chunks anymore - but does pretty much what I stated in the linked question: follows along as chunks are loaded by the player. – SF. May 21 at 0:09)
https://www.reddit.com/r/redstone/comments/cc06u1/chunk_loading_wires/
https://www.reddit.com/r/redstone/comments/bkw784/114_chunk_loader/
https://www.reddit.com/r/technicalminecraft/comments/bqv5pu/1132_chunkloading_through_redstone_signal/ (See "update" comment from sharfpang)
This is the old behaviour: https://www.reddit.com/r/Minecraft/comments/8rg0cc/when_redstone_is_carried_into_an_unloaded_chunk/
from my testing, it also affects 1.19. i tried to make a chunk auto save detector, and it didnt work. i also tried to update an unloaded chunk with the the signal that is produced by two observers, in a loaded chunk, facing each other, but the new chunk didnt load. edit: everything was done in vanilla singleplayer
Can you please attach the world you used to test this? And in which version did it stop working exactly?