I have several simple "Overflow Proof Sorters" in various places around a world. The ones that have redstone going across a chunk border do not behave consistently, but it appears the ones all within one chunk behave normally.
Edit: Much easier steps to reproduce. On my device this seems to cause the bug about 1/3 of the time. Steps two and three are not required, but seemed to make the bug happen more frequently.
1. Create a door (1174, 5, 15) and a button (1175, 6, 16) and a pressure plate (1173, 5, 15). See doorandbutton.jpg
2. Delete and replace the pressure plate.
3. Step on the pressure plate and walk through the door.
4. Travel to 1174, 5, 71.
5. Save and exit.
6. Try the button and it will be likely to not work. You may have to repeat these steps several times.
Old and less clear Steps to reproduce:
1. Create an "Overflow Proof Sorter" (see attachment "overflowsorter.jpg" or similar design on https://minecraft.gamepedia.com/Tutorials/Hopper) that has redstone crossing a chunk border. It is probable that many other devices show the same behavior.
2. Do things Unfortunately I have been unable to reproduce the behavior with simple tests such as unloading and loading half the machine. It seems that if you play and dump items into the machine above for a few hours it will break pretty consistently, but the exact details of how it breaks remain elusive.
3. Come back to find a powered repeater powering a block with a torch on the other side that is also powered (see attachment "oops.jpg"). This is bad and breaks things; everyone is sad.
4. If you break any of the redstone dust on top and simply replace it the device will start working again.
Related issues
Attachments
Comments
migrated
migrated
Are you able to change the repeater in question to the second tick and maintain functionality; howbeit; slightly slower? I seem to remember someone else complaining about redstone timing elsewhere in another bug when on the first tick setting.
migrated
I have not verified whether Louis's suggestion works because it causes other issues with the design in question and I cannot replicate in a simple test world.
migrated
My guess is that the sorters that cross chunk boundaries are breaking because of the two chunks unloading and reloading at different times. If the cross-chunk sorter works while you stay in the area, but always breaks when you travel some distance away and then return then this is likely the issue. If you can use slash commands then setting the area to a tickingarea (kind of like spawn chunks) may solve your problem. If you cannot use commands, then your only choice may be to rebuild the sorters within a single chunk.
migrated
This issue affects almost all processed items in the game. Seems the lazy chunks are not implemented correctly as they should buffer any output from an active chunk so that all variables are set correctly prior to the lazy chunk becoming active.
Auldrick
I am seeing a similar problem with redstone devices copied from an original using a /clone command. Any active redstone torches (unlit) and repeaters (lit) in the clone are unresponsive to their inputs. Breaking and replacing them corrects the problem. The problem does not happen to torches and repeaters that were not activated when the /clone command was executed. In my case the issue doesn't involve chunk loading/unloading or lazy chunks, but the fix for either problem could potentially fix the other. I believe this is an unrelated problem.
Auldrick
Related to MCPE-17304, MCPE-29169.
Auldrick
Confirmed on Windows 10 in a new flat single-player world in creative mode. I did not use a ticking area. The button worked after I walked to 1174, 4, 71, saved and quit, so I tried again after walking to 1174, 4, 136, saving and quitting. The second time the button failed. Possibly affected by larger render distance/player ticking area?
Edited to add: I have attached a demo world (file MCPE-27855.mcworld). To exhibit the problem, you *must* save the world while the door is outside of any ticking area.
I did experiments with a /tickingarea circle, 2 chunk radius around the door. With a ticking area active when the world was saved, the problem did not occur (3 tests). Without a ticking area active, the problem occurred 100% of the time (8 tests).
Edit: Retested with a different render distance. It seems as if the problem only occurs when you save while at a distance farther than your render distance.
Auldrick
I can no longer reproduce this problem under Windows 10 release 1.2.13.60. If anyone is still experiencing this problem, please comment here and add the affected version.
[Mojang] Mega_Spud (Jay)
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Auldrick
Closed as Cannot Reproduce as there has been no response and no further comments for 6 months.
GoldenHelmet
Retested in 1.14.30 as part of researching MCPE-48054. Cannot reproduce with the button & door setup, nor with the powered repeater setup. However, per MCPE-48054 redstone dust can still lose its link to solid blocks across chunk borders.