I have done a test in the new pre-release versions of 1.18.
I create a world in 1.17 and update it to new pre-release versions of 1.18.
The blending feature works well.
Therefore, there should be three kinds of chunk, pure 1.17 chunks, blended chunks and pure 1.18 chunks.
Then, I used a tool called MCA Selector to delete chunks.
If I delete pure 1.18 chunks to regenerate the chunks, no problem exits.
However, if I delete pure 1.17 chunks or blended chunks, those chunks cannot regenerate well with blending feature
The game does not attempt to blend those chunks and the harsh chunk borders show up.
I hope that the blending feature can still work well if the chunks from 1.17 or being blending are deleted in 1.18.
Attachments
Comments 9
Modified game states are considered invalid. The issue you experienced is from modifying world data. This does not fall into the jurisdiction of the developers.
I think this should have been resolved as "wont fix" not works as intended but whatever. I personally haven't ever reset chunks but if you guys do I recommend looking for a program that will allow for those deleted chunks to blend.
I believe the main issue here is that the chunks were deleted after the world was already upgraded to 1.18. If you delete chunks before upgrading to 1.18 it should work fine. If it doesn't, please file a new bug report.
It blends them properly only if the new edge chunks have their InhabitedTime, Timestamp and LastUpdate set to 0, if not and they have been visited before it won't blend them, I don't know if it warrants a bug report.
Regardless I think that this issue should be addressed as server administrators often remove chunks after they are generated, sometimes player maliciously generates hundreds of thousands of chunks that have to be removed to decrease the ridiculous world size, sometimes they build offensive stuff or lag machines that need to be deleted and if they do it on blended chunks after the upgrade, there should be an option to re-enable blending in that region.
Even if you don't want to support such use cases, chunk deletion can happen in normal gameplay like I mentioned above and as is evident by the chunk deletion issue preasent in Pre-Release 5 so I think this issue should be resolved regardless.
I agree what Von Sparq says.
I think that a lot of server administrators often remove chunks after they are generated.
I usually deletes the chunks too to renew resources near spawn point.
Moreover, I faced an issue unluckily before.
The issue is that the chunk has error and cannot be loaded well.
The only way I can do is to delete the chunk to regenerate.
If I have to delete chunks after updating to 1.18,
I may need to face the risk of not blending well in the regenerated chunk.
If the world was last opened in 1.17.1 (or before) and blending doesn't work when upgrading to a 1.18 pre-release, that's a valid bug and you should immediately file a bug report about that. No matter if chunks have been trimmed or not.
Edit: for further clarification, if your world was ever opened in a 1.18 version, and THEN you remove chunks, you can't expect world blending to work properly. (At least for the time being)
Further edit: Note that blending only happens at the edges of old terrain, so as long as you don't trim near the edges of 1.17.1 terrain you should be fine.
That means we cannot trim near the edges of 1.17.1 after upgrading to 1.18.
Will Mojang enhance the blending feature in the future to prevent harsh chunk borders if we delete the chunks in the edges of 1.17.1 terrain if the world is upgraded to 1.18?
Because it is not easy for us to remember which chunks are in the edges of 1.17.1 terrain and many players want to delete chunks without worries such as having error in those chunks or before upgrading from 1.18 to 1.19 in the future.
I would like some clarification here.
Individual chunks have a DataVersion field that records the version that the chunk was last loaded in. Chunks also have a Status field that indicates whether terrain generation has been completed in that chunk. Are these fields used when determining whether to blend chunks?
If a WORLD was opened in 1.18 or newer, and the player then explores to trimmed, fully-generated CHUNKS last loaded in version 1.17.1 or older, is chunk blending expected to work?
I am also experiencing this issue, it is the easiest to trigger by manually removing chunks in the described way but this bug can also be encountered in normal gameplay, if the chunks are deleted or corrupted for example as a result of a crash.
I think it would be best if there was a system that checks if the newly generated chunk will smoothly fit with chunks next to it and if not to engage blending in that area.