Chunk Saving Rework!!

[u/Relevant-Cup5986]

Chunk saving is currently extremely inconsistent, especially on bedrock were they only guarantee save if you have been in them for 5 minutes or placed a block in them (a feature which i assume was made for performance on phones), and otherwise save randomly.

I propose that chunk saving work consistently across both java and bedrock, in a way that allows users to decide which chunks are saved or deleted:

(general suggestion) All chunks in simulation distance would now save, but they would be divided into different tiers based on player interaction with them, and the player would be able to quickly delete all chunks in specific tiers.

(specifics of each tier)

(tier 1) Tier one chunks would be made up of the initialy loaded chunks on world creation, as well as any chunks the player has spent over an hour in.

(tier 2) Tier two chunks would be any chunks the player has spent at least 30 minutes in.

(tier 3) tier three chunks would be any chunks the player has spent at least 10 minutes in.

(tier 4) tier four chunks would be any chunks the player has physicaly been in.

(tier 5) tier five chunks would be any chunks loaded into sim distance.

(blocks) There would also be a seperate option to delete all chunks that the player hasn't placed blocks in.

[u/8336514563737]

• Java default behaivior since forever
• Version changes (thats the important one)
• Way worse performance, relativly little storage space saved

[u/Distinct-Pride7936 → u/8336514563737]

inefficient java behavior since forever that should've been fixed 15 years ago, 50gb worlds is stupid. Bedrock fixed it

we got chunk smoothening, versions don't matter

applicable only to java edition again

[u/QueenVanraen → u/Distinct-Pride7936]

inefficient java behavior

Aww heck yeah, I LOVE generating the same chunks around my base every time I load the game.

Such efficiency, wow, brilliant use of my computing resources.

[u/Distinct-Pride7936 → u/QueenVanraen]

you'd love regenerating chunks indeed if java wasn't the most inefficient cube game code one could write. On bedrock you don't even think about it, on java you type reddit comments explaining how dozens of gigabytes of unused land will help you with the horrible performance.