SHARE
TWEET

Untitled

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