Updated Spawn handling (markdown)

ljacqu 2016-05-28 12:09:42 +02:00
parent 132eb0331a
commit 33cb2fb98e

@ -12,7 +12,7 @@ The following settings have an influence on the spawn feature, listed by priorit
--
Related: `settings.restrictions.SaveQuitLocation` must be true for the quit location to be saved
## Spawn priority
## Spawn Priority
Spawn priority is defined in `settings.restrictions.spawnPriority` (see above), i.e. this setting defines from where the spawn definition should be taken. Possible values:
- **authme** — Spawn points defined in spawn.yml (AuthMe folder). See below for details.
@ -22,7 +22,7 @@ Spawn priority is defined in `settings.restrictions.spawnPriority` (see above),
Example:
```yaml
spawnPriority: 'essentials,authme,default`
spawnPriority: 'essentials,authme,default'
```
If Essentials is available, the spawn defined in Essentials is used. If not, the AuthMe spawn is used as second choice. If this also fails, the default is taken.
@ -52,4 +52,6 @@ Players who have never played on the server before are teleported to the **first
- `/authme spawn` teleports you to the AuthMe spawn point
- `/authme setspawn` sets the AuthMe spawn point
- `/authme firstspawn` teleports you to the AuthMe first spawn point
- `/authme setfirstspawn` sets the AuthMe first spawn point
- `/authme setfirstspawn` sets the AuthMe first spawn point
Permission nodes for the commands are listed on the [command list page](https://github.com/AuthMe-Team/AuthMeReloaded/blob/master/docs/commands.md).