所有权限
To assign permissions to players you must install a permissions plugin, like Luckperms. Below you find a list of permissions that you can assign to players or their permission groups. Please note that if a player has /op, they will have all permissions.
Recommended Permission Setup
You can find a recommended permission setup for players here: Recommended Permission Setup
Player Permissions
These permissions are safe to set for your players.
Numbered Permissions
IMPORTANT:
Replace
<number>with an actual number. Example:lands.lands.<number>-> lands.lands.5If you make changes to numbered permissions and want to synchronize these changes to lands of which the owners are offline: Execute
/lands admin land * syncPermissions. Please note that this is not required. Without executing this command, the limits will automatically update if the land owner is online or once the land owner logs in again.
Stacked Numbered Permissions
By default the highest numbered permission that a player has will define the limit. You can change this by enabling the permission-stacking option in the config.yml file. This will accumulate each limit. Example: A player has lands.lands.5 and lands.lands.4 set. This would result in lands.lands.9.
Numbered Permission Nodes
lands.lands.<number>
Example: lands.lands.5
Description: In how many lands can the player be a member?
NOTE: This does not include owned lands. If you want to set
how many lands the player can own, just set the permission below (lands.ownlands.).
lands.ownlands.<number>
Example: lands.ownlands.2
Description: How many lands can the player own?
lands.chunks.<number>
Example: lands.chunks.75
Description: How many chunks should the player be
able to claim? This is per land.
lands.chunks.support.<number>
Example: lands.chunks.support.5
Description: How many chunks can the player contribute to lands he's member of? Example: lands.chunks.support.5 -> each land in which the player is trusted and not owned by the player, will receive an additional amount of 5 claims.
lands.members.<number>
Example: lands.members.20
Description: Set max members per land. This includes the owner.
lands.areas.<number>
Example: lands.areas.30
Description: Set max "sub areas" per land.
lands.roles.<number>
Example: lands.roles.10
Description: Set max roles per land.
lands.rentals.<number>
Example: lands.rentals.1
Description: Allow the player to rent or buy an amount of areas per land. If set to 0, the player won't be able to rent or buy any areas. If set to 1, the player will only be able to rent or buy one area per land. And so on.
lands.parts.<number>
Example: lands.parts.10
Description: Set the max. amount of disconnected parts for the players owned lands. This includes the initial claim. So setting lands.parts.1, won't do anything. This will only take effect, if the option treat-as-new is disabled in config.yml. This permission allows players to claim a collections of chunks that are disconnected from the original land, but the force-near option will still be enforced once the maximum amount is reached.
lands.free.chunks.<number>
Example: lands.free.chunks.10
Description: The player can claim <number> chunks FOR FREE for each land they own. If they already claimed <number> of chunks this won't have any effect. Please note that an amount of chunks, depending on the "claim-radius" option in config.yml, will always be free. No matter, if this permission has been set or not.
lands.free.lands.<number>
Example: lands.free.lands.1
Description: Set free lands amount (/Lands create).
lands.selection.<number>
Example: lands.selection.1000
Description: Max chunks amount for /Lands selection. The default value is 1000.
lands.camps.<number>
Example: lands.camps.3
Description: Maximum amount of camps.
lands.allies.<number>
Example: lands.allies.3
Description: Maximum amount of allies per land / nation.
lands.enemies.<number>
Example: lands.enemies.3
Description: Maximum amount of enemies per land / nation.
nations.lands.<number>
Example: nations.lands.10
Description: Defines how many lands can be part of the nation of this player.
Command Permissions
Commands wiki page: https://github.com/Angeschossen/Lands/wiki/Commands
Teleportation
The following permissions limit all teleportation initiated by Lands. Players have them by default. However, in some cases the teleportation is initiated by executing a command. In such case they need the permission to use the command as well. You don't need to explicitly set them.
Disabling Teleportation
If you want to disable a teleportation you need to unset the permission in your permissions plugin. Example for LuckPerms: /luckperms group default permission set lands.teleport.sub_area false The value false is important here.
Teleportation Permissions
lands.teleport.chunk
Description: Allow teleportation to claimed chunks via /lands claimlist.
Note: This permission is set by default.
lands.teleport.rentable
Description: Allow teleportation to rentable areas or lands setup for purchase.
Note: This permission is set by default.
lands.teleport.land_spawn
Description: Allow to teleport to a land spawn.
Note: This permission is set by default.
lands.teleport.random_teleport
Description: Allow to random teleport via /lands wild.
Note: This permission is set by default.
lands.teleport.war
Description: Allow to teleport to war spawn via /wars spawn.
Note: This permission is set by default.
lands.teleport.sub_area
Description: Allow to teleport to a sub area.
Note: This permission is set by default.
lands.teleport.unstuck
Description: Allow to teleport via /lands unstuck.
Note: This permission is set by default.
Toggle Natural Flags
These permissions are needed to toggle natural flags like monster spawning for your land.
Toggle Role Flags
These permissions are needed to toggle role flags for your land.
Toggle Personal Flags
Playtime Max Rewards
Only needed if playtime rewards are enabled in the config.
Staff Permissions
These permissions should only be set for your staff.
Bypass Permissions
Moderator Utilities
Administrator Permissions
These permissions should only be set for administrators.