Fixed first time spawn FAQ

Jad 2019-09-01 01:35:14 -05:00
parent d74c8adf39
commit 706c322201

25
FAQ.md

@ -15,16 +15,13 @@ Mojang removed the skyland code in Minecraft 1.0.0, replacing it with "the End"
**Choice B:** If your skylands were already pretty mapped out, then use a border plugin like [WorldBorder](http://dev.bukkit.org/server-mods/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](http://dev.bukkit.org/server-mods/timeshift/) can help you with that, too.
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 a permanent day, plugins like [TimeShift](http://dev.bukkit.org/server-mods/timeshift/) can help you with that, too.
## Is there a way to have each world's inventories separate from each other?
Yes. [Multiverse-Inventories](https://github.com/Multiverse/Multiverse-Inventories/wiki) 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](https://github.com/Pluckerpluck/MultiInv/pull/2).
Yes. [Multiverse-Inventories](https://github.com/Multiverse/Multiverse-Core/wiki/Home-(Inventories)) is a plugin designed for this purpose.
## 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:
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"
@ -34,7 +31,7 @@ Sometimes Minecraft sets the spawn at unacceptable locations (way below the grou
*Now the spawn has been set to an acceptable place*
## 1.8: How does Multiverse handle creative mode?
## 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
@ -47,11 +44,11 @@ Keep in mind that **ops can enter creative mode in a survival world** with the `
## 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.
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|Destinations]] 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.
Now, Each [[Destination|Destinations]] 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 themselves **and** others.
If you just want them to have teleport rights to every destination type for themself: `multiverse.teleport.self.*`
If you just want them to have teleport rights to every destination type for themselves: `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!":
@ -68,9 +65,11 @@ With PermissionsBukkit (just an example, you should be able to do the same with
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.
1. Ensure "firstspawnoverride" is 'true' in your [[config.yml]].
2. Ensure "firstspawnworld" is set to the correct world (do not put quotes around it, simply put the directory (world) name. The default value is `world`.
3. If you have Essentials, ensure you don't have the "EssentialsSpawn" jar. If for whatever reason you want to keep EssentialsSpawn for the other features it provides, you can simply modify Essentials config.yml and modify "spawnpoint" under "newbies:" to the world you desire.
4. In the world you specified, set the spawnpoint using `/mv setspawn`.
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:
@ -133,4 +132,4 @@ With this new permission, server owners can pick particular users to ignore some
## Can you make plugins disable-able/configurable per world?
Unless something has changed with Spigot, this still isn't possible.
Plugins are still [scoped](http://en.wikipedia.org/wiki/Scope_(computer_science)) 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.
Plugins are still [scoped](http://en.wikipedia.org/wiki/Scope_(computer_science)) 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 multi-world command disabling.