FAQ

•What is Multiverse-Core?

Multiverse-Core is a World management plugin. What this means is you can use it to create, delete and manage your different worlds in a Bukkit Server. See the Basic Multiverse Tutorial for a very brief overview!

•Why does it have the '-Core' at the end?

MultiVerse (note the capital V which is no longer in the name Multiverse-Core) was the old version, but a lot has changed. Multiverse-Core is a part of the Multiverse 2 package. What we decided to do was break up MultiVerse into several smaller plugins. This way we avoid plugin conflicts. For example, if you, the server admin, want to use a different portal plugin because you think ours sucks, you now can install just Multiverse-Core.

•What happend to the rest of MultiVerse?

It has been divided into several plugins. See the Plugins of Multiverse 2

•Is there a way to have each world's inventories separate from each other?

Yes. MultiInv is a plugin designed for this purpose. http://dev.bukkit.org/server-mods/multiinv/

•After using MultiInv, a Player keeps dying in a specific world!

Go into that player's file and set their health to a non-0 value. It looks like there is a pull request to fix this here.

•Does Multiverse import my main world (and main Nether)?

No. We do this so you can have your main world use a generator, or be a skylands. Simply type /mv import world normal and optionally /mv import world_nether (or whatever the name of your primary world is).

•Multiverse says it can't take me to a place because it's unsafe! I know it is!

Sometimes Minecraft sets the spawn at unacceptable locations (way below the ground) and the Minecraft server will take over spawning of you. MV2 handles this for you so it'll never take you to an unsafe location. However this creates a conflict. To resolve it, just follow these instructions:

/mvtp myworld
"That world is unsafe"
/mvconfirm
You are teleported to the world anyway
/mv set spawn
Now the spawn has been set to an acceptable place

•1.8: How does Multiverse handle creative mode?

Multiverse has added a new property, mode, to the list of properties on a world. This means you can set the mode on a per-world basis! To change a world to creative, type:

/mvm set mode creative

The world will become a creative world, and any players will be set to creative mode when they enter the world. To set it back, simply type:

/mvm set mode survival

Keep in mind that ops can enter creative mode in a survival world with the /gamemode command. Be careful to only op players that you trust!

•Why did you change from the simple teleport permissions?

The teleport command was becoming immensely powerful and some people don't want their users to have all this power. It is a little bit more complex, but allows for much more flexible teleportation.

Now, Each Destination type gets it's own 2 permissions (These are listed on the Destinations page). You can still give a user multiverse.teleport.* to give them global teleport access for themself and others.

If you just want them to have teleport rights to every destination type for themself: multiverse.teleport.self.*
HINT: This is the same as the old multiverse.core.tp.self permission!

This also allows for very advanced setups like "I want people to be able to teleport only themselves everywhere except other players! Cuz that's cheating!":

With PermissionsBukkit (just an example, you should be able to do the same with your perms plugin)

> perm group setperm moderator multiverse.teleport.other.* false
09:56:46 [INFO] Group moderator now has multiverse.teleport.other.* = false.

> perm group setperm moderator multiverse.teleport.self.* true
09:56:47 [INFO] Group moderator now has multiverse.teleport.self.* = true.

> perm group setperm moderator multiverse.teleport.self.pl false
09:56:48 [INFO] Group moderator now has multiverse.teleport.self.pl = false.

•When a player logs on the first time, they spawn in the wrong place!

Several users have reported a problem where they changed their server spawn using /mv set spawn, but when new users log on for the first time, they don't go to that spawn.

This is a problem with CraftBukkit - for brand new players, custom spawns set by Multiverse don't override the default Minecraft/Bukkit spawn. Without a bugfix, Multiverse can't change this behavior - for now, we all just have to live with it.