[MCPE-14233] Redstone components update upon reloading a world Created: 25/Apr/16  Updated: 25/Oct/16  Resolved: 25/Oct/16

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.15.0 Realms Alpha build 2, 0.15.0 Beta build 1, 0.15.0 Beta build 3, 0.15.6, 0.15.10, 0.15.90.8
Fix Version/s: None

Type: Bug
Reporter: Tavish McEwen
Resolution: Duplicate Votes: 3
Labels: redstone, redstone-update, world-loading

Issue Links:
Duplicate
duplicates MCPE-13608 Redstone components update when world... Resolved
Relates
relates to MCPE-13714 When opening a world, redstone takes ... Resolved
relates to MCPE-15779 Redstone does not load chunks Resolved
Game Mode: Creative
Confirmation Status: Confirmed
Platform: Phone - Android - LG Other (Specify in description)
CHK:

 Description   

Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causeing it to turn off when it should be being powered by something in the unloaded chunk next to it. To reproduce: make a long line of Redstone with repeaters, power
one end, then stand at the other end and lower your render distance. Then reload the world. The redstone will turn off, then turn back on as you load the component powering it. This affects all redstone components that I am aware of, including pistons. It tends to break contraptions as one half may update while the other is unloaded, often sending redstone contraptions into a clock.



 Comments   
Comment by Zeb [ 10/Oct/16 ]

Affects 0.15.90.8 (0.16.0 beta build 5). Again, shouldn't this issue be closed since it is a duplicate of MCPE-13608?

Comment by Tavish McEwen [ 26/Sep/16 ]

Yes

Comment by Zeb [ 30/Aug/16 ]

Isn't this a duplicate of (or at least related to) MCPE-13608?

Comment by Tavish McEwen [ 12/Aug/16 ]

Confirmed for 0.15.6

Comment by Tavish McEwen [ 11/Aug/16 ]

The main issue (things breaking because they are partly unloaded while one part updates) would probably be fixed if MCPE-15779 (redstone not loading chunks) was fixed, but this "feature" doesn't really help anything and should be removed anyways.

Comment by Azelef [ 10/Aug/16 ]

Confirmed in 0.15.4, please reopen.

Comment by AMAN4700 [ 08/Aug/16 ]

Please respond and add the current version if you can reproduce this issue.

Comment by Azelef [ 15/Jun/16 ]

Can confirm it affects pistons in 0.15.1 beta 1. The flying machine in MCPE-15475 and MCPE-15476 goes one block forward when reloaded.

Comment by Tavish McEwen [ 04/Jun/16 ]

Confirmed for 0.15 b1

Comment by PHO [ 27/Apr/16 ]

Ah, I see. The root cause of the problem is that the powered state of redstone components (like repeaters and comparators) is not saved when they are unloaded, i.e. they completely forget the fact that they were powered before getting unloaded. When they are loaded again, all the components in that chunk receive redstone updates to recover their previous state... with a fatal delay that completely messes up any non-trivial redstone circuitries. So yes, this is indeed a partial duplicate of MCPE-13714 which is a general case of MCPE-13270 and MCPE-13413.

Comment by Luis Robles [ 26/Apr/16 ]

Maybe a Duplicate of MCPE-13714

Comment by Tavish McEwen [ 26/Apr/16 ]

No, it just has to not give them a block update. Then they won't change because they don't check if they are being powered, and there is even less lag upon loading a world. This bug does not occur in PC edition.

Comment by PHO [ 26/Apr/16 ]

This is very likely to be an intended behavior, because in order to "fix" this, the game must load each and every chunk of the world upon reloading, and continue processing all those redstone components no matter how far you are away from them. I don't think this is feasible.

Generated at Sat Jan 11 15:02:57 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.