Added RTP on death | More controle over rtp settings | Rtp-admin status command
This update contains 3 parts: rtp-on-death, config restrictions, and rtp-admin status command.
RTP On Death
Just like the title, the plugin now supports randomly teleporting players when they die (or more specifically, they will respawn in a random location). This setting is static, meaning it applies to the entire server, and not one config. You can also specify if a permission node (jakesrtp.rtpondeath) is required for this to take effect, or if it applies to everyone regardless. Also, you can choose if it respects bed spawns. If respect-beds is set to true, players that have a home bed will indeed spawn at the bed and not randomly. Players who do not have a bed spawn though, will spawn randomly.
Example use: Combined this with rtp-on-first-join, and you can have a server with no true spawn point. When a player joins, they will randomly spawn somewhere in the world (you configure where they can land), and until they have a bed, every death takes them again, to a new random location.
Config restrictions
These are restrictions that you can impose on the rtp-configs. These are the additions with a brief description of what they do:
• Command-enabled ~ If true, this config can be used with the
/rtp command. If set to false, the only way to rtp with this config is if the teleport is caused by an admin override command, or a built in static condition (on first join or on death)
• Require-explicit-permission ~ If set to true, to be able to use the rtp config, the user must have a specific permission. This allows you to create multiple configs that apply to the same world, and you can choose which configs people can use by giving them permissions.
• Priority ~ If two configs overlap, the one with the higher priority will be chose.
Example use: You create 3 rtp-configs, one called
First-Join, one called
Noob, and one called
King. Set
First-Join to have its command disabled, that way users can never call it, and you can make sure they only way that it gets used is when a player joins for the first time. Then make the
Noob have a radius of 500 blocks, and require a specif permission which you give to the default rank. Then you make
King have a radius of 2500 blocks, and require a specific permission that you give to your highest rank, making sure to remove the permission to use
Noob from the highest rank. Now when a new player runs the rtp command, they teleport 500 blocks max, while a high rank player can teleport 2500 blocks max. (this specific example can also be done using priorities instead of permissions)
Rtp-Admin status
The command
/rtp-admin status <config> has existed in spirit for some time now, but never was truly implemented. Now though, you can type that command and put a config name for <config> and it will tell you all about it. You can also enter
#static to see the static settings.
Oh, and don't forget,
/rtp-admin reload still exists and can be used to quickly reload the config while you are changing up the settings!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Note: The config version has been changed again, so make sure to copy over your old config valued. Because I have made so many changes to the config so far, I plan on making the config update easier in the future. Sorry for the inconvenience this has caused.