daily pastebin goal
15%
SHARE
TWEET

Untitled

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