Updated World properties (markdown)

FernFerret 2012-01-01 16:06:47 -08:00
parent 89fa7f6d07
commit a705d4864f

@ -25,7 +25,21 @@ Here are the various properties of worlds that can be set in `worlds.yml`. __Nor
## <a name="perms" href="#wiki-perms"></a>World Permissions
You can easily control who can enter various worlds in Multiverse 2. To allow people access to a world, simply grant them access to `multiverse.access.WORLDNAME` where WORLDNAME is the name of the world. By default (with PermissionsBukkit) people _can_ enter newly created worlds. You can give users `multiverse.access.*` to let them access all worlds, or set the same to false to deny access to all worlds.
*__NOTE:__ If you have `enforceaccess` set to `false` in the Multiverse-Core `[[config.yml]]` then _anyone_ can enter _any world_. This is done to support people who are using ops.txt. If you are using a permissions plugin, you will most likely want to set `enforceaccess: true`*
## <a name="perms" href="#wiki-perms"></a>Default Spawn World
Multiverse 2.2+ allows you to set what world users will spawn in. This does _not_ have to be the world that is in `server.properties`. To do this, make sure you have the following 2 values set in your `[[config.yml]]`. You can set this value ingame by using `/mv conf firstspawnoverride true` and `/mv conf firstspawnworld myworld`. We advise against editing the file, but here is the clip:
```
...
# If true, this will ensure players, on first spawn, go to the spawn
# that you've set with Multiverse. Set to false if you use another
# spawn plugin.
firstspawnoverride: true
# This is the world you want players to spawn in. It does *NOT*
# have to be the world in server.properties!
firstspawnworld: world
...
```
## <a name="animals" href="#wiki-animals"></a>Animals
### Spawning