Eric Stokes edited this page Mar 6, 2016 · 40 revisions

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 happened to the rest of MultiVerse?

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

I can't load my SKYLANDS worlds!

Mojang removed the skyland code in Minecraft 1.0.0, replacing it with "the End" chapter of the game. That included (1) floating island terrain, (2) a gray noontime sky, (3) clouds drawn at very low Y levels. You have two choices.

Choice A: Use a terrain generator plugin like SkylandsPlus to allow players to continue to explore by generating additional chunks. This may cause tearing at the explored edges as it's not the same generator.

Choice B: If your skylands were already pretty mapped out, then use a border plugin like WorldBorder to stop any more expansion of the world.

In either case, edit your world configuration to use a NORMAL environment instead of the old missing SKYLAND environment type. Refine your monster spawning settings to suit your tastes. If you want permanent day, plugins like TimeShift can help you with that, too.

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

Yes. Multiverse-Inventories is a plugin designed for this purpose.

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.

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"
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.

Why can't I load any other Multiverse plugins than Core?

A lot of people have trouble with the splitting of Multiverse out into several different plugins. Often, we'll see people who try to update a non-Core plugin (like Multiverse-Portals) without also updating their Multiverse-Core. This causes an error on startup that starts with:

2011-11-02 19:29:40 [SEVERE] Could not load 'plugins\Multiverse-Portals.jar' in folder 'plugins': 
java.lang.NoClassDefFoundError: com/onarandombox/MultiverseCore/api/MVPlugin

This means that you need to update your Multiverse-Core to the latest Awesome Build. This is true even if Multiverse-Core is working fine right now - new versions of Portals and other MV plugins depend on the newest features in Core, so making sure they're all up to date is critical.

Why do any Multiverse commands error out?

We recently updated the library handling commands for the Multiverse plugins. This library is coordinated across several other plugins, including OpenWarp, ChatSuite, TeleportSuite, and Privileges. If you use any of these plugins, you also need their latest versions - sometimes still in development - so that the library works properly across all plugins.

You most likely have this issue if you see an error of the form:

2011-12-19 12:12:34 [SEVERE] null
org.bukkit.command.CommandException: Unhandled exception executing command 'mvtp' in plugin Multiverse-Core v2.2-b418
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:165)
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:378)
    at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:757)
    at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:722)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:715)
    at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:180)
    at net.minecraft.server.Packet3Chat.a(Packet3Chat.java:33)
    at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:93)
    at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:550)
    at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:527)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)
Caused by: java.lang.NoSuchMethodError:
    at com.onarandombox.MultiverseCore.MultiverseCore.onCommand(MultiverseCore.java:431)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 14 more

The important error here is the NoSuchMethodError caused by commandhandler - if you see this, update all your other plugins!

Multiverse crashes my server while adjusting my spawn! Stop it!

The latest development builds include extra options to stop Multiverse from attempting to auto-adjust the spawn point, which is especially useful in Skylands or empty (NullTerrain) worlds. Generating a new world without spawn adjustment is a two-step process.

First, create the world with the normal mv create command, but add -n to the end of it. For NullTerrain, this might look something like:

mv create empty_world normal -g NullTerrain -n

The -g flag indicates that Multiverse should use the NullTerrain generator, and the -n flag tells Multiverse to not adjust the spawn for this world. Second, once the world is created, immediately run the following command to stop Multiverse from adjusting the spawn in the future:

mvm set adjustspawn false empty_world

This will tell Multiverse to never adjust the spawn, even on world reload or server restart.

Mods/OPs/Players keep having their game mode switched!

New builds of Multiverse-Core include an extra permission to prevent automatic mode-switching. This permission takes the form:


With this new permission, server owners can pick particular users to ignore some (or all) of the game mode settings on each world when teleporting between them. For example, a player with mv.bypass.gamemode.* could be an admin, keeping their creative mode setting even in survival worlds. Just set the right permissions in your preferred plugin and you're good to go.

Can you make plugins disable-able/configurable per world?

Unless something has changed with Spigot, this still isn't possible.

Plugins are still scoped at the Server level, meaning once it's loaded it's active for all worlds. Each plugin is responsible for supporting multi-world functions, but there are some permissions plugins that support multiworld command disabling.