SHARE
TWEET

Untitled

a guest May 21st, 2017 543 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="global"
  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.ip-forwarding=true" is set in Sponge's global.conf. 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.
  43. #
  44. # This option only really exists for networks who for whatever reason cannot setup proper ip forwarding.
  45. use-server-uuids=true
  46.  
  47. # If the plugin should send log notifications to users whenever permissions are modified.
  48. log-notify=true
  49.  
  50. # Mirrors world names. Whenever LuckPerms checks what world a user is in, if the world name is in this list, the value assigned
  51. # will be sent forward for permission calculation instead.
  52. world-rewrite {
  53. #  world_nether="world"
  54. #  world_the_end="world"
  55. }
  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.  
  62. # Controls how temporary permissions/parents/meta should be accumulated
  63. #
  64. # The default behaviour is "deny"
  65. # If "accumulate": durations will be added to the existing expiry time
  66. # If "replace": durations will be replaced if the new duration is later than the current expiration
  67. # If "deny": the command will just fail if you try to add another node with the same expiry
  68. temporary-add-behaviour="deny"
  69.  
  70. # How should LuckPerms determine a users "primary" group.
  71. #
  72. # Available Options:
  73. # -> stored                 use the value stored against the users record in the file/database
  74. # -> parents-by-weight      just use the users most highly weighted parent
  75. # -> all-parents-by-weight  same as above, but calculates based upon all parents inherited from both directly and indirectly
  76. primary-group-calculation="parents-by-weight"
  77.  
  78.  
  79.  
  80.  
  81. # +------------------------------------------------------------------------+ #
  82. # |                        Permission Calculation                          | #
  83. # +------------------------------------------------------------------------+ #
  84.  
  85. # If the plugin should apply wildcard permissions.
  86. # If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered permissions matching
  87. # the wildcard.
  88. apply-wildcards=true
  89.  
  90. # If the plugin should parse regex permissions.
  91. # If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the node, and resolve &
  92. # apply all registered permissions matching the regex.
  93. apply-regex=true
  94.  
  95. # If the plugin should complete and apply shorthand permissions.
  96. # If set to true, LuckPerms will detect and expand shorthand node patterns.
  97. apply-shorthand=true
  98.  
  99. # If LuckPerms should resolve and apply permissions according to Sponge's implicit wildcard inheritance system.
  100. #
  101. # That being:
  102. # If a user has been granted "example", then the player should have also be automatically
  103. # granted "example.function", "example.another", "example.deeper.nesting", and so on.
  104. #
  105. # If this option is set to false, this system will not be applied.
  106. apply-sponge-implicit-wildcards=true
  107.  
  108. # If the plugin should apply Sponge default subject permissions.
  109. # Plugins can manipulate a set of default permissions granted to all users. If this option is set to false,
  110. # LuckPerms will ignore this data when considering if a player has a permission.
  111. apply-sponge-default-subjects=true
  112.  
  113. # Define special group weights for this server.
  114. # Default is just 0.
  115. group-weight {
  116. #  admin=10
  117. }
  118.  
  119.  
  120.  
  121.  
  122. # +------------------------------------------------------------------------+ #
  123. # |                      Meta Formatting & Stacking                        | #
  124. # +------------------------------------------------------------------------+ #
  125.  
  126. # Allows you to setup prefix/suffix stacking options.
  127. #
  128. # Available formats:
  129. # - highest
  130. # - lowest
  131. # - highest_own
  132. # - lowest_own
  133. # - highest_on_track_<track>
  134. # - lowest_on_track_<track>
  135. # - highest_not_on_track_<track>
  136. # - lowest_not_on_track_<track>
  137. #
  138. # Each element is added in the order listed.
  139. meta-formatting {
  140.   prefix {
  141.     format = [
  142.       "highest"
  143.     ]
  144.     start-spacer=""
  145.     middle-spacer=" "
  146.     end-spacer=""
  147.   }
  148.   suffix {
  149.     format = [
  150.       "highest"
  151.     ]
  152.     start-spacer=""
  153.     middle-spacer=" "
  154.     end-spacer=""
  155.   }
  156. }
  157.  
  158.  
  159.  
  160.  
  161. # +------------------------------------------------------------------------+ #
  162. # |                               Storage                                  | #
  163. # +------------------------------------------------------------------------+ #
  164.  
  165. # Which storage method the plugin should use.
  166. #
  167. # See: https://github.com/lucko/LuckPerms/wiki/Choosing-a-Storage-type
  168. # Currently supported: mysql, mariadb, postgresql, sqlite, h2, json, yaml, mongodb
  169.  
  170. # Fill out connection info below if you're using MySQL, MariaDB, PostgreSQL or MongoDB
  171. # If your MySQL server supports it, the "mariadb" option is preferred over "mysql".
  172. storage-method="json"
  173.  
  174. # When using a file-based storage type, LuckPerms can monitor the data files for changes, and then schedule automatic
  175. # updates when changes are detected.
  176. #
  177. # If you don't want this to happen, set this option to false.
  178. watch-files=true
  179.  
  180. # This block enables support for split datastores.
  181. split-storage {
  182.   enabled=false
  183.   methods {
  184.     user="h2"
  185.     group="h2"
  186.     track="h2"
  187.     uuid="h2"
  188.     log="h2"
  189.   }
  190. }
  191.  
  192. data {
  193.   # Uses standard DB engine port by default
  194.   # MySQL: 3306, PostgreSQL: 5432, MongoDB: 27017
  195.   # Specify as "host:port" if differs
  196.   address="localhost"
  197.  
  198.   database="minecraft"
  199.   username="root"
  200.   password=""
  201.   pool-size=10 # The size of the MySQL connection pool.
  202.  
  203.   # The prefix for all LuckPerms tables. Change this is you want to use different tables for different servers.
  204.   # This should *not* be set to "lp_" if you have previously ran LuckPerms v2.16.81 or earlier with this database.
  205.   table_prefix="luckperms_"
  206.  
  207.   # This option controls how frequently LuckPerms will perform a sync task.
  208.   # 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.
  209.   #
  210.   # This is disabled by default, as most users will not need it. However, if you're using a remote storage type
  211.   # without a messaging service setup, you may wish to set this value to something like 3.
  212.   #
  213.   # Set to -1 to disable the task completely.
  214.   sync-minutes=-1
  215. }
  216.  
  217. # Settings for the messaging service
  218. #
  219. # If enabled and configured, LuckPerms will use the messaging system to inform other
  220. # connected servers of changes. Use the command "/luckperms networksync" to push changes.
  221. # Data is NOT stored using this service. It is only used as a messaging platform.
  222. #
  223. # If you decide to enable this feature, you should set "sync-minutes" to -1, as there is no need for LuckPerms
  224. # to poll the database for changes.
  225. #
  226. # Available options:
  227. # bungee ==> uses the plugin messaging channels. Must be enabled on all connected servers to work.
  228. # redis ==> uses redis pub sub to push changes. Your redis server must be configured below.
  229. # none ==> nothing
  230. messaging-service="none"
  231.  
  232. # If LuckPerms should automatically push updates after a change has been made with a command.
  233. auto-push-updates=true
  234.  
  235. # Settings for Redis.
  236. # Port 6379 is used by default; set address to "host:port" if differs
  237. redis {
  238.   enabled=false
  239.   address="localhost"
  240.   password=""
  241. }
  242.  
  243.  
  244.  
  245.  
  246. # +------------------------------------------------------------------------+ #
  247. # |                         Default Assignments                            | #
  248. # +------------------------------------------------------------------------+ #
  249.  
  250. # This section allows you to define defaults to give users whenever they connect to the server.
  251. # The default assignments are highly configurable and conditional.
  252. #
  253. # There is one default assignment built into LuckPerms, which will add all users to the "default" group if they
  254. # are not a member of any other group. This setting cannot be disabled. However, you can use this section to add more of
  255. # your own.
  256. #
  257. # IMPORTANT:
  258. # In order to save storage space, LuckPerms does not store users who have no permissions defined, and are only a member
  259. # of the default group. Adding default assignments to this section will negate this effect. It is HIGHLY RECCOMENDED
  260. # that instead of assigning defaults here, you add permissions to the "default" group, or set the "default" group to inherit
  261. # other groups, and then use the group-name-rewrite rule above.
  262. #
  263. # It is also important to note that these rules are considered every time a player logs into the server, and are applied
  264. # directly to the user's data. Simply removing a rule here will not reserse the effect of that rule on any users who have
  265. # already had it applied to them.
  266. #
  267. # The "has" and "lacks" conditions below support standard boolean logic, using the 'and' & 'or' characters used in Java.
  268. # e.g. "(some.other.permission | some.permission.other) & some.thing.else" == a user has 'some.other.permission', or
  269. # 'some.permission.other', and they also have 'some.thing.else'
  270. #
  271. # Groups are represented by the permission node: group.<group name>
  272. # Per server and per world nodes are represented by: "server-world/permission" or "server/permission"
  273. #
  274. # Within conditions, permission nodes MUST be escaped using "<" and ">". See the example below.
  275. #
  276. # Explanation of the examples below: (they're just to demonstrate the features & use cases)
  277. #
  278. # rule1:
  279. # If a user is either in the vip or vip+ group, and they have the "titles.titlecollector" permission set to true, and the
  280. # "some.random.permission" set to false... if they're not in the group "prison_titlepack" on the "prison" server, then
  281. # give add them to the "prison_titlepack" group on the "prison" server, and remove "some.random.permission".
  282. #
  283. # rule2:
  284. # If the user isn't in any of the following groups on the skyblock server: sb_level1, sb_level2, sb_level3, then add
  285. # them to sb_level1 on the skyblock server.
  286. #
  287. # rule3:
  288. # If the user is a member of the default group, remove them from default, add them to member, and set their primary group
  289. # to member.
  290. #
  291. # WARNING: Unlike internal commands, this system does not ensure that a group exists before adding a user to it.
  292. # It also does not unsure that a user is a member of a group before making that group their primary group.
  293. #
  294. # Before you use "give: group.<name>" or "set-primary-group", make sure that the group exists, and that the user is
  295. # a member of the group.
  296. default-assignments {
  297. #  rule1 {
  298. #    if {
  299. #      has-true="(<group.vip> | <group.vip+>) & <titles.tilecollector>"
  300. #      has-false="<some.random.permission>"
  301. #      lacks="<prison/group.prison_titlepack>"
  302. #    }
  303. #    give = [
  304. #      "prison/group.prison_titlepack"
  305. #    ]
  306. #    take = [
  307. #      "some.random.permission"
  308. #    ]
  309. #  }
  310. #  rule2 {
  311. #    if {
  312. #      lacks="<skyblock/group.sb_level1> & <skyblock/group.sb_level2> & <skyblock/group.sb_level3>"
  313. #    }
  314. #    give = [
  315. #      "skyblock/group.sb_level1"
  316. #    ]
  317. #  }
  318. #  rule3 {
  319. #    if {
  320. #      has-true="<group.default>"
  321. #    }
  322. #    take = [
  323. #      "group.default"
  324. #    ]
  325. #    give = [
  326. #      "group.member"
  327. #    ]
  328. #    set-primary-group="member"
  329. #  }
  330. }
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