Upgrading world from 1.10 to 1.14.4

Discussion in 'Systems Administration' started by Crysillion, Jan 14, 2020.

  1. Hello! I looked up this issue rather extensively and discovered that in 1.13, Minecraft changed the way it handled world generation in a significant way, which has a high tendency to break worlds that existed before 1.13.

    I'll start from the beginning and try to keep this short.

    The world is 1.10 because that's the last version a plugin called GiantCaves was supported. I am making a cave world and needed this plugin to create it. After creating the world, I used WorldBorder to load 10,000 x 10,000 of the world. I knew that by pre-rendering it, it should stop the world from generating default terrain where I didn't want it to.

    I then shut the server off, backed up the world (of course), then ran the server with Minecraft 1.14.4 (with GiantCaves removed). For much of the world, everything is still in tact. For other parts, however...


    Chunks are abruptly generated in the vanilla style. In this case, this is an ocean, so it places random chunks of ocean through the world. The terrain height you're looking at elsewise extends up to about Y210~, because it's meant to be a cave world.

    These holes did not exist when the world was in 1.10. I looked around and saw someone suggest --forceUpgrade. I attempted that with the world backup and, after a couple hours, ran the server again. Same problem in the same spots. The same chunks reverted to default.

    My question to you all now is... what can I do to fix this? Is there any particular reason why this is happening (in the same spots with the same chunks)?

    Would fixing these manually be an option, or would these chunks keep reverting back to 1.13 default?
    #1 Crysillion, Jan 14, 2020
    Last edited: Jan 14, 2020
  2. Phoenix616

    Resource Staff

    It is usually suggested to increment the server version with each minor version when upgrading the worlds so the chunk errors might be caused by you going directly to 1.14.4. (Also you should load the world once completely e.g. with WorldBorder's force option or for newever versionns the --forceUpgrade startup argument to make sure all chunks are converted)
    • Agree Agree x 1
  3. I'd be down to give this a shot for sure, but I'm using TerrainControlGenerator and it's not updated to 1.13. $35 for EpicWorldGenerator is a rather steep asking price when all I'm trying to do is raise the base terrain, so I'm at a bit of an impasse there.