Santy Viper

Hi, I am the original creator of this report. I am posting this new comment because, due to the migration of the bug tracker system, I no longer have access to my original account, even using the same email address.

IMPORTANT UPDATE: THE ISSUE ALSO AFFECTS PS5!

The severe lag spike issue during autosave is still present and is LITERALLY making the game unplayable for many users. I was surprised to learn from comments on my video that the problem also affects PS5, which indicates this is a deeper optimization or code issue, not just a PS4 hardware limitation (CPU/HDD).

Dear mods, please, I urge you to re-evaluate this issue. I am here after being ignored for 3 years because this is a truly critical bug. Most players don't even know the autosave is the cause of the freezes.

Detailed Description and Reproduction Steps:

1. What Happens: When the autosave runs, the local server freezes severely, causing huge, game-breaking lag spikes. As you know (per the original report), this stops all interactions: mobs, block placement/breaking, chests, inventory, and even the game ticks (redstone, day/night cycle).

2. Frequency & Severity: This occurs every time the autosave executes (random intervals). The strength and duration of the lag spike is DIRECTLY determined by the SIZE OF YOUR WORLD (MB/GB).

3. How to Reproduce:

   • This problem does NOT occur on recently created worlds because the file size is too small.

   • The lag starts and intensifies after playing for some days or weeks (depending on the amount of generated chunks/world size). The bigger the world gets, the worse the lag becomes until it is unplayable.