SHARE
TWEET

Untitled

a guest Jun 5th, 2017 507 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ##############################################################################
  2. # +------------------------------------------------------------------------+ #
  3. # |                       LuckPerms Configuration                          | #
  4. # |                  https://github.com/lucko/LuckPerms                    | #
  5. # +------------------------------------------------------------------------+ #
  6. ##############################################################################
  7.  
  8. # +------------------------------------------------------------------------+ #
  9. # |                               General                                  | #
  10. # +------------------------------------------------------------------------+ #
  11.  
  12. # The name of the server, used for server specific permissions. Set to 'global' to disable.
  13. server: bedwars
  14.  
  15. # If users on this server should have their global permissions applied.
  16. # If set to false, only server specific permissions will apply for users on this server
  17. include-global: true
  18.  
  19. # If users on this server should have their global world permissions applied.
  20. # If set to false, only world specific permissions will apply for users on this server
  21. include-global-world: true
  22.  
  23. # If users on this server should have global (non-server specific) groups applied
  24. apply-global-groups: true
  25.  
  26. # If users on this server should have global (non-world specific) groups applied
  27. apply-global-world-groups: true
  28.  
  29. # If UUIDs should be pulled from the server, or looked up by username based upon previous connections.
  30. #
  31. # This option should be set to true in most cases. When set to false, in order to get a player's UUID, LuckPerms will:
  32. # 1. Check if a player with the given username has joined before, if they have, use the UUID they used on their previous login.
  33. # 2. Save and return the players "current" uuid.
  34. #
  35. # For offline mode (cracked) servers, a players UUID is generated based upon their username.
  36. #
  37. # IMPORTANT:
  38. # If you are using BungeeCord proxy running in online mode, it is important that "online-mode=false" is set in server.properties, but
  39. # "bungeecord: true" is set in the spigot.yml. You also need to set "ip_forward: true" in BungeeCord's config.yml.
  40. # If for whatever reason you are not able to do this, and do not have ip-forward enabled, then you may need to set "use-server-uuids" to false.
  41. #
  42. # If your proxy is running in offline mode, you should still be setting up ip-forwarding as described above, but may also find that you need to set
  43. # "bungee-online-mode" to false in paper.yml, if you are using PaperSpigot. (https://ci.destroystokyo.com/job/PaperSpigot/)
  44. #
  45. # This option only really exists for networks who for whatever reason cannot setup proper ip forwarding.
  46. use-server-uuids: true
  47.  
  48. # If the plugin should send log notifications to users whenever permissions are modified.
  49. log-notify: true
  50.  
  51. # Mirrors world names. Whenever LuckPerms checks what world a user is in, if the world name is in this list, the value assigned
  52. # will be sent forward for permission calculation instead.
  53. world-rewrite:
  54. #  world_nether: world
  55. #  world_the_end: world
  56.  
  57. # Rewrites group names. The underlying name of the group does not change, just the output in commands / placeholders / Vault.
  58. group-name-rewrite:
  59. #  default: Member
  60.  
  61. # Controls how temporary permissions/parents/meta should be accumulated
  62. #
  63. # The default behaviour is "deny"
  64. # If "accumulate": durations will be added to the existing expiry time
  65. # If "replace": durations will be replaced if the new duration is later than the current expiration
  66. # If "deny": the command will just fail if you try to add another node with the same expiry
  67. temporary-add-behaviour: deny
  68.  
  69. # How should LuckPerms determine a users "primary" group.
  70. #
  71. # Available Options:
  72. # -> stored                 use the value stored against the users record in the file/database
  73. # -> parents-by-weight      just use the users most highly weighted parent
  74. # -> all-parents-by-weight  same as above, but calculates based upon all parents inherited from both directly and indirectly
  75. primary-group-calculation: stored
  76.  
  77.  
  78.  
  79.  
  80. # +------------------------------------------------------------------------+ #
  81. # |                        Permission Calculation                          | #
  82. # +------------------------------------------------------------------------+ #
  83.  
  84. # If the plugin should apply wildcard permissions.
  85. # If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered permissions matching
  86. # the wildcard.
  87. apply-wildcards: true
  88.  
  89. # If the plugin should parse regex permissions.
  90. # If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the node, and resolve &
  91. # apply all registered permissions matching the regex.
  92. apply-regex: true
  93.  
  94. # If the plugin should complete and apply shorthand permissions.
  95. # If set to true, LuckPerms will detect and expand shorthand node patterns.
  96. apply-shorthand: true
  97.  
  98. # If the plugin should apply Bukkit child permissions.
  99. # Plugin authors can define custom permissions structures for their plugin, which will be resolved and used
  100. # by LuckPerms if this setting is enabled.
  101. apply-bukkit-child-permissions: true
  102.  
  103. # If the plugin should apply Bukkit default permissions.
  104. # Plugin authors can define permissions which should be given to all users by default, or setup permissions
  105. # which should/shouldn't be given to opped players.
  106. # If this option is set to false, LuckPerms will ignore these defaults.
  107. apply-bukkit-default-permissions: true
  108.  
  109. # If the plugin should apply attachment permissions.
  110. # Other plugins on the server are able to add their own "permission attachments" to players. This allows
  111. # them to grant players additional permissions which last until the end of the session, or until they're removed.
  112. # If this option is set to false, LuckPerms will not include these attachment permissions when considering if a
  113. # player should have access to a certain permission.
  114. apply-bukkit-attachment-permissions: true
  115.  
  116. # Define special group weights for this server.
  117. # Default is just 0.
  118. group-weight:
  119. #  admin: 10
  120.  
  121.  
  122.  
  123.  
  124. # +------------------------------------------------------------------------+ #
  125. # |                      Meta Formatting & Stacking                        | #
  126. # +------------------------------------------------------------------------+ #
  127.  
  128. # Allows you to setup prefix/suffix stacking options.
  129. #
  130. # Available formats:
  131. # - highest
  132. # - lowest
  133. # - highest_own
  134. # - lowest_own
  135. # - highest_on_track_<track>
  136. # - lowest_on_track_<track>
  137. # - highest_not_on_track_<track>
  138. # - lowest_not_on_track_<track>
  139. #
  140. # Each element is added in the order listed.
  141. meta-formatting:
  142.   prefix:
  143.     format:
  144.       - "highest"
  145.     start-spacer: ""
  146.     middle-spacer: " "
  147.     end-spacer: ""
  148.   suffix:
  149.     format:
  150.       - "highest"
  151.     start-spacer: ""
  152.     middle-spacer: " "
  153.     end-spacer: ""
  154.  
  155.  
  156.  
  157.  
  158. # +------------------------------------------------------------------------+ #
  159. # |                    OP (Server Operator) Settings                       | #
  160. # +------------------------------------------------------------------------+ #
  161.  
  162. # If the vanilla OP system is enabled. If set to false, all users will be de-opped, and the op/deop commands will be disabled.
  163. enable-ops: true
  164.  
  165. # If set to true, any user with the permission "luckperms.autoop" will automatically be granted server operator status.
  166. # This permission can be inherited, or set on specific servers/worlds, temporarily, etc.
  167. # Additionally, setting this to true will force the "enable-ops" option above to false. All users will be de-opped unless
  168. # they have the permission node, and the op/deop commands will be disabled.
  169. #
  170. # It is important to note that this setting is only checked when a player first joins the server, and when they switch
  171. # worlds. Therefore, simply removing this permission from a user will not automatically de-op them. A player needs to
  172. # relog to have the change take effect.
  173. #
  174. # It is recommended that you use this option instead of assigning a single '*' permission.
  175. auto-op: false
  176.  
  177. # If opped players should be allowed to use LuckPerms commands. Set to false to only allow users who have the permissions access to the commands
  178. commands-allow-op: true
  179.  
  180.  
  181.  
  182.  
  183. # +------------------------------------------------------------------------+ #
  184. # |                                Vault                                   | #
  185. # +------------------------------------------------------------------------+ #
  186.  
  187. # If the vault-server option below should be used.
  188. # When this option is set to false, the server value defined above under "server" is used.
  189. use-vault-server: false
  190.  
  191. # The name of the server used within Vault operations. If you don't want Vault operations to be server specific, set this
  192. # to "global".
  193. #
  194. # Will only take effect if use-vault-server is set to true above.
  195. vault-server: global
  196.  
  197. # If global permissions should be considered when retrieving meta or player groups
  198. vault-include-global: true
  199.  
  200. # If Vault operations should ignore any world arguments if supplied.
  201. vault-ignore-world: false
  202.  
  203. # If LuckPerms should print debugging info to console when a plugin uses a Vault function
  204. vault-debug: false
  205.  
  206.  
  207.  
  208.  
  209. # +------------------------------------------------------------------------+ #
  210. # |                               Storage                                  | #
  211. # +------------------------------------------------------------------------+ #
  212.  
  213. # Which storage method the plugin should use.
  214. #
  215. # See: https://github.com/lucko/LuckPerms/wiki/Choosing-a-Storage-type
  216. # Currently supported: mysql, mariadb, postgresql, sqlite, h2, json, yaml, mongodb
  217.  
  218. # Fill out connection info below if you're using MySQL, MariaDB, PostgreSQL or MongoDB
  219. # If your MySQL server supports it, the "mariadb" option is preferred over "mysql".
  220. storage-method: mysql
  221.  
  222. # When using a file-based storage type, LuckPerms can monitor the data files for changes, and then schedule automatic
  223. # updates when changes are detected.
  224. #
  225. # If you don't want this to happen, set this option to false.
  226. watch-files: true
  227.  
  228. # This block enables support for split datastores.
  229. split-storage:
  230.   enabled: true
  231.   methods:
  232.     user: mysql
  233.     group: yaml
  234.     track: yaml
  235.     uuid: mysql
  236.     log: mysql
  237.  
  238. data:
  239.   # Uses standard DB engine port by default
  240.   # MySQL: 3306, PostgreSQL: 5432, MongoDB: 27017
  241.   # Specify as "host:port" if differs
  242.   address: localhost
  243.  
  244.   database: luckperm
  245.   username: root
  246.   password: '*****'
  247.   pool-size: 10 # The size of the MySQL connection pool.
  248.  
  249.   # The prefix for all LuckPerms tables. Change this is you want to use different tables for different servers.
  250.   # This should *not* be set to "lp_" if you have previously ran LuckPerms v2.16.81 or earlier with this database.
  251.   table_prefix: 'luckperms_'
  252.  
  253.   # This option controls how frequently LuckPerms will perform a sync task.
  254.   # A sync task will refresh all data from the storage, and ensure that the most up-to-date data is being used by the plugin.
  255.   #
  256.   # This is disabled by default, as most users will not need it. However, if you're using a remote storage type
  257.   # without a messaging service setup, you may wish to set this value to something like 3.
  258.   #
  259.   # Set to -1 to disable the task completely.
  260.   sync-minutes: 1
  261.  
  262. # Settings for the messaging service
  263. #
  264. # If enabled and configured, LuckPerms will use the messaging system to inform other
  265. # connected servers of changes. Use the command "/luckperms networksync" to push changes.
  266. # Data is NOT stored using this service. It is only used as a messaging platform.
  267. #
  268. # If you decide to enable this feature, you should set "sync-minutes" to -1, as there is no need for LuckPerms
  269. # to poll the database for changes.
  270. #
  271. # Available options:
  272. # bungee ==> uses the plugin messaging channels. Must be enabled on all connected servers to work.
  273. # lilypad ==> uses lilypad pub sub to push changes. You need to have the LilyPad-Connect plugin installed.
  274. # redis ==> uses redis pub sub to push changes. Your redis server must be configured below.
  275. # none ==> nothing
  276. messaging-service: none
  277.  
  278. # If LuckPerms should automatically push updates after a change has been made with a command.
  279. auto-push-updates: true
  280.  
  281. # Settings for Redis.
  282. # Port 6379 is used by default; set address to "host:port" if differs
  283. redis:
  284.   enabled: false
  285.   address: localhost
  286.   password: ''
  287.  
  288.  
  289.  
  290.  
  291. # +------------------------------------------------------------------------+ #
  292. # |                         Default Assignments                            | #
  293. # +------------------------------------------------------------------------+ #
  294.  
  295. # This section allows you to define defaults to give users whenever they connect to the server.
  296. # The default assignments are highly configurable and conditional.
  297. #
  298. # There is one default assignment built into LuckPerms, which will add all users to the "default" group if they
  299. # are not a member of any other group. This setting cannot be disabled. However, you can use this section to add more of
  300. # your own.
  301. #
  302. # IMPORTANT:
  303. # In order to save storage space, LuckPerms does not store users who have no permissions defined, and are only a member
  304. # of the default group. Adding default assignments to this section will negate this effect. It is HIGHLY RECCOMENDED
  305. # that instead of assigning defaults here, you add permissions to the "default" group, or set the "default" group to inherit
  306. # other groups, and then use the group-name-rewrite rule above.
  307. #
  308. # It is also important to note that these rules are considered every time a player logs into the server, and are applied
  309. # directly to the user's data. Simply removing a rule here will not reserse the effect of that rule on any users who have
  310. # already had it applied to them.
  311. #
  312. # The "has" and "lacks" conditions below support standard boolean logic, using the 'and' & 'or' characters used in Java.
  313. # e.g. "(some.other.permission | some.permission.other) & some.thing.else" == a user has 'some.other.permission', or
  314. # 'some.permission.other', and they also have 'some.thing.else'
  315. #
  316. # Groups are represented by the permission node: group.<group name>
  317. # Per server and per world nodes are represented by: "server-world/permission" or "server/permission"
  318. #
  319. # Within conditions, permission nodes MUST be escaped using "<" and ">". See the example below.
  320. #
  321. # Explanation of the examples below: (they're just to demonstrate the features & use cases)
  322. #
  323. # rule1:
  324. # If a user is either in the vip or vip+ group, and they have the "titles.titlecollector" permission set to true, and the
  325. # "some.random.permission" set to false... if they're not in the group "prison_titlepack" on the "prison" server, then
  326. # give add them to the "prison_titlepack" group on the "prison" server, and remove "some.random.permission".
  327. #
  328. # rule2:
  329. # If the user isn't in any of the following groups on the skyblock server: sb_level1, sb_level2, sb_level3, then add
  330. # them to sb_level1 on the skyblock server.
  331. #
  332. # rule3:
  333. # If the user is a member of the default group, remove them from default, add them to member, and set their primary group
  334. # to member.
  335. #
  336. # WARNING: Unlike internal commands, this system does not ensure that a group exists before adding a user to it.
  337. # It also does not unsure that a user is a member of a group before making that group their primary group.
  338. #
  339. # Before you use "give: group.<name>" or "set-primary-group", make sure that the group exists, and that the user is
  340. # a member of the group.
  341. default-assignments:
  342. #  rule1:
  343. #    if:
  344. #      has-true: (<group.vip> | <group.vip+>) & <titles.tilecollector>
  345. #      has-false: <some.random.permission>
  346. #      lacks: <prison/group.prison_titlepack>
  347. #    give:
  348. #      - prison/group.prison_titlepack
  349. #    take:
  350. #      - some.random.permission
  351. #  rule2:
  352. #    if:
  353. #      lacks: <skyblock/group.sb_level1> & <skyblock/group.sb_level2> & <skyblock/group.sb_level3>
  354. #    give:
  355. #      - skyblock/group.sb_level1
  356. #  rule3:
  357. #    if:
  358. #      has-true: <group.default>
  359. #    take:
  360. #      - group.default
  361. #    give:
  362. #      - group.member
  363. #    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