-
Bug
-
Resolution: Fixed
-
Minecraft 18w49a, Minecraft 18w50a, Minecraft 19w02a, Minecraft 19w03c, Minecraft 19w04a, Minecraft 19w04b, Minecraft 19w05a
-
Confirmed
After unloading and reloading a chunk with various active redstone components by flying away, the redstone components are stuck.
This is likely caused by scheduled ticks not being saved correctly for some reason.
Note that the components keep working if instead of unloading them by flying you leave the world and enter it again.
Steps to reproduce:
(0. Make sure you are not in the spawn chunks)
1. Build a repeater clock
2. Fly far way (render distance 2 helps)
3. Come back, see repeaters stuck
Video: https://youtu.be/S48ctDkQw3Y
Affected components:
- Command blocks (Kind of important, because this hinders testing for issues regarding chunk loading)
- Repeaters
- Comparators
- Redstone Torches
- Redstone Lamps
- Observers
- Falling blocks
- Buttons
- Pressure plates
- Tripwire hooks
- Scaffolding
- Chorus Plants
- Water/Lava
- Detector Rails
- is duplicated by
-
MC-140156 redstone clocks freeze whenever I walk away from the clock
- Resolved
-
MC-141038 repeating commands
- Resolved
-
MC-141079 Commandblocks set on repeat on always active stop working after being in unloaded chunks, and then the chucks are realoaded.
- Resolved
-
MC-141941 Saving game while water is flowing freezes the flow
- Resolved
-
MC-142149 Active Redstone Clocks/Observers stop working right when reloading game
- Resolved
-
MC-142319 Repeating Command Blocks doesn't work well on upgraded world
- Resolved
-
MC-143419 Redstone stops working when the chunk is inactive
- Resolved
-
MC-143544 Detector rails stuck powered after chunk unloads
- Resolved
- relates to
-
MC-158219 Tile ticks sometimes are not cleared from the save file properly, causing some blocks to become unresponsive
- Reopened