Added vanish plugin support, sensor limitation per permissions, and a rpslist command.
Added
- /rpslist [player] - Grab a players sensors, or your own. Player argument is optional.
- rpslist permissions "rps.list" default true, and "rps.list.player" default OP for grabbing other players sensors.
- RPS Limiter ranks/permission sets. Limit the amount of sensors a player can place, more info down below.
- Vanish detection supported by SuperVanish, PremiumVanish, VanishNoPacket and a few more vanish plugins. Works alongside the same way as if a player was invisible with potions, Invisible Entities Trigger will still reveal you so disable that trigger permission.
- New language node "lang_restriction_place_limit"
Whats Next?
- Shift-Clicking Hostile/Peaceful mobs trigger will open a new menu where you can limit to specific Hostile/Peaceful mobs. Only wanting horses for example, you would Shift-Click Peaceful and select the horse, and only horses will be enabled.
rps.limiter Permissions in config file
After loading up the plugin, In the config.yml file you will find a node section "rps.limiter", in this section if a new config.yml file is generated you will see something like below, if not you will see a single default one generated.
Code (Text):
limiter:
player:
amount: 40
default: true
admin:
amount: -1
default: op
This will create new permissions based off the names you give it. "rps.limiter.player" for example is the permission key for the first one, "rps.limiter.admin" for the other one. "default: true" is so that every starting player has the permission set to TRUE by default (duh), any limiter rank added without one will be given the default permission of OP (allowed defaults are: true, false, op, not op). The amount can be any integer, and
-1 represents unlimited. If an amount is not specified it is automatically set to -1. Server OP's will always have unlimited no matter their permission level.
If there are no limiter "groups/ranks" in the config file players will be able to place unlimited sensors and a "rps.limiter.default" rank will be generated in the config file.
Note: Permissions are checked in descending order so technically you do not need to remove a smaller amount permission when adding a greater amount permission. (for people who have permission stores)