# Effectively when this setting is 'true': the tree is flattened, and rules applied afterwards,

# and when this setting is 'false':, the rules are just applied during each step of the traversal.

post-traversal-inheritance-sort: false



# +----------------------------------------------------------------------------------------------+ #

# | Permission resolution settings | #

# +----------------------------------------------------------------------------------------------+ #



# If users on this server should have their global permissions applied.

# When set to false, only server specific permissions will apply for users on this server

include-global: true



# If users on this server should have their global world permissions applied.

# When set to false, only world specific permissions will apply for users on this server

include-global-world: true



# If users on this server should have global (non-server specific) groups applied

apply-global-groups: true



# If users on this server should have global (non-world specific) groups applied

apply-global-world-groups: true



# +----------------------------------------------------------------------------------------------+ #

# | Meta lookup settings | #

# +----------------------------------------------------------------------------------------------+ #



# Defines how meta values should be selected.

#

# - Possible options:

# => inheritance Selects the meta value that was inherited first

# => highest-number Selects the highest numerical meta value

# => lowest-number Selects the lowest numerical meta value

meta-value-selection-default: inheritance



# Defines how meta values should be selected per key.

meta-value-selection:

# max-homes: highest-number



# +----------------------------------------------------------------------------------------------+ #

# | Inheritance settings | #

# +----------------------------------------------------------------------------------------------+ #



# If the plugin should apply wildcard permissions.

#

# - If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered

# permissions matching the wildcard.

apply-wildcards: true



# If LuckPerms should resolve and apply permissions according to the Sponge style implicit wildcard

# inheritance system.

#

# - That being: If a user has been granted "example", then the player should have also be

# automatically granted "example.function", "example.another", "example.deeper.nesting",

# and so on.

apply-sponge-implicit-wildcards: false



# If the plugin should parse regex permissions.

#

# - If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the

# node, and resolve & apply all registered permissions matching the regex.

apply-regex: true



# If the plugin should complete and apply shorthand permissions.

#

# - If set to true, LuckPerms will detect and expand shorthand node patterns.

apply-shorthand: true



# If the plugin should apply Bukkit child permissions.

#

# - Plugin authors can define custom permissions structures for their plugin, which will be resolved

# and used by LuckPerms if this setting is enabled.

apply-bukkit-child-permissions: true



# If the plugin should apply Bukkit default permissions.

#

# - Plugin authors can define permissions which should be given to all users by default, or setup

# permissions which should/shouldn't be given to opped players.

# - If this option is set to false, LuckPerms will ignore these defaults.

apply-bukkit-default-permissions: true



# If the plugin should apply attachment permissions.

#

# - Other plugins on the server are able to add their own "permission attachments" to players.

# - This allows them to grant players additional permissions which last until the end of the

# session, or until they're removed.

# - If this option is set to false, LuckPerms will not include these attachment permissions when

# considering if a player should have access to a certain permission.

apply-bukkit-attachment-permissions: true



# +----------------------------------------------------------------------------------------------+ #

# | Extra settings | #

# +----------------------------------------------------------------------------------------------+ #



# Allows you to set "aliases" for the worlds sent forward for context calculation.

#

# - These aliases are provided in addition to the real world name. Applied recursively.

# - Remove the comment characters for the default aliases to apply.

world-rewrite:

# world_nether: world

# world_the_end: world



# Define special group weights for this server.

#

# - Group weights can also be applied directly to group data, using the setweight command.

# - This section allows weights to be set on a per-server basis.

group-weight:

# admin: 10









# +----------------------------------------------------------------------------------------------+ #

# | | #

# | FINE TUNING OPTIONS | #

# | | #

# | A number of more niche settings for tweaking and changing behaviour. The section also | #

# | contains toggles for some more specialised features. It is only necessary to make changes to | #

# | these options if you want to fine-tune LuckPerms behaviour. | #

# | | #

# +----------------------------------------------------------------------------------------------+ #



# +----------------------------------------------------------------------------------------------+ #

# | Server Operator (OP) settings | #

# +----------------------------------------------------------------------------------------------+ #



# Controls whether server operators should exist at all.

#

# - When set to 'false', all players will be de-opped, and the /op and /deop commands will be

# disabled.

enable-ops: true



# Enables or disables a special permission based system in LuckPerms for controlling OP status.

#

# - If set to true, any user with the permission "luckperms.autoop" will automatically be granted

# server operator status. This permission can be inherited, or set on specific servers/worlds,

# temporarily, etc.

# - Additionally, setting this to true will force the "enable-ops" option above to false. All users

# will be de-opped unless they have the permission node, and the op/deop commands will be

# disabled.

# - It is recommended that you use this option instead of assigning a single '*' permission.

auto-op: false



# Defines if "opped" players should be able to use all LuckPerms commands by default.

#

# - Set to false to only allow users who have the permissions access to the commands

commands-allow-op: true



# +----------------------------------------------------------------------------------------------+ #

# | Vault integration settings | #

# +----------------------------------------------------------------------------------------------+ #



# If Vault lookups for offline players on the main server thread should be enabled.

#

# LuckPerms has a "catch" for plugins attempting to perform unsafe offline player data lookups

# from the main server thread. This catch raises an exception (causes an error to occur) when unsafe

# lookups are made, instead of allowing the lookup to happen, which would likely cause the server

# to lag.

#

# However, if you're willing to accept the consequences, the catch can be disabled by setting this

# option to 'true.

vault-unsafe-lookups: false



# Controls which group LuckPerms should use for NPC players when handling Vault requests.

#

# - As NPCs aren't actually real players, LuckPerms does not load any user data for them. This

# becomes an issue when plugins want to check for their permissions using Vault.

# - As a solution, Vault checks for NPCs fallback to a group, which is defined below.

vault-npc-group: default



# Controls how LuckPerms should consider the OP status of NPC players when handing Vault requests.

#

# - If you want NPCs to have the same permissions as "normal" players, set this option to false.

# - If you want NPCs to have OP status, set this option to true.

vault-npc-op-status: false



# If the vault-server option below should be used.

#

# - When this option is set to false, the server value defined above under "server" is used.

use-vault-server: false



# The name of the server used within Vault operations.

#

# - If you don't want Vault operations to be server specific, set this to "global".

# - Will only take effect if use-vault-server is set to true above.

vault-server: global



# If global permissions should be considered when retrieving meta or player groups

vault-include-global: true



# If Vault operations should ignore any world arguments if supplied.

vault-ignore-world: false



# +----------------------------------------------------------------------------------------------+ #

# | Miscellaneous (and rarely used) settings | #

# +----------------------------------------------------------------------------------------------+ #



# If LuckPerms should produce extra logging output when it handles logins.

#

# - Useful if you're having issues with UUID forwarding or data not being loaded.

debug-logins: false



# If LuckPerms should allow usernames with non alphanumeric characters.

#

# - Note that due to the design of the storage implementation, usernames must still be 16 characters

# or less.

allow-invalid-usernames: false



# If LuckPerms should allow a users primary group to be removed with the 'parent remove' command.

#

# - When this happens, the plugin will set their primary group back to default.

prevent-primary-group-removal: false



# If LuckPerms should update the list of commands sent to the client when permissions are changed.

update-client-command-list: true



# If LuckPerms should attempt to resolve Vanilla command target selectors for LP commands.

# See here for more info: https://minecraft.gamepedia.com/Commands#Target_selectors

resolve-command-selectors: false