How sure are we that 1.18 won't break a 1.17 world?

[Cranching]

How sure are we that 1.18 won't break a 1.17 world?

 

I'd like to try it but many hours into current world.

[TroyCast]

My old 1.16 world does no longer work under 1.18, so I would be really unsure.

[Maelstrom]

Make a back up of your 1.17 world and then try it.  If the world breaks, you can revert to the back up and continue playing in 1.17 (probably need a separate install to do so though).

[Cranching]

Yes, agreed, parallel would be the way to move forward. Does anyone have 1.18 and 1.17 installed in parallel for this purpose? How is it working? Were there any tricks getting 1.17 and 1.18 installed in parallel (if they look in the same place(s), directories or IP, for fundamentals) ?

TroyCast - I would expect that 1.18 or any other full version update changes the most recent world file(s), so the way to go from 1.16 to 1.18 could be through 1.17?

[Rufkut]

Another option is find a map in 1.18 you like then using creative mode to create schematics of your base then importing those schematics in the 1.18 world. There you'll have your base and a new chunks to explore with all the newer features. 

[Cranching]

I used the method detailed by Streetwind in various posts, e.g., here. It works. 

Rufkut - this is a good idea, also new is:

• Feature: Added  /land claim export  to allow players on multiplayer servers to export their claim to be saved on the server. Disabled by default, requires privilege "exportclaims" to run. It is up to server owners to determine what to do with these exports - they are in the server data folder. Useful for migrating to a 1.18 world via worldedit.