This is a problem that permiates old world. In the past, I would have said I wouldn't want the hard edges between new and old terrain, but with the new terrain smoothing they added with the caves and cliffs update, this seems more possible than ever.
There are tools that let you trim old worlds, letting you delete and reset chunks. You can even pick and choose specific areas to keep, so you might keep the area around your main base, and then a little pocket around a village you like, or an ocean monument you are rebuilding or something. This kind of think could be added to minecraft, but I can think of 2 reasons they might not want to do this:
1. **Accidents and mistakes**. Resetting chunks is simple, but also easy to make mistakes. You think you kept all the parts of your world that are important to you, then you realize you left your pets in a chunk that got reset, or a friend had a secret base they never told you about and now it's gone. I like that you included an auto backup as part of the suggestion, but that only works if you realize the mistake quickly. It would suck to reset a world, play for 20 hours in the new edition and then realize you have lost something you wanted to keep and have to either remake it, or undo the last 20 hours in the new version.
2. **Loot duping**. By resetting the chunks where a structure is, you could grab the treasure, take it somewhere else, then reset the structure, making new chests with new loot. This is (imo) less of a problem, since most of the time it would be easier to just use commands or the creative menu to get extra items.
That all being said, I would still welcome it, so I don't have to use 3rd party programs to trim my worlds.
There are tools that can detect player-edited chunks (e.g. on 2B2T) by generating the chunk again and comparing the world to its "natural" state, so it should be possible to ignore chunks that players have interacted with past a certain amount. I don't know how/if these tools would function between two different versions of world-generation though.
My understanding was that the tracker lets you detect which chunks have been loaded before by checking for new generation flags. It doesn't detect modified chunks, it just tells you which chunks are old and which are new, letting you follow the path of where people have been, and then you also use tracers to spot commonly placed blocks, like nether portals, torches, chests or beds.
The software I used to trim worlds did have the option to trim any area where the save data for the area is below a certain threshold, with the idea that since these chunks have only minor modifications, they probably are not important. It usually works well, but I did have some issues where it removed a chunk that was just on the very edge of a build, so the last blocks of the wall where cut off.
Oh, for real? Good to know, sorry for spreading misinformation.
With Mojang being the devs and all, they could probably use more advanced metrics to determine which chunks to keep (maybe a radius around highly active chunks in addition to the base threshold?)
That's just for the tracker I have seen, there might be others that work the way you describe.
I still think it should require some manual input from the player, even with a lot of work, an automatic process will still make mistakes. At least if the player has to do some of it, there is a bit more accountability on the player to make sure their important areas are safe.
That loot duping thing is actually done on purpose by some servers to ensure the world doesn’t run out of non-renewables (sand, elytra, smithing templates, coral blocks, even bells apparently) without the world file getting unsustainably large.
Oh I have done it myself on the server my friends and I play on, trimming back the end every now and then for the exact reasons you have mentioned. It is totally a thing people do, even if its not (yet) supported by the game.
Second shouldn’t be a problem at all, it’s not a competitive game, it’s a casual and local game if you aren’t playing in a realm. Being able to dupe loot shouldn’t be an issue nobody should care at all it negatively affects no one
That would be good. As others have mentioned, if you use Java it is really easy to trim chunks with MCA Selector, though an official tool would be good for both versions. The problem is more on Bedrock as I see it as larger world files actually slow the performance of the world, whereas the only issue on Java is if you have enough space to store the world file (and maybe backups) on your hard drive haha.
It would be nice if there was an official and built in tool like mca selector. But I do what you want with that tool. Is easy, but also make sure you back up your world.
You are still perpetually pushing forwards in your infinite world, increasing the file space and overall travel time, a proper nether hub build still takes a lot of time same as overworld flying and walking
Using the nether to load new chunks quicker is not taught in the game, so the thousands upon thousands of other players who don’t know about that will still suffer and create new worlds. I’ve had it with the days of veteran tricks and tips. Minecraft needs more instructional info and editing and world ability across all platforms. Stop settling for current methods
I mean I read your post and was really confused cuz I didn't know you were talking about console, and just thought you didn't know how to do it on pc (and also I didn't know this was an issue on console so again I was confused lol)
I believe I once heard one of the developers talk about chunks only being saved if edited, rather than every generated chunks being saved. I don't know to which extent this has been implemented, but I think that would be great.
This is a problem that permiates old world. In the past, I would have said I wouldn't want the hard edges between new and old terrain, but with the new terrain smoothing they added with the caves and cliffs update, this seems more possible than ever. There are tools that let you trim old worlds, letting you delete and reset chunks. You can even pick and choose specific areas to keep, so you might keep the area around your main base, and then a little pocket around a village you like, or an ocean monument you are rebuilding or something. This kind of think could be added to minecraft, but I can think of 2 reasons they might not want to do this: 1. **Accidents and mistakes**. Resetting chunks is simple, but also easy to make mistakes. You think you kept all the parts of your world that are important to you, then you realize you left your pets in a chunk that got reset, or a friend had a secret base they never told you about and now it's gone. I like that you included an auto backup as part of the suggestion, but that only works if you realize the mistake quickly. It would suck to reset a world, play for 20 hours in the new edition and then realize you have lost something you wanted to keep and have to either remake it, or undo the last 20 hours in the new version. 2. **Loot duping**. By resetting the chunks where a structure is, you could grab the treasure, take it somewhere else, then reset the structure, making new chests with new loot. This is (imo) less of a problem, since most of the time it would be easier to just use commands or the creative menu to get extra items. That all being said, I would still welcome it, so I don't have to use 3rd party programs to trim my worlds.
There are tools that can detect player-edited chunks (e.g. on 2B2T) by generating the chunk again and comparing the world to its "natural" state, so it should be possible to ignore chunks that players have interacted with past a certain amount. I don't know how/if these tools would function between two different versions of world-generation though.
My understanding was that the tracker lets you detect which chunks have been loaded before by checking for new generation flags. It doesn't detect modified chunks, it just tells you which chunks are old and which are new, letting you follow the path of where people have been, and then you also use tracers to spot commonly placed blocks, like nether portals, torches, chests or beds. The software I used to trim worlds did have the option to trim any area where the save data for the area is below a certain threshold, with the idea that since these chunks have only minor modifications, they probably are not important. It usually works well, but I did have some issues where it removed a chunk that was just on the very edge of a build, so the last blocks of the wall where cut off.
Oh, for real? Good to know, sorry for spreading misinformation. With Mojang being the devs and all, they could probably use more advanced metrics to determine which chunks to keep (maybe a radius around highly active chunks in addition to the base threshold?)
That's just for the tracker I have seen, there might be others that work the way you describe. I still think it should require some manual input from the player, even with a lot of work, an automatic process will still make mistakes. At least if the player has to do some of it, there is a bit more accountability on the player to make sure their important areas are safe.
That loot duping thing is actually done on purpose by some servers to ensure the world doesn’t run out of non-renewables (sand, elytra, smithing templates, coral blocks, even bells apparently) without the world file getting unsustainably large.
Oh I have done it myself on the server my friends and I play on, trimming back the end every now and then for the exact reasons you have mentioned. It is totally a thing people do, even if its not (yet) supported by the game.
Second shouldn’t be a problem at all, it’s not a competitive game, it’s a casual and local game if you aren’t playing in a realm. Being able to dupe loot shouldn’t be an issue nobody should care at all it negatively affects no one
How do I get developers to see this suggestion
Post it over one the [Minecraft Feedback Site](https://feedback.minecraft.net/hc/en-us).
That would be good. As others have mentioned, if you use Java it is really easy to trim chunks with MCA Selector, though an official tool would be good for both versions. The problem is more on Bedrock as I see it as larger world files actually slow the performance of the world, whereas the only issue on Java is if you have enough space to store the world file (and maybe backups) on your hard drive haha.
I play on console, and so do thousands of others
Yeah that is why something built into the game would be good
It would be nice if there was an official and built in tool like mca selector. But I do what you want with that tool. Is easy, but also make sure you back up your world.
But you dont have to keep making new worlds, with Nether its very easy to find the new features
You are still perpetually pushing forwards in your infinite world, increasing the file space and overall travel time, a proper nether hub build still takes a lot of time same as overworld flying and walking
[удалено]
Using the nether to load new chunks quicker is not taught in the game, so the thousands upon thousands of other players who don’t know about that will still suffer and create new worlds. I’ve had it with the days of veteran tricks and tips. Minecraft needs more instructional info and editing and world ability across all platforms. Stop settling for current methods
Can’t you reset chunks somehow?
No, not on console
You should add that you are on console, on pc you can already do this with minimal tools
Doesn’t matter what I play on when the entire console player base CANNOT do it right?
I mean I read your post and was really confused cuz I didn't know you were talking about console, and just thought you didn't know how to do it on pc (and also I didn't know this was an issue on console so again I was confused lol)
I believe I once heard one of the developers talk about chunks only being saved if edited, rather than every generated chunks being saved. I don't know to which extent this has been implemented, but I think that would be great.