Guidefor server owners3 min read
IllegalStateException: Overworld settings missing when moving a world between Paper and vanilla
Paper 26 stores world_gen_settings.dat inside the Overworld dimension folder. Vanilla and NeoForge read it from the shared data folder. Which files to move, in which direction, and why Paper closed the report as working as intended.
What you are seeing
The server dies during startup, after datapack loading, with two lines that belong together:
Unable to read or access the world gen settings file!
world/data/minecraft/world_gen_settings.dat
java.lang.IllegalStateException: Overworld settings missing
It happens the first time a world that has been running on Paper is started on vanilla or NeoForge. The world is fine. The file exists. It is just not where the server now reading it expects it to be.
The cause
Minecraft 26.1 pulled most of level.dat apart into separate files and moved every
dimension under a dimensions folder, covered in full in the 26.1 world folder
layout. Paper rebuilt its own storage on top
of that layout in a pull request merged 3 April 2026, which moved per-world data into each
dimension's own data path.
That is where the two implementations diverge. Vanilla and NeoForge 26.2 treat
world_gen_settings.dat as world level data and read it from the shared folder. Paper 26.2
treats it as Overworld data and writes it inside the Overworld dimension.
| Server | Where world_gen_settings.dat lives |
|---|---|
| Paper 26.2 | world/dimensions/minecraft/overworld/data/minecraft/ |
| Vanilla and NeoForge 26.2 | world/data/minecraft/ |
The fix
Stop the server, then move these five files from
world/dimensions/minecraft/overworld/data/minecraft/ into world/data/minecraft/:
game_rules.datscheduled_events.datwandering_trader.datweather.datworld_gen_settings.dat
Start the server again and the world loads. This is Paper's own documented procedure on its migration page, not a community workaround.
Only the last file causes the crash, which is why most forum answers mention just that one. Move only that one and the server will start, having quietly reset your game rules, weather, scheduled events and wandering trader state to defaults. Take all five.
Whether updating helps
It does not, and this is the part worth being blunt about. The mismatch was filed against Paper on 28 July 2026 with a clean reproduction, no plugins and no datapacks. It was closed three minutes later, labelled resolution: works as intended. The reasoning from a Paper developer was that CraftBukkit's multi-dimension support made a large amount of state per dimension, and keeping compatibility with vanilla's file positions is not viable without breaking dimension support that a lot of people rely on.
So there is no build number to wait for. If you move worlds between Paper and vanilla or NeoForge on the 26 line, moving these files is a permanent step in your process.
The direction that is automatic
Going the other way costs nothing. Paper detects a vanilla world on first startup and
converts it, logging lines tagged VanillaWorldMigration while it runs. Only Paper to
vanilla is manual.
That migration was not always reliable. The pull request that diagnosed the state of it in
March 2026 opened with the line "World migration for existing worlds was completely broken,
and we were not using the new folder layouts, instead defaulting to falling back to the
legacy world folder structure, causing existing worlds to be inaccessible." On Paper 26.1,
worlds coming from vanilla ended up with their region files nested inside
world/dimensions/minecraft while Paper still read the old paths, so the Overworld, Nether
and End all regenerated as new.
That pull request was closed without merging. The rewrite that superseded it, merged the same day, is what actually ships today, so the broken behaviour belongs to 26.1 rather than to current builds. Anyone still sitting on an early 26.1 Paper build should update before migrating a world into it.
Do not delete the file
Paper still crashes on startup if the Overworld's world_gen_settings.dat is missing
entirely, rather than regenerating it with defaults. That report, filed 14 July 2026 against
a 26.2 development build, is open and accepted. A pull request merged 26 July 2026 that
fixed migration for deleted dimensions lists this crash as a known remaining issue. Other
dimensions are unaffected.
The practical consequence is that copying is safer than moving. Copy the five files to the
shared data/minecraft folder and leave the originals in place, and the world stays
startable on both server types. Either way, take a backup first: backing up a server before
an update covers what else needs to go in it.
