Since the 1.16 update has been implemented, severe problems have been noted with the automatic autosave of worlds, a problem that stands out especially on olg gen consoles (Switch, Playstation 4 and Xbox One). Once the autosave is executed, the world tends to freeze for a certain amount of seconds in all its senses while in process, leaving the world unplayable during this time, unable to interact with any block or mob, generating crashes of music/sounds and terrain generation. It also affects processes such as crop growth, day/night cycle, mob generation, etc.

In addition, it is a problem that becomes exponentially more frustrating as the world gets larger, since more data must be stored. So, in some worlds just started, it can be a problem that lasts app 15 to 20 sec, but with some worlds over 200mb of weight can last over 60 sec and even reaching 3 minutes of freezing, and this is not the worst, since the world tends to autosave for almost every move we make, so this happens more often everytime, until it reaches a point that the worlds become totally unplayable.

I am not an expert in programming to say this, and I understand that it must not be easy to fix such a big problem, but I really believe that this problem must be fixed, we have had this problem for more than three years and it only gets worse and worse with every update. And even if it is too complex to fix as soon as possible, an option to disable the autosave would be really appreciated, leaving this option as something manual that the player must use as it was in Minecraft Legacy Edition (Versions developed by 4J Studios).

I will leave a video that I found on Youtube in my little investigation of the problem. It is difficult for me to send you a video taking into account that I play from my Ps4, but my case is not far from what you see in this video:

• https://youtu.be/QwI5SwuMj-o

[Credits to SantyEagle for uploading the video]