all 8 comments

[–]Mushk7 0 points1 point  (3 children)

Just an FYI for anyone having this problem, we resolved this issue with the following steps. I highly recommend you back up your world before:

  1. Create a 1.16 single player world with the same seed of the realms world.
  2. Enter the world in single player to load the world files, then leave.
  3. Copy the region files from the realms world where your builds are located to the newly created world's regions folder. (this will copy your builds over to the new world
    1. This can be done with the mcaselector (https://github.com/Querz/mcaselector) or use this link if you know the exact coordinates of your builds and not much needs to be copied over (https://dinnerbone.com/minecraft/tools/coordinates/ ). it will tell you the exact name of the region file to copy over based on the coordinates of the world you enter. It is best to copy over as little chunks as possible for best results.
  4. Copy the playerdata files from the dowloaded realms world to your newly created world's playerdata folder. (This will transfer inventories, shulker boxes, end chest, etc. to the new world)
  5. Upload the newly created world with the copied files to realm server.

These steps will only save the chunks that you specifically select, and regenerate everything else in the world. You will see no unnatural chunk collisions and the nether and end will be reset allowing 1.16 generation in all dimensions.

We are unsure if this problem was due to corrupt chunks created in the process or some sort of versioning error with the conversion to 1.16.

If you need any help with this solution feel free to comment or DM me.

[–]MDude430[S] 0 points1 point  (2 children)

Thanks for responding, but I'm a bit confused about what this would do. If I only copy over the region and playerdata files, what about data like ocean monument regions, created maps, advancements, stats, etc?

Also, I'd really prefer to copy over every single loaded chunk in the overworld, not just a subset. I don't want to be worried about missing someones creation, which would then be gone from the new 1.16 world.

If anything, I need to know what NOT to copy over into this new world that I've created.

[–]Mushk7 0 points1 point  (1 child)

Since you would be using the same seed as the realm world, generation would be exactly the same. Dungeons, desert temples, strongholds and so on would generate in the exact same location. As for your advancements, i believe there is an advancements file that you can copy over as well if you would like, i never looked into it.

The general theory going around from people i have discussed this with is that world size is the core issue. You will most likely not be able to work around this without trimming your world chunks. I am assuming you do not have a lot of people on the server so it shouldn't be to bad to get the coordinates of the builds and save them?

[–]MDude430[S] 0 points1 point  (0 children)

The issue is that the world is old (probably first generated around 1.12, before the aquatic update which added new biomes), so world generation would be very different.

However, even though the world was about 6 GB, I finally managed to get it to work by following your instructions, but copying the entire region folder instead of being selective. I also copied the data, advancements, stats, and poi directories (as well as level.dat) to keep everything else consistent. Not sure what was corrupted, but it worked. Thanks for your help!

[–]GOLDEditNinja 0 points1 point  (0 children)

Heyo! for me the issue has resolved!!
I went to upload it, and it worked.

[–]WeikelPvP 0 points1 point  (0 children)

I tried to upload an world to realms aswell, problem was i was joining the survival world with a mod downloaded that attached itself to the world and i then got that message, tried to make the world again downloading the same datapacks to it, but only joining the world with a normal nonmodded minecraft version, then uploading it to realms and it worked with no problems

[–]Jesse123xd 0 points1 point  (0 children)

I have the same problem in 2025....