Upstream/AuthMeReloaded
1
0
Fork 0
mirror of https://github.com/AuthMe/AuthMeReloaded.git synced 2024-11-29 05:35:15 +01:00
Code Issues Projects Releases Wiki Activity

Mention that settings are located under "limbo" (feedback by Gnat008)

ljacqu 2017-03-26 23:08:02 +02:00
parent c8598099a5
commit 6158ddea6b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Limbo-players.md

@ -27,7 +27,7 @@ Consider the following example:
1. player logs in 1. player logs in
1. we restore limbo properties -> player has walk speed 5 again 1. we restore limbo properties -> player has walk speed 5 again
We try to combat such issues by allowing you to configure how we should restore the limbo properties. For example, you may choose to keep the maximum speed from player and limbo player, or you can define to set "allow flight" always to _true_ when a player logs in. You can configure the behavior for each property in config.yml. We try to combat such issues by allowing you to configure how we should restore the limbo properties. You can find these settings in your config.yml under "limbo". For example, you may choose to keep the maximum speed from player and limbo player, or you can define to set "allow flight" always to _true_ when a player logs in.
Note that restoring the OP status is not configurable. For security reasons, if an unregistered player is OP, he will no longer be OP once he registers & logs in. Similarly, an unregistered player who gets opped will no longer be OP when he logs in. In order to set someone as OP successfully, he needs to be authenticated. Note that restoring the OP status is not configurable. For security reasons, if an unregistered player is OP, he will no longer be OP once he registers & logs in. Similarly, an unregistered player who gets opped will no longer be OP when he logs in. In order to set someone as OP successfully, he needs to be authenticated.