Redstone components update when world is reloaded
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From MCPE-14233:
Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causing 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.
Steps to reproduce:
1. Create a flat creative world.
2. Place a lever, turn it on, and then place a long line redstone dust and repeaters extending far out some distance outside of chunk-loading range, and then make the wire do a u-turn and come back to the start. Make sure there are repeaters so that the signal can go all the way.
3. Exit the world and reload it.
4. Wait a little while, and you'll notice that the returning end of the wire will turn off, as the redstone updates and can't find a power source, since the connection between the start and end is unloaded, and also because of MCPE-15779. (Though even if that was fixed there might still be a moment where the dust becomes unpowered while the chunks are still being loaded.)
This effect can also sometimes be seen in cases where a piston is being powered by a source in another chunk, and the chunk with the piston loads first. This is more difficult to reproduce in a world, though.
Edit by PHO:
The second part of the original description is WAI: MCPE-15779.
The first part, redstone components being ticked upon loading chunks, is the real issue. It is probably a leftover from the past behavior: state of redstone components used to be forgotten upon unloading chunks, and in order to recover it the game ticked all of them on the chunk reload. Now their state seems to be correctly saved in the file so they need not to be ticked, and doing so also causes the very problem: components in unloaded chunks affect the entire contraption. To reproduce this,
- Open a world attached to
MCPE-15779. - Load all the chunks where the entire circuit resides in.
- Return to the point where the piston is placed.
- Close the world and open it again.
- Observe that the piston momentarily extends and then retracts. Ideally the piston and the line of dust should stay activated even though the middle part of the dust line is in unloaded chunks, because their last state (active) should be saved in the file and the game only needs to restore it.
Linked Issues
is duplicated by2
relates to8
MCPE-29548Relogging can cause observers to emit pulsesConfirmedMCPE-13270Comparators measuring a non-empty container momentarily stop emitting power upon reloadingFixedMCPE-13413Active unpowered locked repeaters become inactive after reloadingFixedMCPE-15779Redstone does not load chunksWorks As IntendedMCPE-17464Extended pistons retract for a second when the world is loaded.Cannot ReproduceMCPE-18570Schrodinger's SteveWorks As IntendedMCPE-179412Dispenser with bucket may fail to pick up water or lava if activated immediately before/after relogConfirmedMCPE-20159Active redstone signals are not restored properly on world loadCannot Reproduce
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Created Issue:
State of Redstone not saving after reload of world
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
Attachments1
is duplicated by
relates to
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
relates to
is duplicated by
relates to
relates to
State of Redstone not saving after reload of worldRedstone components update when world is reloaded
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From 14233:
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.
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From 14233:
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.In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From
MCPE-14233: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.
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From
MCPE-14233: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.In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From
MCPE-14233:Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causing 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.
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From
MCPE-14233:Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causing 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.
Steps to reproduce:
1. Create a flat creative world.
2. Place a lever, turn it on, and then place a long line redstone dust and repeaters extending far out some distance outside of chunk-loading range, and then make the wire do a u-turn and come back to the start. Make sure there are repeaters so that the signal can go all the way.
3. Exit the world and reload it.
4. Wait a little while, and you'll notice that the returning end of the wire will turn off, as the redstone updates and can't find a power source, since the connection between the start and end is unloaded, and also because
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From
MCPE-14233:Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causing 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.
Steps to reproduce:
1. Create a flat creative world.
2. Place a lever, turn it on, and then place a long line redstone dust and repeaters extending far out some distance outside of chunk-loading range, and then make the wire do a u-turn and come back to the start. Make sure there are repeaters so that the signal can go all the way.
3. Exit the world and reload it.
4. Wait a little while, and you'll notice that the returning end of the wire will turn off, as the redstone updates and can't find a power source, since the connection between the start and end is unloaded, and also because ofMCPE-15779. (Though even if that was fixed there might still be a moment where the dust becomes unpowered while the chunks are still being loaded.)This effect can also sometimes be seen in cases where a piston is being powered by a source in another chunk, and the chunk with the piston loads first. This is more difficult to reproduce in a world, though.
is duplicated by
relates to
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From
MCPE-14233:Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causing 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.
Steps to reproduce:
1. Create a flat creative world.
2. Place a lever, turn it on, and then place a long line redstone dust and repeaters extending far out some distance outside of chunk-loading range, and then make the wire do a u-turn and come back to the start. Make sure there are repeaters so that the signal can go all the way.
3. Exit the world and reload it.
4. Wait a little while, and you'll notice that the returning end of the wire will turn off, as the redstone updates and can't find a power source, since the connection between the start and end is unloaded, and also because ofMCPE-15779. (Though even if that was fixed there might still be a moment where the dust becomes unpowered while the chunks are still being loaded.)This effect can also sometimes be seen in cases where a piston is being powered by a source in another chunk, and the chunk with the piston loads first. This is more difficult to reproduce in a world, though.
Edit by PHO:
The second part of the original description is WAI:MCPE-15779.
The first part, redstone components being ticked upon loading chunks, is the real issue. It is probably a leftover from the past behavior: state of redstone components used to be forgotten upon unloading chunks, and in order to recover it the game ticked all of them on the chunk reload. Now their state seems to be correctly saved in the file so they need not to be ticked, and doing so also causes the very problem: components in unloaded chunks affect the entire contraption. To reproduce this,
- Open a world attached to
MCPE-15779.- Load all the chunks where the entire circuit resides in.
- Return to the point where the piston is placed.
- Close the world and open it again.
- Observe that the piston momentarily extends and then retracts. Ideally the piston and the line of dust should stay activated even though the middle part of the dust line is in unloaded chunks, because their last state (active) should be saved in the file and the game only needs to restore it.
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From
MCPE-14233:Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causing 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.
Steps to reproduce:
1. Create a flat creative world.
2. Place a lever, turn it on, and then place a long line redstone dust and repeaters extending far out some distance outside of chunk-loading range, and then make the wire do a u-turn and come back to the start. Make sure there are repeaters so that the signal can go all the way.
3. Exit the world and reload it.
4. Wait a little while, and you'll notice that the returning end of the wire will turn off, as the redstone updates and can't find a power source, since the connection between the start and end is unloaded, and also because ofMCPE-15779. (Though even if that was fixed there might still be a moment where the dust becomes unpowered while the chunks are still being loaded.)This effect can also sometimes be seen in cases where a piston is being powered by a source in another chunk, and the chunk with the piston loads first. This is more difficult to reproduce in a world, though.
Edit by
PHO:
The second part of the original description is WAI:MCPE-15779.
The first part, redstone components being ticked upon loading chunks, is the real issue. It is probably a leftover from the past behavior: state of redstone components used to be forgotten upon unloading chunks, and in order to recover it the game ticked all of them on the chunk reload. Now their state seems to be correctly saved in the file so they need not to be ticked, and doing so also causes the very problem: components in unloaded chunks affect the entire contraption. To reproduce this,
- Open a world attached to
MCPE-15779.- Load all the chunks where the entire circuit resides in.
- Return to the point where the piston is placed.
- Close the world and open it again.
- Observe that the piston momentarily extends and then retracts. Ideally the piston and the line of dust should stay activated even though the middle part of the dust line is in unloaded chunks, because their last state (active) should be saved in the file and the game only needs to restore it.
In my survival world, I have a lever that controls dispensers on a semi automatic wheat farm. The dispensers fire water buckets. I Have a circuit seen below which activates on the rising and falling action of the lever. When I am in the game, the circuit works as intended but if I relog the game (quit to title and join back) the dispenser will fire the bucket and stay in that state. I assume it is the Redstone torches that do not save state as I leave the game.
From
MCPE-14233:Upon loading a world, redstone components update. The redstone may change based on an unloaded chunk, causing 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.
Steps to reproduce:
1. Create a flat creative world.
2. Place a lever, turn it on, and then place a long line redstone dust and repeaters extending far out some distance outside of chunk-loading range, and then make the wire do a u-turn and come back to the start. Make sure there are repeaters so that the signal can go all the way.
3. Exit the world and reload it.
4. Wait a little while, and you'll notice that the returning end of the wire will turn off, as the redstone updates and can't find a power source, since the connection between the start and end is unloaded, and also because ofMCPE-15779. (Though even if that was fixed there might still be a moment where the dust becomes unpowered while the chunks are still being loaded.)This effect can also sometimes be seen in cases where a piston is being powered by a source in another chunk, and the chunk with the piston loads first. This is more difficult to reproduce in a world, though.
Edit by PHO:
The second part of the original description is WAI:MCPE-15779.
The first part, redstone components being ticked upon loading chunks, is the real issue. It is probably a leftover from the past behavior: state of redstone components used to be forgotten upon unloading chunks, and in order to recover it the game ticked all of them on the chunk reload. Now their state seems to be correctly saved in the file so they need not to be ticked, and doing so also causes the very problem: components in unloaded chunks affect the entire contraption. To reproduce this,
- Open a world attached to
MCPE-15779.- Load all the chunks where the entire circuit resides in.
- Return to the point where the piston is placed.
- Close the world and open it again.
- Observe that the piston momentarily extends and then retracts. Ideally the piston and the line of dust should stay activated even though the middle part of the dust line is in unloaded chunks, because their last state (active) should be saved in the file and the game only needs to restore it.
relates to
relates to
relates to
is duplicated by
relates to
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
relates to
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
Thank you for your report! However, this issue has already been reported as MCPE-13608. Consider doing a search next time, to check if a report on the issue you're submitting doesn't already exist.
Isn't this a duplicate of (or at least related to) MCPE-13608?
EDIT 2: I just tested, and when pistons get stuck, they act like solid/opaque blocks, meaning you can send a pulse through them and have a repeater pick up the signal on the other end, which doesn't normally happen! this means that this bug is actually the same thing as MCPE-17304! I think the mods should merge the 2 issues, since they are one and the same.
EDIT: Apparently this also affects droppers/dispensers as well. See: https://redd.it/55pbt1
So I tried to activate a random sticky piston in my world and it just wouldn't activate, even after giving it block updates, breaking the block above the piston that it was supposed to push, breaking and moving the lever that was supposed to power it, placing a redstone block next to it, and trying all sorts of ways to power it. After relogging, the piston started working again. I have no idea what caused this bug or how to reproduce it, but luckily I was smart enough to start recording when the bug happened. It happened again later on to the same piston, but I could never reproduce it consistently or with any other pistons in my world. Note that I never broke the piston that was behaving weirdly.
I'm sorry that this bug report is so vague, but I honestly have no idea why this happened or how to reproduce it. If anyone has any idea why this might have happened, please let me know... I haven't got a clue as to what would cause this to happen, other than improper world-loading, in which case this might be related to MCPE-13608 and/or MCPE-14233.
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?
Reopening... I have found out that this is in fact a separate issue from MCPE-13608.
Attached screenshot & test world from MCPE-19086.
This could be related to MCPE-13608 but I wasn't sure. Feel free to post the video under that bug if that makes tracking easier
I have an observer block that is observing a piece of powered Redstone. When I reload the world, the observer activates. See image for the contraption I used. The observer does not activate on reloading chunks or if the Redstone is unpowered. Similar to issue MCPE-13608 but unresolved and specific to observers and powered Redstone.
I apoligise I uploaded this 3 Times as my phone does not seem to be giving me confirmation of a successful post.
Never mind, that happens often.
Btw this "Relates to"
MCPE-13270andMCPE-13413but it is possible that they are all the same bug.Does this bug still appear in 0.14.0? If so please respond.
Yes, unfortunately this still occurs same as before.
Yes this bug is still around in 0.14.2 for my iPhone 4- I have tested numerous combinations of redstone, torches, repeaters, comparators and dispensers. Most times there is a single pulse right as the world opens that activates the dispenser. My guess is that the powered state of the dispenser is not saved so when you open the world it activates it again. Please fix. This causes damage when you have TNT dispensers.
Please respond and add the current version if you can reproduce this issue.
Still happens in 0.15.2
I tried in a different world and this happened as well.
Thanks,
Jim
I'm sorry sir, 0.15.4 is the current version, not 0.15.2.
Confirmed in 0.15.4, please reopen.
Yes, Azelef is right this still is a major problem. I mistakenly typed 0.15.2 insteard of 0.15.4
I have noticed in my testing that this happens with redstone blocks with a torch on top as well.
Affects 0.15.90.8 (0.16.0 beta build 5). Interestingly, I've only had this happen to me on Pocket Edition, and it isn't happening to me on Win10 0.15.10. I may need to do some more testing, though.Ignore this comment, I believe I was improperly testing this bug. I'll try and properly test it later...
Fixed in 1.1.0.55! Yay!