Upstream/Multiverse-Core
1
0
Fork 0
mirror of https://github.com/Multiverse/Multiverse-Core.git synced 2024-11-22 02:25:41 +01:00
Code Issues Projects Releases Wiki Activity

Updated FAQ (markdown)

lithium3141 2011-11-02 15:11:58 -07:00
parent 4e0300f581
commit d1b55b4ac2
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
FAQ.md

@ -67,4 +67,12 @@ With PermissionsBukkit (just an example, you should be able to do the same with
## <a name="firstspawn" href="#wiki-firstspawn">•</a>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.
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.
## <a name="badapi" href="#wiki-badapi">•</a>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.