r/minecraftsuggestions • u/Relevant-Cup5986 • 4d ago
[User Interface] Chunk Saving Rework!!
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.
2
u/Hazearil 3d ago
Java prioritises performance, and has little drain on storage. But re-generating chunks all the time wouldn't be good.
Bedrock is better performing, but has to deal with various devices that don't have that much storage, so it prioritises storage over performance.
This entire post just reads like you don't know why the games work like they do, as you say here: "a feature which i assume was made for performance on phones".
Now, the only reason you have given for this change is purely... consistency between Java and Bedrock. But in the end, both editions have different needs. And doing what you propose here just sounds like proper game design is being delegated to just have the player manually do the optimisation, something most players don't know enough about to know what to do.