Multiverse: several worlds on one server

A vanilla server loads exactly one world (plus its matching Nether and End). If you want a survival world and a creative world and a minigames world on the same server, all loaded at once with a command to hop between them, that's what Multiverse does. This guide covers the core ideas — create, import, teleport — and, just as importantly, how Multiverse relates to the panel's Worlds page and where the sharp edges are.

How it relates to the Worlds page

This trips people up, so let's be clear about who does what:

• The panel's Worlds page uploads or generates world folders, shows a 3D map, and the level-name property picks the one world your server treats as the default (where players spawn on login). That's vanilla behavior — one main world.
• Multiverse is a plugin that keeps several worlds loaded at the same time and adds /mv commands to travel between them. It doesn't replace level-name — your level-name world is still the default login world; Multiverse manages the extras alongside it.

The two work together: you can upload a world with the Worlds page, then import it into Multiverse so it's loaded and reachable.

Install and the core commands

Install Multiverse-Core from the Plugins page and restart. Then the four commands you'll use constantly (run in console or in-game as an operator):

So a typical setup is: /mv create creative NORMAL, then /mv tp creative to visit it. To adopt a world you uploaded via the Worlds page, use /mv import <folder-name> NORMAL with the exact folder name.

💡 Tip: /mv create and /mv import are different jobs. Create makes a new world from scratch. Import adopts a world folder that already exists on the server — use it for uploaded worlds, or worlds that existed before you installed Multiverse.

The permission note

/mv commands are powerful, so out of the box only operators can run them. To let staff use them without full op, grant the Multiverse permission nodes through LuckPerms, and keep world-destroying commands (below) to admins only.

The sharp edges — read before you run

Multiverse can delete and regenerate worlds, and those commands do exactly what they say — permanently. This is the "world surgery" moment:

• /mv remove <name> — unregisters a world from Multiverse but leaves the folder on disk. Reversible.
• /mv delete <name> — deletes the world's files. Not reversible.
• /mv regen <name> — wipes and regenerates the world. Everything built there is gone.

⚠️ Heads up: Take a backup before any delete, regen, or bulk world change. These commands remove files immediately with no undo. On the free plan, backups store to your own Google Drive — connect it before you start.

A second caveat about your main world: your level-name world is special (it's where players log in). Don't delete or regen it casually. If you need to reset it, the panel's Worlds page has a safer recipe — stop the server and rename the folder rather than deleting it.

What Multiverse-Core alone does not do

Core handles worlds and travel. Two things people expect that need separate modules (extra jars from the Plugins page):

• Separate inventories per world. By default a player carries the same inventory everywhere. Keeping survival and creative inventories apart needs Multiverse-Inventories.
• Custom Nether/End portal linking between your worlds needs Multiverse-NetherPortals.

Install those only if you need them — Core is enough to create worlds and teleport.

🎯 Good to know: Every loaded world uses memory continuously, whether anyone's in it or not. On the free plan's shared RAM, keep the world count and their sizes modest, and watch for out-of-memory trouble. A handful of small worlds is fine; a dozen large ones is not.

Because command syntax and module names have changed across Multiverse versions, check the current Multiverse documentation if a command doesn't behave as written here.

Verify it works

Run /mv list — your worlds should be listed. /mv tp <name> should drop you into the world you name. After a restart, /mv list should still show every world (Multiverse remembers them), and players should spawn in your level-name world on login as before.

Troubleshooting

• /mv import says the world doesn't exist — the folder name must match exactly, and the folder must contain level.dat. Check the name on the Worlds page or in the File Manager.
• Everyone shares one inventory across worlds — that's default behavior; install Multiverse-Inventories to separate them.
• Ran /mv delete and lost a world — restore from your backup. This is exactly why the backup step exists.
• Server slow with several worlds loaded — each costs RAM and CPU. Reduce the number of loaded worlds, or profile with spark. See Fixing Minecraft lag.

Next steps

• Manage your Minecraft worlds
• LuckPerms basics
• Backups
• Fixing Minecraft lag