The default configuration of a protection is to be as restrictive as possible to anyone who is not a member of a protection. But it is likely you may want to ease those restrictions for multiple reasons. A possible reason might be to allow anyone to use an EXP grinder. If you don't protect the EXP grinder then people could grief it, but if you fully protect it then you are forced to update the permissions of any player that wants to use it. Instead, you can configure it in a way that allows people to use the EXP grinder without griefing it.

/pr setminlevel <protection name> <permission> <permission level>

allows you to change the minimum level required for a specific permission.

For example, if you want everyone to be able to kill hostile mobs in a protection named "EXPFarm" without being invited: /pr setminlevel EXPFarm kill_hostile none. This sets the minimum required permission level for kill_hostile to "none" meaning that anyone can now kill hostile mobs in this protection.

If you like, you can also be more restrictive on members of your protection: /pr setminlevel EXPFarm build admin. This would mean that you need to have at least an admin permission level in order to build on this protection.

For a full list of levels and permissions you can change, check out the permissions guide.

/pr flag <name> <flag> <true/false>

There are also a number of flags you can change about a protection to make it less protective. By default, creepers and tnt will not do any damage to your protection. If you would like, you can temporarily or permanently disable this or any other flags mentioned in this section.

Here are a list of all flags you can update:

• pvp set this to true to enable PVP in your protection.
• entity_damage_entity set this to true to allow hostile entities to damage other entities. Note that this may allow people to kill your animals in your protection by abusing creepers or skeletons.
• fire_spread set this to true to allow fire to spread and damage blocks.
• mob_griefing set this to true to allow entities to place/break blocks in your protection. Eg: endermen stealing blocks.
• explosion_damage enable this to allow creepers and tnt to do damage to blocks within your protection. You must enable entity_damage_entity to allow them to damage entities too.
• border_piston_protection disable this to allow pistons to push and pull blocks at the border of a protection.
• nether_portal_protection enabled by default, this prevents any portals from being generated in your protection if someone tries to enter your protection through the nether.
• pressure_plate_protection enabled by default, this makes tripwires and pressure plates require the interact permission to activate. Disable this to let anyone use pressure plates and tripwires.
• border_fluid_protection enabled by default, disable this to allow water/lava to flow from outside your protection inside.
• border_tree_protection enabled by default, disable this to allow trees and crops that grow outside your protection to grow inside the borders.

It is recommended you only change the flags of your protection for very specific scenarios or to change them temporarily. Disabling border_fluid_protection in a protection named "MyProtection" might look like: /pr flag MyProtection border_fluid_protection false

/pr configpreset <name> <preset>

There are a few presets you can use to automatically configure your protection in specific ways. Here are all the types:

/pr configpreset <name> default

Your protection is set to this as default. Use this command to configure your protection back to how it was originally if you mess up. The default configuration is the most secure.

/pr configpreset <name> wilderness

All protection measures in your protection are removed to make it similar to the wilderness. The difference between wilderness and a protection with a wilderness preset is that no one else can claim the land.

/pr configpreset <name> public_farm

This will enable interact, kill_friendly, kill_hostile, chest and /pr home for all users. This will also set the minimum level required for building to member (same as default). In general, this would make a good setup for a shared enderman EXP farm or anything similar.

/pr config <name>

Type this command to view the configuration of a protection. You do not need to have any permissions to view this.