The server starts a new "world" folder instead of my uploaded map — how do I fix it?
When you upload a map and the server boots into fresh terrain instead, it means the server couldn't find a valid world where it expected one. This is almost always a folder-name or level.dat placement issue, and it's quick to fix.
Why it happens
The server looks for a valid world at the folder named in level-name (default world), with level.dat directly inside it. If your map's folder is named something else, or level.dat is buried in a subfolder, the server assumes there's no world there and generates a new empty one.
Step-by-step fix
- Stop the server.
- Confirm your map folder is named exactly
world(or matcheslevel-name), and thatlevel.datis directly inside it — not nested likeworld/MyMap/level.dat. - Delete the auto-generated empty
worldfolder. - Re-place your map correctly and start.
Tip: A common cause is a double-nested folder after unzipping — e.g.
world/MyMap/level.dat. Move the contents up solevel.datsits atworld/level.dat.
Frequently asked questions
How do I know level.dat is in the right place? Open the world folder in the Files tab — you should see level.dat listed right there, alongside the region folder, not inside another subfolder.
Do I need to delete the empty world first? Yes — remove the auto-generated empty world so your uploaded folder can take its place cleanly.
It still generates fresh terrain — what else could it be? Check that level-name in server.properties matches your folder name, and that the upload completed fully via SFTP.