FAQ - IzzelAliz/Multiverse-Core GitHub Wiki

什么是Multiverse-Core?

Multiverse-Core是一个管理世界的插件。意思就是你可以用它来创建，删除或管理你在服务器内的不同世界，在Basic Multiverse Tutorial 找到一个非常简短的简介！

为什么它在结尾有'-Core'？

MultiVerse (注意大写的V，在Multiverse-Core中已被删除) 是它的老版本，但是有不少已经被改变了。Multiverse-Core 是Multiverse 2 package的一部分。我们决定做的是把MultiVerse变成several smaller plugins几个更小的插件。这样我们可以避免插件冲突。举例说，如果作为服务器管理员的你，想要使用其他的传送插件，因为你认为我们的很烂，你可以只选择安装Multiverse-Core。

MultiVerse的剩余部分发生了什么改变？

它被分为了几个插件。请看Plugins of Multiverse 2。

我不能加载SKYLANDS(空岛)世界！

Mojang 在 Minecraft 1.0.0中删除了空岛的代码，将它换成了"the End"(末地)。这包括了: 1.浮空岛地形 2.一个灰色的中午的天空 3.位置非常低的云。你有两个选择

选项A： 用地形生成类插件，例如SkylandsPlus 通过附加的区块允许玩家继续探索，如此做可能因使用不同的生成器而使探索过的地图边界出现断层。

选项B： 如果你的空岛在地图边缘，那么使用类似WorldBorder 的插件来阻止世界的拓展。

在任何情况下，将这个世界配置中的世界类型从被删除的老版的'SKYLAND'(空岛)改为'NORMAL'(普通)。改善怪物生成来满足你的需求。如果你想要时间永远停留在某一刻，类似TimeShift 的插件也可以帮助你。

有不同的有没有办法分开存储每个世界的物品？

是的，有。 Multiverse-Inventories是一个能满足这种需求的插件。

在使用MultiInv后，一个玩家一直在一个特定的世界死亡！

前往那个玩家的资料然后设定他的生命值为一个非零的数值。看起来这儿有人发请求修复这个漏洞了 here.

Multiverse说他不能带我去一个不安全的地方，但我知道那里很安全！

有些情况下Minecraft会在一些让人难以接受的地方设置出生点(地下)然后Minecraft服务器会接管你的出生。MV2会为你处理这个问题，所以你永远不会被传送至一个不安全的地点。但是这造成了一个冲突。通过以下步骤来解决这个问题： /mvtp myworld
"That world is unsafe(那个世界不安全)"
/mvconfirm
You are teleported to the world anyway(总而言之你被传送到了那个世界)
/mv set spawn
现在那个世界的出生地被设置在了一个可以接受的地方

1.8: Multiverse怎样处理创造模式？

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:
com.pneumaticraft.commandhandler.CommandHandler.locateAndRunCommand(Lorg/bukkit/command/CommandSender;Ljava/util/List;Z)Z
    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:

mv.bypass.gamemode.WORLD_NAME

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.