· 4 years ago · May 17, 2021, 05:56 PM
1####################################################################################################
2# +----------------------------------------------------------------------------------------------+ #
3# | __ __ ___ __ __ | #
4# | | | | / ` |__/ |__) |__ |__) |\/| /__` | #
5# | |___ \__/ \__, | \ | |___ | \ | | .__/ | #
6# | | #
7# | https://luckperms.net | #
8# | | #
9# | WIKI: https://luckperms.net/wiki | #
10# | DISCORD: https://discord.gg/luckperms | #
11# | BUG REPORTS: https://github.com/lucko/LuckPerms/issues | #
12# | | #
13# | Each option in this file is documented and explained here: | #
14# | ==> https://luckperms.net/wiki/Configuration | #
15# | | #
16# | New options are not added to this file automatically. Default values are used if an | #
17# | option cannot be found. The latest config versions can be obtained at the link above. | #
18# +----------------------------------------------------------------------------------------------+ #
19####################################################################################################
20
21# +----------------------------------------------------------------------------------------------+ #
22# | | #
23# | ESSENTIAL SETTINGS | #
24# | | #
25# | Important settings that control how LuckPerms functions. | #
26# | | #
27# +----------------------------------------------------------------------------------------------+ #
28
29# The name of the server, used for server specific permissions.
30#
31# - When set to "global" this setting is effectively ignored.
32# - In all other cases, the value here is added to all players in a "server" context.
33# - See: https://luckperms.net/wiki/Context
34server: global
35
36# If the servers own UUID cache/lookup facility should be used when there is no record for a player
37# already in LuckPerms.
38#
39# - When this is set to 'false', commands using a player's username will not work unless the player
40# has joined since LuckPerms was first installed.
41# - To get around this, you can use a player's uuid directly in the command, or enable this option.
42# - When this is set to 'true', the server facility is used. This may use a number of methods,
43# including checking the servers local cache, or making a request to the Mojang API.
44use-server-uuid-cache: false
45
46
47
48
49# +----------------------------------------------------------------------------------------------+ #
50# | | #
51# | STORAGE SETTINGS | #
52# | | #
53# | Controls which storage method LuckPerms will use to store data. | #
54# | | #
55# +----------------------------------------------------------------------------------------------+ #
56
57# How the plugin should store data
58#
59# - The various options are explained in more detail on the wiki:
60# https://luckperms.net/wiki/Storage-types
61#
62# - Possible options:
63#
64# | Remote databases - require connection information to be configured below
65# |=> MySQL
66# |=> MariaDB (preferred over MySQL)
67# |=> PostgreSQL
68# |=> MongoDB
69#
70# | Flatfile/local database - don't require any extra configuration
71# |=> H2 (preferred over SQLite)
72# |=> SQLite
73#
74# | Readable & editable text files - don't require any extra configuration
75# |=> YAML (.yml files)
76# |=> JSON (.json files)
77# |=> HOCON (.conf files)
78# |=> TOML (.toml files)
79# |
80# | By default, user, group and track data is separated into different files. Data can be combined
81# | and all stored in the same file by switching to a combined storage variant.
82# | Just add '-combined' to the end of the storage-method, e.g. 'yaml-combined'
83#
84# - A H2 database is the default option.
85# - If you want to edit data manually in "traditional" storage files, we suggest using YAML.
86storage-method: h2
87
88# The following block defines the settings for remote database storage methods.
89#
90# - You don't need to touch any of the settings here if you're using a local storage method!
91# - The connection detail options are shared between all remote storage types.
92data:
93
94 # Define the address and port for the database.
95 # - The standard DB engine port is used by default
96 # (MySQL: 3306, PostgreSQL: 5432, MongoDB: 27017)
97 # - Specify as "host:port" if differs
98 address: localhost
99
100 # The name of the database to store LuckPerms data in.
101 # - This must be created already. Don't worry about this setting if you're using MongoDB.
102 database: minecraft
103
104 # Credentials for the database.
105 username: root
106 password: ''
107
108 # These settings apply to the MySQL connection pool.
109 # - The default values will be suitable for the majority of users.
110 # - Do not change these settings unless you know what you're doing!
111 pool-settings:
112
113 # Sets the maximum size of the MySQL connection pool.
114 # - Basically this value will determine the maximum number of actual
115 # connections to the database backend.
116 # - More information about determining the size of connection pools can be found here:
117 # https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
118 maximum-pool-size: 10
119
120 # Sets the minimum number of idle connections that the pool will try to maintain.
121 # - For maximum performance and responsiveness to spike demands, it is recommended to not set
122 # this value and instead allow the pool to act as a fixed size connection pool.
123 # (set this value to the same as 'maximum-pool-size')
124 minimum-idle: 10
125
126 # This setting controls the maximum lifetime of a connection in the pool in milliseconds.
127 # - The value should be at least 30 seconds less than any database or infrastructure imposed
128 # connection time limit.
129 maximum-lifetime: 1800000 # 30 minutes
130
131 # This setting controls how frequently the pool will 'ping' a connection in order to prevent it
132 # from being timed out by the database or network infrastructure, measured in milliseconds.
133 # - The value should be less than maximum-lifetime and greater than 30000 (30 seconds).
134 # - Setting the value to zero will disable the keepalive functionality.
135 keepalive-time: 0
136
137 # This setting controls the maximum number of milliseconds that the plugin will wait for a
138 # connection from the pool, before timing out.
139 connection-timeout: 5000 # 5 seconds
140
141 # This setting allows you to define extra properties for connections.
142 #
143 # By default, the following options are set to enable utf8 encoding. (you may need to remove
144 # these if you are using PostgreSQL)
145 # useUnicode: true
146 # characterEncoding: utf8
147 #
148 # You can also use this section to disable SSL connections, by uncommenting the 'useSSL' and
149 # 'verifyServerCertificate' options below.
150 properties:
151 useUnicode: true
152 characterEncoding: utf8
153 #useSSL: false
154 #verifyServerCertificate: false
155
156 # The prefix for all LuckPerms SQL tables.
157 # - Change this if you want to use different tables for different servers.
158 table-prefix: 'luckperms_'
159
160 # The prefix to use for all LuckPerms collections. Change this if you want to use different
161 # collections for different servers. The default is no prefix.
162 mongodb-collection-prefix: ''
163
164 # MongoDB ClientConnectionURI for use with replica sets and custom connection options
165 # - See https://docs.mongodb.com/manual/reference/connection-string/
166 mongodb-connection-uri: ''
167
168# Define settings for a "split" storage setup.
169#
170# - This allows you to define a storage method for each type of data.
171# - The connection options above still have to be correct for each type here.
172split-storage:
173 # Don't touch this if you don't want to use split storage!
174 enabled: false
175 methods:
176 # These options don't need to be modified if split storage isn't enabled.
177 user: h2
178 group: h2
179 track: h2
180 uuid: h2
181 log: h2
182
183
184
185
186# +----------------------------------------------------------------------------------------------+ #
187# | | #
188# | UPDATE PROPAGATION & MESSAGING SERVICE | #
189# | | #
190# | Controls the ways in which LuckPerms will sync data & notify other servers of changes. | #
191# | These options are documented on greater detail on the wiki under "Instant Updates". | #
192# | | #
193# +----------------------------------------------------------------------------------------------+ #
194
195# This option controls how frequently LuckPerms will perform a sync task.
196#
197# - A sync task will refresh all data from the storage, and ensure that the most up-to-date data is
198# being used by the plugin.
199# - This is disabled by default, as most users will not need it. However, if you're using a remote
200# storage type without a messaging service setup, you may wish to set this to something like 3.
201# - Set to -1 to disable the task completely.
202sync-minutes: -1
203
204# If the file watcher should be enabled.
205#
206# - When using a file-based storage type, LuckPerms can monitor the data files for changes, and
207# automatically update when changes are detected.
208# - If you don't want this feature to be active, set this option to false.
209watch-files: true
210
211# Define which messaging service should be used by the plugin.
212#
213# - If enabled and configured, LuckPerms will use the messaging service to inform other connected
214# servers of changes.
215# - Use the command "/lp networksync" to manually push changes.
216# - Data is NOT stored using this service. It is only used as a messaging platform.
217#
218# - If you decide to enable this feature, you should set "sync-minutes" to -1, as there is no need
219# for LuckPerms to poll the database for changes.
220#
221# - Possible options:
222# => sql Uses the SQL database to form a queue system for communication. Will only work when
223# 'storage-method' is set to MySQL or MariaDB. This is chosen by default if the
224# option is set to 'auto' and SQL storage is in use. Set to 'notsql' to disable this.
225# => pluginmsg Uses the plugin messaging channels to communicate with the proxy.
226# LuckPerms must be installed on your proxy & all connected servers backend servers.
227# Won't work if you have more than one proxy.
228# => lilypad Uses LilyPad pub-sub to push changes. You need to have the LilyPad-Connect plugin
229# installed.
230# => redis Uses Redis pub-sub to push changes. Your server connection info must be configured
231# below.
232# => rabbitmq Uses RabbitMQ pub-sub to push changes. Your server connection info must be
233# configured below.
234# => auto Attempts to automatically setup a messaging service using redis or sql.
235messaging-service: auto
236
237# If LuckPerms should automatically push updates after a change has been made with a command.
238auto-push-updates: true
239
240# If LuckPerms should push logging entries to connected servers via the messaging service.
241push-log-entries: true
242
243# If LuckPerms should broadcast received logging entries to players on this platform.
244#
245# - If you have LuckPerms installed on your backend servers as well as a BungeeCord proxy, you
246# should set this option to false on either your backends or your proxies, to avoid players being
247# messaged twice about log entries.
248broadcast-received-log-entries: true
249
250# Settings for Redis.
251# Port 6379 is used by default; set address to "host:port" if differs
252redis:
253 enabled: false
254 address: localhost
255 password: ''
256
257# Settings for RabbitMQ.
258# Port 5672 is used by default; set address to "host:port" if differs
259rabbitmq:
260 enabled: false
261 address: localhost
262 vhost: '/'
263 username: 'guest'
264 password: 'guest'
265
266
267
268
269# +----------------------------------------------------------------------------------------------+ #
270# | | #
271# | CUSTOMIZATION SETTINGS | #
272# | | #
273# | Settings that allow admins to customize the way LuckPerms operates. | #
274# | | #
275# +----------------------------------------------------------------------------------------------+ #
276
277# Controls how temporary permissions/parents/meta should be accumulated.
278#
279# - The default behaviour is "deny".
280# - This behaviour can also be specified when the command is executed. See the command usage
281# documentation for more info.
282#
283# - Possible options:
284# => accumulate durations will be added to the existing expiry time
285# => replace durations will be replaced if the new duration is later than the current
286# expiration
287# => deny the command will just fail if you try to add another node with the same expiry
288temporary-add-behaviour: deny
289
290# Controls how LuckPerms will determine a users "primary" group.
291#
292# - The meaning and influence of "primary groups" are explained in detail on the wiki.
293# - The preferred approach is to let LuckPerms automatically determine a users primary group
294# based on the relative weight of their parent groups.
295#
296# - Possible options:
297# => stored use the value stored against the users record in the file/database
298# => parents-by-weight just use the users most highly weighted parent
299# => all-parents-by-weight same as above, but calculates based upon all parents inherited from
300# both directly and indirectly
301primary-group-calculation: parents-by-weight
302
303# If the plugin should check for "extra" permissions with users run LP commands.
304#
305# - These extra permissions allow finer control over what users can do with each command, and who
306# they have access to edit.
307# - The nature of the checks are documented on the wiki under "Argument based command permissions".
308# - Argument based permissions are *not* static, unlike the 'base' permissions, and will depend upon
309# the arguments given within the command.
310argument-based-command-permissions: false
311
312# If the plugin should check whether senders are a member of a given group before they're able to
313# edit the groups data or add/remove other users to/from it.
314# Note: these limitations do not apply to the web editor!
315require-sender-group-membership-to-modify: false
316
317# If the plugin should send log notifications to users whenever permissions are modified.
318#
319# - Notifications are only sent to those with the appropriate permission to receive them
320# - They can also be temporarily enabled/disabled on a per-user basis using
321# '/lp log notify <on|off>'
322log-notify: true
323
324# Defines a list of log entries which should not be sent as notifications to users.
325#
326# - Each entry in the list is a RegEx expression which is matched against the log entry description.
327log-notify-filtered-descriptions:
328# - "parent add example"
329
330# If LuckPerms should automatically install translation bundles and periodically update them.
331auto-install-translations: true
332
333# Defines the options for prefix and suffix stacking.
334#
335# - The feature allows you to display multiple prefixes or suffixes alongside a players username in
336# chat.
337# - It is explained and documented in more detail on the wiki under "Prefix & Suffix Stacking".
338#
339# - The options are divided into separate sections for prefixes and suffixes.
340# - The 'duplicates' setting refers to how duplicate elements are handled. Can be 'retain-all',
341# 'first-only' or 'last-only'.
342# - The value of 'start-spacer' is included at the start of the resultant prefix/suffix.
343# - The value of 'end-spacer' is included at the end of the resultant prefix/suffix.
344# - The value of 'middle-spacer' is included between each element in the resultant prefix/suffix.
345#
346# - Possible format options:
347# => highest Selects the value with the highest weight, from all values
348# held by or inherited by the player.
349#
350# => lowest Same as above, except takes the one with the lowest weight.
351#
352# => highest_own Selects the value with the highest weight, but will not
353# accept any inherited values.
354#
355# => lowest_own Same as above, except takes the value with the lowest weight.
356#
357# => highest_inherited Selects the value with the highest weight, but will only
358# accept inherited values.
359#
360# => lowest_inherited Same as above, except takes the value with the lowest weight.
361#
362# => highest_on_track_<track> Selects the value with the highest weight, but only if the
363# value was inherited from a group on the given track.
364#
365# => lowest_on_track_<track> Same as above, except takes the value with the lowest weight.
366#
367# => highest_not_on_track_<track> Selects the value with the highest weight, but only if the
368# value was inherited from a group not on the given track.
369#
370# => lowest_not_on_track_<track> Same as above, except takes the value with the lowest weight.
371#
372# => highest_from_group_<group> Selects the value with the highest weight, but only if the
373# value was inherited from the given group.
374#
375# => lowest_from_group_<group> Same as above, except takes the value with the lowest weight.
376#
377# => highest_not_from_group_<group> Selects the value with the highest weight, but only if the
378# value was not inherited from the given group.
379#
380# => lowest_not_from_group_<group> Same as above, except takes the value with the lowest weight.
381meta-formatting:
382 prefix:
383 format:
384 - "highest"
385 duplicates: first-only
386 start-spacer: ""
387 middle-spacer: " "
388 end-spacer: ""
389 suffix:
390 format:
391 - "highest"
392 duplicates: first-only
393 start-spacer: ""
394 middle-spacer: " "
395 end-spacer: ""
396
397
398
399
400# +----------------------------------------------------------------------------------------------+ #
401# | | #
402# | PERMISSION CALCULATION AND INHERITANCE | #
403# | | #
404# | Modify the way permission checks, meta lookups and inheritance resolutions are handled. | #
405# | | #
406# +----------------------------------------------------------------------------------------------+ #
407
408# The algorithm LuckPerms should use when traversing the "inheritance tree".
409#
410# - Possible options:
411# => breadth-first See: https://en.wikipedia.org/wiki/Breadth-first_search
412# => depth-first-pre-order See: https://en.wikipedia.org/wiki/Depth-first_search
413# => depth-first-post-order See: https://en.wikipedia.org/wiki/Depth-first_search
414inheritance-traversal-algorithm: depth-first-pre-order
415
416# If a final sort according to "inheritance rules" should be performed after the traversal algorithm
417# has resolved the inheritance tree.
418#
419# "Inheritance rules" refers to things such as group weightings, primary group status, and the
420# natural contextual ordering of the group nodes.
421#
422# Setting this to 'true' will allow for the inheritance rules to take priority over the structure of
423# the inheritance tree.
424#
425# Effectively when this setting is 'true': the tree is flattened, and rules applied afterwards,
426# and when this setting is 'false':, the rules are just applied during each step of the traversal.
427post-traversal-inheritance-sort: false
428
429# Defines the mode used to determine whether a set of contexts are satisfied.
430#
431# - Possible options:
432# => at-least-one-value-per-key Set A will be satisfied by another set B, if at least one of the
433# key-value entries per key in A are also in B.
434# => all-values-per-key Set A will be satisfied by another set B, if all key-value
435# entries in A are also in B.
436context-satisfy-mode: at-least-one-value-per-key
437
438# LuckPerms has a number of built-in contexts. These can be disabled by adding the context key to
439# the list below.
440disabled-contexts:
441# - "world"
442
443# +----------------------------------------------------------------------------------------------+ #
444# | Permission resolution settings | #
445# +----------------------------------------------------------------------------------------------+ #
446
447# If users on this server should have their global permissions applied.
448# When set to false, only server specific permissions will apply for users on this server
449include-global: true
450
451# If users on this server should have their global world permissions applied.
452# When set to false, only world specific permissions will apply for users on this server
453include-global-world: true
454
455# If users on this server should have global (non-server specific) groups applied
456apply-global-groups: true
457
458# If users on this server should have global (non-world specific) groups applied
459apply-global-world-groups: true
460
461# +----------------------------------------------------------------------------------------------+ #
462# | Meta lookup settings | #
463# +----------------------------------------------------------------------------------------------+ #
464
465# Defines how meta values should be selected.
466#
467# - Possible options:
468# => inheritance Selects the meta value that was inherited first
469# => highest-number Selects the highest numerical meta value
470# => lowest-number Selects the lowest numerical meta value
471meta-value-selection-default: inheritance
472
473# Defines how meta values should be selected per key.
474meta-value-selection:
475# max-homes: highest-number
476
477# +----------------------------------------------------------------------------------------------+ #
478# | Inheritance settings | #
479# +----------------------------------------------------------------------------------------------+ #
480
481# If the plugin should apply wildcard permissions.
482#
483# - If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered
484# permissions matching the wildcard.
485apply-wildcards: true
486
487# If LuckPerms should resolve and apply permissions according to the Sponge style implicit wildcard
488# inheritance system.
489#
490# - That being: If a user has been granted "example", then the player should have also be
491# automatically granted "example.function", "example.another", "example.deeper.nesting",
492# and so on.
493apply-sponge-implicit-wildcards: false
494
495# If the plugin should apply negated Bukkit default permissions before it considers wildcard
496# assignments.
497#
498# - Plugin authors can define permissions which explicitly should not be given automatically to OPs.
499# This is usually used for so called "anti-permissions" - permissions which, when granted, apply
500# something negative.
501# - If this option is set to true, LuckPerms will consider any negated declarations made by
502# plugins before it considers wildcards. (similar to the way the OP system works)
503# - If this option is set to false, LuckPerms will consider any wildcard assignments first.
504apply-default-negated-permissions-before-wildcards: false
505
506# If the plugin should parse regex permissions.
507#
508# - If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the
509# node, and resolve & apply all registered permissions matching the regex.
510apply-regex: true
511
512# If the plugin should complete and apply shorthand permissions.
513#
514# - If set to true, LuckPerms will detect and expand shorthand node patterns.
515apply-shorthand: true
516
517# If the plugin should apply Bukkit child permissions.
518#
519# - Plugin authors can define custom permissions structures for their plugin, which will be resolved
520# and used by LuckPerms if this setting is enabled.
521apply-bukkit-child-permissions: true
522
523# If the plugin should apply Bukkit default permissions.
524#
525# - Plugin authors can define permissions which should be given to all users by default, or setup
526# permissions which should/shouldn't be given to opped players.
527# - If this option is set to false, LuckPerms will ignore these defaults.
528apply-bukkit-default-permissions: true
529
530# If the plugin should apply attachment permissions.
531#
532# - Other plugins on the server are able to add their own "permission attachments" to players.
533# - This allows them to grant players additional permissions which last until the end of the
534# session, or until they're removed.
535# - If this option is set to false, LuckPerms will not include these attachment permissions when
536# considering if a player should have access to a certain permission.
537apply-bukkit-attachment-permissions: true
538
539# +----------------------------------------------------------------------------------------------+ #
540# | Extra settings | #
541# +----------------------------------------------------------------------------------------------+ #
542
543# Allows you to set "aliases" for the worlds sent forward for context calculation.
544#
545# - These aliases are provided in addition to the real world name. Applied recursively.
546# - Remove the comment characters for the default aliases to apply.
547world-rewrite:
548# world_nether: world
549# world_the_end: world
550
551# Define special group weights for this server.
552#
553# - Group weights can also be applied directly to group data, using the setweight command.
554# - This section allows weights to be set on a per-server basis.
555group-weight:
556# admin: 10
557
558
559
560
561# +----------------------------------------------------------------------------------------------+ #
562# | | #
563# | FINE TUNING OPTIONS | #
564# | | #
565# | A number of more niche settings for tweaking and changing behaviour. The section also | #
566# | contains toggles for some more specialised features. It is only necessary to make changes to | #
567# | these options if you want to fine-tune LuckPerms behaviour. | #
568# | | #
569# +----------------------------------------------------------------------------------------------+ #
570
571# +----------------------------------------------------------------------------------------------+ #
572# | Server Operator (OP) settings | #
573# +----------------------------------------------------------------------------------------------+ #
574
575# Controls whether server operators should exist at all.
576#
577# - When set to 'false', all players will be de-opped, and the /op and /deop commands will be
578# disabled.
579enable-ops: true
580
581# Enables or disables a special permission based system in LuckPerms for controlling OP status.
582#
583# - If set to true, any user with the permission "luckperms.autoop" will automatically be granted
584# server operator status. This permission can be inherited, or set on specific servers/worlds,
585# temporarily, etc.
586# - Additionally, setting this to true will force the "enable-ops" option above to false. All users
587# will be de-opped unless they have the permission node, and the op/deop commands will be
588# disabled.
589# - It is recommended that you use this option instead of assigning a single '*' permission.
590auto-op: enable-ops
591
592# Defines if "opped" players should be able to use all LuckPerms commands by default.
593#
594# - Set to false to only allow users who have the permissions access to the commands
595commands-allow-op: true
596
597# +----------------------------------------------------------------------------------------------+ #
598# | Vault integration settings | #
599# +----------------------------------------------------------------------------------------------+ #
600
601# If Vault lookups for offline players on the main server thread should be enabled.
602#
603# LuckPerms has a "catch" for plugins attempting to perform unsafe offline player data lookups
604# from the main server thread. This catch raises an exception (causes an error to occur) when unsafe
605# lookups are made, instead of allowing the lookup to happen, which would likely cause the server
606# to lag.
607#
608# However, if you're willing to accept the consequences, the catch can be disabled by setting this
609# option to 'true.
610vault-unsafe-lookups: false
611
612# If LuckPerms should use the 'display name' of a group when returning groups in Vault API calls.
613#
614# - When this option is set to true, the display name of the group is returned.
615# - When this option is set to false, the standard name/id of the group is returned.
616vault-group-use-displaynames: true
617
618# Controls which group LuckPerms should use for NPC players when handling Vault requests.
619#
620# - As NPCs aren't actually real players, LuckPerms does not load any user data for them. This
621# becomes an issue when plugins want to check for their permissions using Vault.
622# - As a solution, Vault checks for NPCs fallback to a group, which is defined below.
623vault-npc-group: default
624
625# Controls how LuckPerms should consider the OP status of NPC players when handing Vault requests.
626#
627# - If you want NPCs to have the same permissions as "normal" players, set this option to false.
628# - If you want NPCs to have OP status, set this option to true.
629vault-npc-op-status: false
630
631# If the vault-server option below should be used.
632#
633# - When this option is set to false, the server value defined above under "server" is used.
634use-vault-server: false
635
636# The name of the server used within Vault operations.
637#
638# - If you don't want Vault operations to be server specific, set this to "global".
639# - Will only take effect if use-vault-server is set to true above.
640vault-server: global
641
642# If global permissions should be considered when retrieving meta or player groups
643vault-include-global: true
644
645# If Vault operations should ignore any world arguments if supplied.
646vault-ignore-world: false
647
648# +----------------------------------------------------------------------------------------------+ #
649# | Miscellaneous (and rarely used) settings | #
650# +----------------------------------------------------------------------------------------------+ #
651
652# If LuckPerms should produce extra logging output when it handles logins.
653#
654# - Useful if you're having issues with UUID forwarding or data not being loaded.
655debug-logins: false
656
657# If LuckPerms should allow usernames with non alphanumeric characters.
658#
659# - Note that due to the design of the storage implementation, usernames must still be 16 characters
660# or less.
661allow-invalid-usernames: false
662
663# If LuckPerms should allow a users primary group to be removed with the 'parent remove' command.
664#
665# - When this happens, the plugin will set their primary group back to default.
666prevent-primary-group-removal: false
667
668# If LuckPerms should update the list of commands sent to the client when permissions are changed.
669update-client-command-list: true
670
671# If LuckPerms should attempt to register "Brigadier" command list data for its commands.
672register-command-list-data: true
673
674# If LuckPerms should attempt to resolve Vanilla command target selectors for LP commands.
675# See here for more info: https://minecraft.gamepedia.com/Commands#Target_selectors
676resolve-command-selectors: false