-
Bug
-
Resolution: Invalid
-
None
-
1.21.0.23 Preview
-
None
-
Unconfirmed
-
Xbox
I have an issue with my bedrock world starting to corrupt in the experimental version of Bedrock.
I was stupid and most likely created a scenario with a huge excessive amount of pending ticks because I:
-Had experimental mode on and chunk load limit set to the new maximum (by accident, forgot to turn it back after testing)
-Had loads of different redstone machines in one chunk and more in nearby chunks
-Had a gold farm with nether portal in this chunk
-Had lots of water streams on blue ice and bubble columns/elevators in nearby chunks flowing items into this same chunk at high speeds
My world started showing signs of corruption in this specific chunk (and nearby chunks):
-Water not flowing normally
-Redstone being slow
-Blocks changing position
-Progress not saving/reverting
If I use a tool to inspect all the pending ticks, and remove all the pending ticks for the chunks affected, will this save my world? Or should I go back to an earlier backup where this corruption has not yet triggered, remove the pending ticks here, and then fix everything in that backup?
Also, was the main cause here too many tick updates? Or the render distance allowing the updated ticks from pretty much all my redstone machines in the area to overflow the game memory?