SHARE
TWEET

Untitled

GoldLeej Feb 9th, 2019 (edited) 313 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ####################################################################################################
  2.  
  3. # +----------------------------------------------------------------------------------------------+ #
  4.  
  5. # |                                   __         __   ___  __         __                         | #
  6.  
  7. # |                        |    |  | /  ` |__/  |__) |__  |__)  |\/| /__`                        | #
  8.  
  9. # |                        |___ \__/ \__, |  \  |    |___ |  \  |  | .__/                        | #
  10.  
  11. # |                                                                                              | #
  12.  
  13. # |                                  https://luckperms.github.io                                 | #
  14.  
  15. # |                                                                                              | #
  16.  
  17. # |  SOURCE CODE: https://github.com/lucko/LuckPerms                                             | #
  18.  
  19. # |  WIKI:        https://github.com/lucko/LuckPerms/wiki                                        | #
  20.  
  21. # |  BUG REPORTS: https://github.com/lucko/LuckPerms/issues                                      | #
  22.  
  23. # |                                                                                              | #
  24.  
  25. # |  Each option in this file is documented and explained here:                                  | #
  26.  
  27. # |   ==>  https://github.com/lucko/LuckPerms/wiki/Configuration                                 | #
  28.  
  29. # |                                                                                              | #
  30.  
  31. # |  New options are not added to this file automatically. Default values are used if an         | #
  32.  
  33. # |  option cannot be found. The latest config versions can be obtained at the link above.       | #
  34.  
  35. # +----------------------------------------------------------------------------------------------+ #
  36.  
  37. ####################################################################################################
  38.  
  39.  
  40.  
  41. # +----------------------------------------------------------------------------------------------+ #
  42.  
  43. # |                                                                                              | #
  44.  
  45. # |                                      ESSENTIAL SETTINGS                                      | #
  46.  
  47. # |                                                                                              | #
  48.  
  49. # |                   Important settings that control how LuckPerms functions.                   | #
  50.  
  51. # |                                                                                              | #
  52.  
  53. # +----------------------------------------------------------------------------------------------+ #
  54.  
  55.  
  56.  
  57. # The name of the server, used for server specific permissions.
  58.  
  59. #
  60.  
  61. # - When set to "global" this setting is effectively ignored.
  62.  
  63. # - In all other cases, the value here is added to all players in a "server" context.
  64.  
  65. # - See: https://github.com/lucko/LuckPerms/wiki/Context
  66.  
  67. server = "global"
  68.  
  69.  
  70.  
  71. # If the servers own UUID cache/lookup facility should be used when there is no record for a player
  72.  
  73. # already in LuckPerms.
  74.  
  75. #
  76.  
  77. # - When this is set to 'false', commands using a player's username will not work unless the player
  78.  
  79. #   has joined since LuckPerms was first installed.
  80.  
  81. # - To get around this, you can use a player's uuid directly in the command, or enable this option.
  82.  
  83. # - When this is set to 'true', the server facility is used. This may use a number of methods,
  84.  
  85. #   including checking the servers local cache, or making a request to the Mojang API.
  86.  
  87. use-server-uuid-cache = false
  88.  
  89.  
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97. # +----------------------------------------------------------------------------------------------+ #
  98.  
  99. # |                                                                                              | #
  100.  
  101. # |                                       STORAGE SETTINGS                                       | #
  102.  
  103. # |                                                                                              | #
  104.  
  105. # |                Controls which storage method LuckPerms will use to store data.               | #
  106.  
  107. # |                                                                                              | #
  108.  
  109. # +----------------------------------------------------------------------------------------------+ #
  110.  
  111.  
  112.  
  113. # How the plugin should store data
  114.  
  115. #
  116.  
  117. # - The various options are explained in more detail on the wiki:
  118.  
  119. #   https://github.com/lucko/LuckPerms/wiki/Choosing-a-Storage-type
  120.  
  121. #
  122.  
  123. # - Possible options:
  124.  
  125. #
  126.  
  127. #   |  Remote databases - require connection information to be configured below
  128.  
  129. #   |=> MySQL
  130.  
  131. #   |=> MariaDB (preferred over MySQL)
  132.  
  133. #   |=> PostgreSQL
  134.  
  135. #   |=> MongoDB
  136.  
  137. #
  138.  
  139. #   |  Flatfile/local database - don't require any extra configuration
  140.  
  141. #   |=> H2 (preferred over SQLite)
  142.  
  143. #   |=> SQLite
  144.  
  145. #
  146.  
  147. #   |  Readable & editable text files - don't require any extra configuration
  148.  
  149. #   |=> YAML (.yml files)
  150.  
  151. #   |=> JSON (.json files)
  152.  
  153. #   |=> HOCON (.conf files)
  154.  
  155. #   |=> TOML (.toml files)
  156.  
  157. #   |
  158.  
  159. #   | By default, user, group and track data is separated into different files. Data can be combined
  160.  
  161. #   | and all stored in the same file by switching to a combined storage variant.
  162.  
  163. #   | Just add '-combined' to the end of the storage-method, e.g. 'yaml-combined'
  164.  
  165. #
  166.  
  167. # - A H2 database is the default option.
  168.  
  169. # - If you want to edit data manually in "traditional" storage files, we suggest using YAML.
  170.  
  171. storage-method = "MySQL"
  172.  
  173.  
  174.  
  175. # The following block defines the settings for remote database storage methods.
  176.  
  177. #
  178.  
  179. # - You don't need to touch any of the settings here if you're using a local storage method!
  180.  
  181. # - The connection detail options are shared between all remote storage types.
  182.  
  183. data {
  184.  
  185.  
  186.  
  187.   # Define the address and port for the database.
  188.  
  189.   # - The standard DB engine port is used by default
  190.  
  191.   #   (MySQL = 3306, PostgreSQL = 5432, MongoDB = 27017)
  192.  
  193.   # - Specify as "host:port" if differs
  194.  
  195.   address = "sql.pebblehost.com"
  196.  
  197.  
  198.  
  199.  
  200.  
  201.  
  202.   # These settings apply to the MySQL connection pool.
  203.  
  204.   # - The default values will be suitable for the majority of users.
  205.  
  206.   # - Do not change these settings unless you know what you're doing!
  207.  
  208.   pool-settings {
  209.  
  210.  
  211.  
  212.     # Sets the maximum size of the MySQL connection pool.
  213.  
  214.     # - Basically this value will determine the maximum number of actual
  215.  
  216.     #   connections to the database backend.
  217.  
  218.     # - More information about determining the size of connection pools can be found here:
  219.  
  220.     #   https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
  221.  
  222.     maximum-pool-size = 10
  223.  
  224.  
  225.  
  226.     # Sets the minimum number of idle connections that the pool will try to maintain.
  227.  
  228.     # - For maximum performance and responsiveness to spike demands, it is recommended to not set
  229.  
  230.     #   this value and instead allow the pool to act as a fixed size connection pool.
  231.  
  232.     #   (set this value to the same as 'maximum-pool-size')
  233.  
  234.     minimum-idle = 10
  235.  
  236.  
  237.  
  238.     # This setting controls the maximum lifetime of a connection in the pool in milliseconds.
  239.  
  240.     # - The value should be at least 30 seconds less than any database or infrastructure imposed
  241.  
  242.     #   connection time limit.
  243.  
  244.     maximum-lifetime = 1800000 # 30 minutes
  245.  
  246.  
  247.  
  248.     # This setting controls the maximum number of milliseconds that the plugin will wait for a
  249.  
  250.     # connection from the pool, before timing out.
  251.  
  252.     connection-timeout = 5000 # 5 seconds
  253.  
  254.  
  255.  
  256.     # This setting allows you to define extra properties for connections.
  257.  
  258.     properties {
  259.  
  260.       useUnicode = true
  261.  
  262.       characterEncoding = "utf8"
  263.  
  264.     }
  265.  
  266.   }
  267.  
  268.  
  269.  
  270.   # The prefix for all LuckPerms SQL tables.
  271.  
  272.   # - Change this is you want to use different tables for different servers.
  273.  
  274.   table_prefix = "luckperms_"
  275.  
  276.  
  277.  
  278.   # The prefix to use for all LuckPerms collections. Change this if you want to use different
  279.  
  280.   # collections for different servers. The default is no prefix.
  281.  
  282.   mongodb_collection_prefix = ""
  283.  
  284.  
  285.  
  286.   # MongoDB ClientConnectionURI for use with replica sets and custom connection options
  287.  
  288.   # - See https://docs.mongodb.com/manual/reference/connection-string/
  289.  
  290.   mongodb_connection_URI = ""
  291.  
  292. }
  293.  
  294.  
  295.  
  296. # Define settings for a "split" storage setup.
  297.  
  298. #
  299.  
  300. # - This allows you to define a storage method for each type of data.
  301.  
  302. # - The connection options above still have to be correct for each type here.
  303.  
  304. split-storage {
  305.  
  306.   # Don't touch this if you don't want to use split storage!
  307.  
  308.   enabled = false
  309.  
  310.   methods {
  311.  
  312.     # These options don't need to be modified if split storage isn't enabled.
  313.  
  314.     user = "h2"
  315.  
  316.     group = "h2"
  317.  
  318.     track = "h2"
  319.  
  320.     uuid = "h2"
  321.  
  322.     log = "h2"
  323.  
  324.   }
  325.  
  326. }
  327.  
  328.  
  329.  
  330.  
  331.  
  332.  
  333.  
  334.  
  335.  
  336. # +----------------------------------------------------------------------------------------------+ #
  337.  
  338. # |                                                                                              | #
  339.  
  340. # |                            UPDATE PROPAGATION & MESSAGING SERVICE                            | #
  341.  
  342. # |                                                                                              | #
  343.  
  344. # |    Controls the ways in which LuckPerms will sync data & notify other servers of changes.    | #
  345.  
  346. # |     These options are documented on greater detail on the wiki under "Instant Updates".      | #
  347.  
  348. # |                                                                                              | #
  349.  
  350. # +----------------------------------------------------------------------------------------------+ #
  351.  
  352.  
  353.  
  354. # This option controls how frequently LuckPerms will perform a sync task.
  355.  
  356. #
  357.  
  358. # - A sync task will refresh all data from the storage, and ensure that the most up-to-date data is
  359.  
  360. #   being used by the plugin.
  361.  
  362. # - This is disabled by default, as most users will not need it. However, if you're using a remote
  363.  
  364. #   storage type without a messaging service setup, you may wish to set this to something like 3.
  365.  
  366. # - Set to -1 to disable the task completely.
  367.  
  368. sync-minutes = -1
  369.  
  370.  
  371.  
  372. # If the file watcher should be enabled.
  373.  
  374. #
  375.  
  376. # - When using a file-based storage type, LuckPerms can monitor the data files for changes, and
  377.  
  378. #   automatically update when changes are detected.
  379.  
  380. # - If you don't want this feature to be active, set this option to false.
  381.  
  382. watch-files = true
  383.  
  384.  
  385.  
  386. # Define which messaging service should be used by the plugin.
  387.  
  388. #
  389.  
  390. # - If enabled and configured, LuckPerms will use the messaging service to inform other connected
  391.  
  392. #   servers of changes.
  393.  
  394. # - Use the command "/lp networksync" to manually push changes.
  395.  
  396. # - Data is NOT stored using this service. It is only used as a messaging platform.
  397.  
  398. #
  399.  
  400. # - If you decide to enable this feature, you should set "sync-minutes" to -1, as there is no need
  401.  
  402. #   for LuckPerms to poll the database for changes.
  403.  
  404. #
  405.  
  406. # - Possible options:
  407.  
  408. #   => sql       Uses the SQL database to form a queue system for communication. Will only work when
  409.  
  410. #                'storage-method' is set to MySQL or MariaDB. This is chosen by default if the
  411.  
  412. #                option is set to 'none' and SQL storage is in use. Set to 'notsql' to disable this.
  413.  
  414. #   => pluginmsg Uses the plugin messaging channels to communicate with the proxy.
  415.  
  416. #                LuckPerms must be installed on your proxy & all connected servers backend servers.
  417.  
  418. #                Won't work if you have more than one proxy.
  419.  
  420. #   => redis     Uses Redis pub-sub to push changes. Your server connection info must be configured
  421.  
  422. #                below.
  423.  
  424. #   => none      Disables the service.
  425.  
  426. messaging-service = "none"
  427.  
  428.  
  429.  
  430. # If LuckPerms should automatically push updates after a change has been made with a command.
  431.  
  432. auto-push-updates = true
  433.  
  434.  
  435.  
  436. # If LuckPerms should push logging entries to connected servers via the messaging service.
  437.  
  438. push-log-entries = true
  439.  
  440.  
  441.  
  442. # If LuckPerms should broadcast received logging entries to players on this platform.
  443.  
  444. #
  445.  
  446. # - If you have LuckPerms installed on your backend servers as well as a BungeeCord proxy, you
  447.  
  448. #   should set this option to false on either your backends or your proxies, to avoid players being
  449.  
  450. #   messaged twice about log entries.
  451.  
  452. broadcast-received-log-entries = true
  453.  
  454.  
  455.  
  456. # Settings for Redis.
  457.  
  458. # Port 6379 is used by default; set address to "host:port" if differs
  459.  
  460. redis {
  461.  
  462.   enabled = false
  463.  
  464.   address = "localhost"
  465.  
  466.   password = ""
  467.  
  468. }
  469.  
  470.  
  471.  
  472.  
  473.  
  474.  
  475.  
  476.  
  477.  
  478. # +----------------------------------------------------------------------------------------------+ #
  479.  
  480. # |                                                                                              | #
  481.  
  482. # |                                    CUSTOMIZATION SETTINGS                                    | #
  483.  
  484. # |                                                                                              | #
  485.  
  486. # |              Settings that allow admins to customize the way LuckPerms operates.             | #
  487.  
  488. # |                                                                                              | #
  489.  
  490. # +----------------------------------------------------------------------------------------------+ #
  491.  
  492.  
  493.  
  494. # Controls how temporary permissions/parents/meta should be accumulated.
  495.  
  496. #
  497.  
  498. # - The default behaviour is "deny".
  499.  
  500. # - This behaviour can also be specified when the command is executed. See the command usage
  501.  
  502. #   documentation for more info.
  503.  
  504. #
  505.  
  506. # - Possible options:
  507.  
  508. #   => accumulate   durations will be added to the existing expiry time
  509.  
  510. #   => replace      durations will be replaced if the new duration is later than the current
  511.  
  512. #                   expiration
  513.  
  514. #   => deny         the command will just fail if you try to add another node with the same expiry
  515.  
  516. temporary-add-behaviour = "deny"
  517.  
  518.  
  519.  
  520. # Controls how LuckPerms will determine a users "primary" group.
  521.  
  522. #
  523.  
  524. # - The meaning and influence of "primary groups" are explained in detail on the wiki.
  525.  
  526. # - The preferred approach is to let LuckPerms automatically determine a users primary group
  527.  
  528. #   based on the relative weight of their parent groups.
  529.  
  530. #
  531.  
  532. # - Possible options:
  533.  
  534. #   => stored                  use the value stored against the users record in the file/database
  535.  
  536. #   => parents-by-weight       just use the users most highly weighted parent
  537.  
  538. #   => all-parents-by-weight   same as above, but calculates based upon all parents inherited from
  539.  
  540. #                              both directly and indirectly
  541.  
  542. primary-group-calculation = "parents-by-weight"
  543.  
  544.  
  545.  
  546. # If the plugin should check for "extra" permissions with users run LP commands.
  547.  
  548. #
  549.  
  550. # - These extra permissions allow finer control over what users can do with each command, and who
  551.  
  552. #   they have access to edit.
  553.  
  554. # - The nature of the checks are documented on the wiki under "Argument based command permissions".
  555.  
  556. # - Argument based permissions are *not* static, unlike the 'base' permissions, and will depend upon
  557.  
  558. #   the arguments given within the command.
  559.  
  560. argument-based-command-permissions = false
  561.  
  562.  
  563.  
  564. # If the plugin should check whether senders are a member of a given group before they're able to
  565.  
  566. # edit the groups data or add/remove other users to/from it.
  567.  
  568. # Note: these limitations do not apply to the web editor!
  569.  
  570. require-sender-group-membership-to-modify = false
  571.  
  572.  
  573.  
  574. # If the plugin should send log notifications to users whenever permissions are modified.
  575.  
  576. #
  577.  
  578. # - Notifications are only sent to those with the appropriate permission to receive them
  579.  
  580. # - They can also be temporarily enabled/disabled on a per-user basis using
  581.  
  582. #   '/lp log notify <on|off>'
  583.  
  584. log-notify = true
  585.  
  586.  
  587.  
  588. # Defines the options for prefix and suffix stacking.
  589.  
  590. #
  591.  
  592. # - The feature allows you to display multiple prefixes or suffixes alongside a players username in
  593.  
  594. #   chat.
  595.  
  596. # - It is explained and documented in more detail on the wiki under "Prefix & Suffix Stacking".
  597.  
  598. #
  599.  
  600. # - The options are divided into separate sections for prefixes and suffixes.
  601.  
  602. # - The 'duplicates' setting refers to how duplicate elements are handled. Can be 'retain-all',
  603.  
  604. #   'first-only' or 'last-only'.
  605.  
  606. # - The value of 'start-spacer' is included at the start of the resultant prefix/suffix.
  607.  
  608. # - The value of 'end-spacer' is included at the end of the resultant prefix/suffix.
  609.  
  610. # - The value of 'middle-spacer' is included between each element in the resultant prefix/suffix.
  611.  
  612. #
  613.  
  614. # - Possible format options:
  615.  
  616. #   => highest                        Selects the value with the highest weight, from all values
  617.  
  618. #                                     held by or inherited by the player.
  619.  
  620. #
  621.  
  622. #   => lowest                         Same as above, except takes the one with the lowest weight.
  623.  
  624. #
  625.  
  626. #   => highest_own                    Selects the value with the highest weight, but will not
  627.  
  628. #                                     accept any inherited values.
  629.  
  630. #
  631.  
  632. #   => lowest_own                     Same as above, except takes the value with the lowest weight.
  633.  
  634. #
  635.  
  636. #   => highest_inherited              Selects the value with the highest weight, but will only
  637.  
  638. #                                     accept inherited values.
  639.  
  640. #
  641.  
  642. #   => lowest_inherited               Same as above, except takes the value with the lowest weight.
  643.  
  644. #
  645.  
  646. #   => highest_on_track_<track>       Selects the value with the highest weight, but only if the
  647.  
  648. #                                     value was inherited from a group on the given track.
  649.  
  650. #
  651.  
  652. #   => lowest_on_track_<track>        Same as above, except takes the value with the lowest weight.
  653.  
  654. #
  655.  
  656. #   => highest_not_on_track_<track>   Selects the value with the highest weight, but only if the
  657.  
  658. #                                     value was inherited from a group not on the given track.
  659.  
  660. #
  661.  
  662. #   => lowest_not_on_track_<track>    Same as above, except takes the value with the lowest weight.
  663.  
  664. meta-formatting {
  665.  
  666.   prefix {
  667.  
  668.     format = [
  669.  
  670.       "highest"
  671.  
  672.     ]
  673.  
  674.     duplicates = "first-only"
  675.  
  676.     start-spacer = ""
  677.  
  678.     middle-spacer = " "
  679.  
  680.     end-spacer = ""
  681.  
  682.   }
  683.  
  684.   suffix {
  685.  
  686.     format = [
  687.  
  688.       "highest"
  689.  
  690.     ]
  691.  
  692.     duplicates = "first-only"
  693.  
  694.     start-spacer = ""
  695.  
  696.     middle-spacer = " "
  697.  
  698.     end-spacer = ""
  699.  
  700.   }
  701.  
  702. }
  703.  
  704.  
  705.  
  706.  
  707.  
  708.  
  709.  
  710.  
  711.  
  712. # +----------------------------------------------------------------------------------------------+ #
  713.  
  714. # |                                                                                              | #
  715.  
  716. # |                            PERMISSION CALCULATION AND INHERITANCE                            | #
  717.  
  718. # |                                                                                              | #
  719.  
  720. # |    Modify the way permission checks, meta lookups and inheritance resolutions are handled.   | #
  721.  
  722. # |                                                                                              | #
  723.  
  724. # +----------------------------------------------------------------------------------------------+ #
  725.  
  726.  
  727.  
  728. # The algorithm LuckPerms should use when traversing the "inheritance tree".
  729.  
  730. #
  731.  
  732. # - Possible options:
  733.  
  734. #   => breadth-first            See: https://en.wikipedia.org/wiki/Breadth-first_search
  735.  
  736. #   => depth-first-pre-order    See: https://en.wikipedia.org/wiki/Depth-first_search
  737.  
  738. #   => depth-first-post-order   See: https://en.wikipedia.org/wiki/Depth-first_search
  739.  
  740. inheritance-traversal-algorithm = "depth-first-pre-order"
  741.  
  742.  
  743.  
  744. # +----------------------------------------------------------------------------------------------+ #
  745.  
  746. # | Permission resolution settings                                                               | #
  747.  
  748. # +----------------------------------------------------------------------------------------------+ #
  749.  
  750.  
  751.  
  752. # If users on this server should have their global permissions applied.
  753.  
  754. # When set to false, only server specific permissions will apply for users on this server
  755.  
  756. include-global = true
  757.  
  758.  
  759.  
  760. # If users on this server should have their global world permissions applied.
  761.  
  762. # When set to false, only world specific permissions will apply for users on this server
  763.  
  764. include-global-world = true
  765.  
  766.  
  767.  
  768. # If users on this server should have global (non-server specific) groups applied
  769.  
  770. apply-global-groups = true
  771.  
  772.  
  773.  
  774. # If users on this server should have global (non-world specific) groups applied
  775.  
  776. apply-global-world-groups = true
  777.  
  778.  
  779.  
  780. # +----------------------------------------------------------------------------------------------+ #
  781.  
  782. # | Inheritance settings                                                                         | #
  783.  
  784. # +----------------------------------------------------------------------------------------------+ #
  785.  
  786.  
  787.  
  788. # If the plugin should apply wildcard permissions.
  789.  
  790. #
  791.  
  792. # - If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered
  793.  
  794. #   permissions matching the wildcard.
  795.  
  796. apply-wildcards = true
  797.  
  798.  
  799.  
  800. # If the plugin should parse regex permissions.
  801.  
  802. #
  803.  
  804. # - If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the
  805.  
  806. #   node, and resolve & apply all registered permissions matching the regex.
  807.  
  808. apply-regex = true
  809.  
  810.  
  811.  
  812. # If the plugin should complete and apply shorthand permissions.
  813.  
  814. #
  815.  
  816. # - If set to true, LuckPerms will detect and expand shorthand node patterns.
  817.  
  818. apply-shorthand = true
  819.  
  820.  
  821.  
  822. # If LuckPerms should resolve and apply permissions according to Sponge's implicit wildcard
  823.  
  824. # inheritance system.
  825.  
  826. #
  827.  
  828. # That being:
  829.  
  830. # If a user has been granted "example", then the player should have also be automatically granted
  831.  
  832. # "example.function", "example.another", "example.deeper.nesting", and so on.
  833.  
  834. #
  835.  
  836. # If this option is set to false, this system will not be applied.
  837.  
  838. apply-sponge-implicit-wildcards=true
  839.  
  840.  
  841.  
  842. # If the plugin should apply Sponge default subject permissions.
  843.  
  844. # Plugins can manipulate a set of default permissions granted to all users. If this option is set to
  845.  
  846. # false, LuckPerms will ignore this data when considering if a player has a permission.
  847.  
  848. apply-sponge-default-subjects=true
  849.  
  850.  
  851.  
  852. # +----------------------------------------------------------------------------------------------+ #
  853.  
  854. # | Extra settings                                                                               | #
  855.  
  856. # +----------------------------------------------------------------------------------------------+ #
  857.  
  858.  
  859.  
  860. # Allows you to set "aliases" for the worlds sent forward for context calculation.
  861.  
  862. #
  863.  
  864. # - These aliases are provided in addition to the real world name. Applied recursively.
  865.  
  866. # - Remove the comment characters for the default aliases to apply.
  867.  
  868. world-rewrite {
  869.  
  870.   #world_nether = "world"
  871.  
  872.   #world_the_end = "world"
  873.  
  874. }
  875.  
  876.  
  877.  
  878. # Define special group weights for this server.
  879.  
  880. #
  881.  
  882. # - Group weights can also be applied directly to group data, using the setweight command.
  883.  
  884. # - This section allows weights to be set on a per-server basis.
  885.  
  886. group-weight {
  887.  
  888.   #admin = 10
  889.  
  890. }
  891.  
  892.  
  893.  
  894.  
  895.  
  896.  
  897.  
  898.  
  899.  
  900. # +----------------------------------------------------------------------------------------------+ #
  901.  
  902. # |                                                                                              | #
  903.  
  904. # |                                      FINE TUNING OPTIONS                                     | #
  905.  
  906. # |                                                                                              | #
  907.  
  908. # |     A number of more niche settings for tweaking and changing behaviour. The section also    | #
  909.  
  910. # | contains toggles for some more specialised features. It is only necessary to make changes to | #
  911.  
  912. # |                  these options if you want to fine-tune LuckPerms behaviour.                 | #
  913.  
  914. # |                                                                                              | #
  915.  
  916. # +----------------------------------------------------------------------------------------------+ #
  917.  
  918.  
  919.  
  920. # +----------------------------------------------------------------------------------------------+ #
  921.  
  922. # | Miscellaneous (and rarely used) settings                                                     | #
  923.  
  924. # +----------------------------------------------------------------------------------------------+ #
  925.  
  926.  
  927.  
  928. # If LuckPerms should produce extra logging output when it handles logins.
  929.  
  930. #
  931.  
  932. # - Useful if you're having issues with UUID forwarding or data not being loaded.
  933.  
  934. debug-logins = false
  935.  
  936.  
  937.  
  938. # If LuckPerms should allow usernames with non alphanumeric characters.
  939.  
  940. #
  941.  
  942. # - Note that due to the design of the storage implementation, usernames must still be 16 characters
  943.  
  944. #   or less.
  945.  
  946. allow-invalid-usernames = false
  947.  
  948.  
  949.  
  950. # If LuckPerms should allow a users primary group to be removed with the 'parent remove' command.
  951.  
  952. #
  953.  
  954. # - When this happens, the plugin will set their primary group back to default.
  955.  
  956. prevent-primary-group-removal = false
  957.  
  958.  
  959.  
  960.  
  961.  
  962.  
  963.  
  964.  
  965.  
  966. # +----------------------------------------------------------------------------------------------+ #
  967.  
  968. # |                                                                                              | #
  969.  
  970. # |                                      DEFAULT ASSIGNMENTS                                     | #
  971.  
  972. # |                                                                                              | #
  973.  
  974. # +----------------------------------------------------------------------------------------------+ #
  975.  
  976.  
  977.  
  978. # This section allows you to define defaults to give users whenever they connect to the server.
  979.  
  980. # The default assignments are highly configurable and conditional.
  981.  
  982. #
  983.  
  984. # There is one default assignment built into LuckPerms, which will add all users to the "default"
  985.  
  986. # group if they are not a member of any other group. This setting cannot be disabled. However, you
  987.  
  988. # can use this section to add more of your own.
  989.  
  990. #
  991.  
  992. # IMPORTANT:
  993.  
  994. # In order to save storage space, LuckPerms does not store users who have no permissions defined,
  995.  
  996. # and are only a member of the default group. Adding default assignments to this section will negate
  997.  
  998. # this effect. It is HIGHLY RECCOMENDED that instead of assigning defaults here, you add permissions
  999.  
  1000. # to the "default" group, or set the "default" group to inherit other groups, and then use the
  1001.  
  1002. # group-name-rewrite rule above.
  1003.  
  1004. #
  1005.  
  1006. # It is also important to note that these rules are considered every time a player logs into the
  1007.  
  1008. # server, and are applied directly to the user's data. Simply removing a rule here will not reverse
  1009.  
  1010. # the effect of that rule on any users who have already had it applied to them.
  1011.  
  1012. #
  1013.  
  1014. # The "has" and "lacks" conditions below support standard boolean logic, using the 'and' & 'or'
  1015.  
  1016. # characters used in Java.
  1017.  
  1018. # e.g. "(some.other.permission | some.permission.other) & some.thing.else" == a user has
  1019.  
  1020. # 'some.other.permission', or 'some.permission.other', and they also have 'some.thing.else'
  1021.  
  1022. #
  1023.  
  1024. # Groups are represented by the permission node: group.<group name>
  1025.  
  1026. # Per server and per world nodes are represented by "server-world/permission" or "server/permission"
  1027.  
  1028. #
  1029.  
  1030. # Within conditions, permission nodes MUST be escaped using "<" and ">". See the example below.
  1031.  
  1032. #
  1033.  
  1034. # Explanation of the examples below: (they're just to demonstrate the features & use cases)
  1035.  
  1036. #
  1037.  
  1038. # rule1:
  1039.  
  1040. # If a user is either in the vip or vip+ group, and they have the "titles.titlecollector" permission
  1041.  
  1042. # set to true, and the "some.random.permission" set to false... if they're not in the group
  1043.  
  1044. # "prison_titlepack" on the "prison" server, then give add them to the "prison_titlepack" group on
  1045.  
  1046. # the "prison" server, and remove "some.random.permission".
  1047.  
  1048. #
  1049.  
  1050. # rule2:
  1051.  
  1052. # If the user isn't in any of the following groups on the skyblock server: sb_level1, sb_level2,
  1053.  
  1054. # sb_level3, then add them to sb_level1 on the skyblock server.
  1055.  
  1056. #
  1057.  
  1058. # rule3:
  1059.  
  1060. # If the user is a member of the default group, remove them from default, add them to member, and
  1061.  
  1062. # set their primary group to member.
  1063.  
  1064. #
  1065.  
  1066. # WARNING: Unlike internal commands, this system does not ensure that a group exists before adding
  1067.  
  1068. # a user to it. It also does not unsure that a user is a member of a group before making that group
  1069.  
  1070. # their primary group.
  1071.  
  1072. #
  1073.  
  1074. # Before you use "give: group.<name>" or "set-primary-group", make sure that the group exists, and
  1075.  
  1076. # that the user is a member of the group.
  1077.  
  1078. default-assignments {
  1079.  
  1080. #  rule1 {
  1081.  
  1082. #    if {
  1083.  
  1084. #      has-true="(<group.vip> | <group.vip+>) & <titles.tilecollector>"
  1085.  
  1086. #      has-false="<some.random.permission>"
  1087.  
  1088. #      lacks="<prison/group.prison_titlepack>"
  1089.  
  1090. #    }
  1091.  
  1092. #    give = [
  1093.  
  1094. #      "prison/group.prison_titlepack"
  1095.  
  1096. #    ]
  1097.  
  1098. #    take = [
  1099.  
  1100. #      "some.random.permission"
  1101.  
  1102. #    ]
  1103.  
  1104. #  }
  1105.  
  1106. #  rule2 {
  1107.  
  1108. #    if {
  1109.  
  1110. #      lacks="<skyblock/group.sb_level1> & <skyblock/group.sb_level2> & <skyblock/group.sb_level3>"
  1111.  
  1112. #    }
  1113.  
  1114. #    give = [
  1115.  
  1116. #      "skyblock/group.sb_level1"
  1117.  
  1118. #    ]
  1119.  
  1120. #  }
  1121.  
  1122. #  rule3 {
  1123.  
  1124. #    if {
  1125.  
  1126. #      has-true="<group.default>"
  1127.  
  1128. #    }
  1129.  
  1130. #    take = [
  1131.  
  1132. #      "group.default"
  1133.  
  1134. #    ]
  1135.  
  1136. #    give = [
  1137.  
  1138. #      "group.member"
  1139.  
  1140. #    ]
  1141.  
  1142. #    set-primary-group="member"
  1143.  
  1144. #  }
  1145.  
  1146. }
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!
 
Top