PortalMine owner documentation. Test important changes on a copy and keep a verified backup.
Safe rule: never replace a world while the server is running, and never delete the previous world before the new archive is validated.
1. Stop writes and preserve the current world
- Stop the server and wait until the status is fully offline.
- Download or create a backup of the active world and configuration.
- Record the current
level-namevalue. - Keep the backup outside the server storage until the replacement is verified.
2. Validate the archive structure
A valid world archive must contain the world data, not another download page or a launcher. The most common import failure is an extra wrapper folder.
| Edition | Expected markers | Typical location |
|---|---|---|
| Java | level.dat, region/, optional DIM-1/ and DIM1/ | World root |
| Official Bedrock | level.dat, db/, levelname.txt | World root inside worlds/ |
| PocketMine-MP | level.dat plus provider-specific world data | Named folder inside worlds/ |
If the archive opens as MyWorld/MyWorld/level.dat, remove one wrapper level before importing. Do not flatten the files inside db or region.
3. Import and replace the active world
Use the World import action, choose the archive, and wait through upload, transfer, extraction, validation, and replacement. For a large file, 100% browser upload is not the final stage. PortalMine must still verify the server-side file and find the world root.
4. Edition-specific notes
Java
Keep the server version equal to or newer than the version that last saved the world. Downgrading can remove blocks, entities, or data. Modded worlds also need the same loader and required mods.
Official Bedrock
The process must preserve the LevelDB db folder. Enter the displayed UDP port when joining. A healthy console start does not guarantee a mismatched client can connect.
PocketMine and Nukkit families
World formats and feature coverage differ from the official Bedrock server. A world exported from the game may require conversion or may not preserve every block and entity.
5. Verify before deleting the backup
- Start the server and confirm it loads the intended world name.
- Join at spawn and inspect several known locations.
- Test inventory, dimensions, permissions, and add-ons.
- Read the console for world-conversion or missing-content warnings.
- Keep the previous backup until players have tested the replacement.