Advertisement
Guest User

confic

a guest
Feb 23rd, 2017
92
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.86 KB | None | 0 0
  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 this server is in offline or online mode.
  30. # This setting allows a player to have the same UUID across a network of offline mode/mixed servers.
  31. #
  32. # You should generally reflect the setting in server.properties here. Except when...
  33. #
  34. # 1. You have Sponge servers connected to a BungeeCord proxy, with online-mode set to false, but 'bungeecord ip-forwarding'
  35. # set to true in the sponge/global.conf AND 'ip-forward' set to true in the BungeeCord config.yml
  36. # In this case, set online-mode in LuckPerms to true, despite the server being in offline mode.
  37. #
  38. # 2. You are only running one server instance using LuckPerms, (not a network) In this case, set online-mode to true no
  39. # matter what is set in server.properties. (we can just fallback to the servers uuid cache)
  40. online-mode=true
  41.  
  42. # If the plugin should send log notifications to users whenever permissions are modified.
  43. log-notify=true
  44.  
  45. # Mirrors world names. Whenever LuckPerms checks what world a user is in, if the world name is in this list, the value assigned
  46. # will be sent forward for permission calculation instead.
  47. world-rewrite {
  48. # world_nether="world"
  49. # world_the_end="world"
  50. }
  51.  
  52. # Rewrites group names. The underlying name of the group does not change, just the output in commands / placeholders / Vault.
  53. group-name-rewrite {
  54. # default="Member"
  55. }
  56.  
  57. # Controls how temporary permissions/parents/meta should be accumulated
  58. #
  59. # The default behaviour is "deny"
  60. # If "accumulate": durations will be added to the existing expiry time
  61. # If "replace": durations will be replaced if the new duration is later than the current expiration
  62. # If "deny": the command will just fail if you try to add another node with the same expiry
  63. temporary-add-behaviour="deny"
  64.  
  65.  
  66.  
  67.  
  68. # +------------------------------------------------------------------------+ #
  69. # | Permission Calculation | #
  70. # +------------------------------------------------------------------------+ #
  71.  
  72. # If the plugin should apply wildcard permissions.
  73. # If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered permissions matching
  74. # the wildcard.
  75. apply-wildcards=true
  76.  
  77. # If the plugin should parse regex permissions.
  78. # If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the node, and resolve &
  79. # apply all registered permissions matching the regex.
  80. apply-regex=true
  81.  
  82. # If the plugin should complete and apply shorthand permissions.
  83. # If set to true, LuckPerms will detect and expand shorthand node patterns.
  84. apply-shorthand=true
  85.  
  86. # Define special group weights for this server.
  87. # Default is just 0.
  88. group-weight {
  89. # admin=10
  90. }
  91.  
  92.  
  93.  
  94.  
  95. # +------------------------------------------------------------------------+ #
  96. # | Meta Formatting & Stacking | #
  97. # +------------------------------------------------------------------------+ #
  98.  
  99. # Allows you to setup prefix/suffix stacking options.
  100. #
  101. # Available formats:
  102. # - highest
  103. # - lowest
  104. # - highest_own
  105. # - lowest_own
  106. # - highest_on_track_<track>
  107. # - lowest_on_track_<track>
  108. #
  109. # Each element is added in the order listed.
  110. meta-formatting {
  111. prefix {
  112. format = [
  113. "highest"
  114. ]
  115. start-spacer=""
  116. middle-spacer=" "
  117. end-spacer=""
  118. }
  119. suffix {
  120. format = [
  121. "highest"
  122. ]
  123. start-spacer=""
  124. middle-spacer=" "
  125. end-spacer=""
  126. }
  127. }
  128.  
  129.  
  130.  
  131.  
  132. # +------------------------------------------------------------------------+ #
  133. # | Storage | #
  134. # +------------------------------------------------------------------------+ #
  135.  
  136. # Which storage method the plugin should use.
  137. # Currently supported: mysql, postgresql, sqlite, h2, json, yaml, mongodb
  138. # Fill out connection info below if you're using MySQL, PostgreSQL or MongoDB
  139. storage-method="h2"
  140.  
  141. # This block enables support for split datastores.
  142. split-storage {
  143. enabled=false
  144. methods {
  145. user="h2"
  146. group="h2"
  147. track="h2"
  148. uuid="h2"
  149. log="h2"
  150. }
  151. }
  152.  
  153. data {
  154. # Uses standard DB engine port by default
  155. # MySQL: 3306, PostgreSQL: 5432, MongoDB: 27017
  156. # Specify as "host:port" if differs
  157. address="localhost"
  158.  
  159. database="minecraft"
  160. username="root"
  161. password=""
  162. pool-size=10 # The size of the MySQL connection pool.
  163.  
  164. # The prefix for all LuckPerms tables. Change this is you want to use different tables for different servers.
  165. # This should *not* be set to "lp_" if you have previously ran LuckPerms v2.16.81 or earlier with this database.
  166. table_prefix="luckperms_"
  167.  
  168. # Set to -1 to disable. If this is the only instance accessing the datastore, you can disable syncing.
  169. # e.g. if you're using sqlite or flatfile, this can be set to -1 to save resources.
  170. sync-minutes=3
  171. }
  172.  
  173. # Settings for the messaging service
  174. #
  175. # If enabled and configured, LuckPerms will use the messaging system to inform other
  176. # connected servers of changes. Use the command "/luckperms networksync" to push changes.
  177. # Data is NOT stored using this service. It is only used as a messaging platform.
  178. #
  179. # If you decide to enable this feature, you should set "sync-minutes" to -1, as there is no need for LuckPerms
  180. # to poll the database for changes.
  181. #
  182. # Available options:
  183. # bungee ==> uses the plugin messaging channels. Must be enabled on all connected servers to work.
  184. # redis ==> uses redis pub sub to push changes. Your redis server must be configured below.
  185. # none ==> nothing
  186. messaging-service="none"
  187.  
  188. # Settings for Redis.
  189. # Port 6379 is used by default; set address to "host:port" if differs
  190. redis {
  191. enabled=false
  192. address="localhost"
  193. password=""
  194. }
  195.  
  196.  
  197.  
  198.  
  199. # +------------------------------------------------------------------------+ #
  200. # | Default Assignments | #
  201. # +------------------------------------------------------------------------+ #
  202.  
  203. # This section allows you to define defaults to give users whenever they connect to the server.
  204. # The default assignments are highly configurable and conditional.
  205. #
  206. # There is one default assignment built into LuckPerms, which will add all users to the "default" group if they
  207. # are not a member of any other group. This setting cannot be disabled. However, you can use this section to add more of
  208. # your own.
  209. #
  210. # IMPORTANT:
  211. # In order to save storage space, LuckPerms does not store users who have no permissions defined, and are only a member
  212. # of the default group. Adding default assignments to this section will negate this effect. It is HIGHLY RECCOMENDED
  213. # that instead of assigning defaults here, you add permissions to the "default" group, or set the "default" group to inherit
  214. # other groups, and then use the group-name-rewrite rule above.
  215. #
  216. # It is also important to note that these rules are considered every time a player logs into the server, and are applied
  217. # directly to the user's data. Simply removing a rule here will not reserse the effect of that rule on any users who have
  218. # already had it applied to them.
  219. #
  220. # The "has" and "lacks" conditions below support standard boolean logic, using the 'and' & 'or' characters used in Java.
  221. # e.g. "(some.other.permission | some.permission.other) & some.thing.else" == a user has 'some.other.permission', or
  222. # 'some.permission.other', and they also have 'some.thing.else'
  223. #
  224. # Groups are represented by the permission node: group.<group name>
  225. # Per server and per world nodes are represented by: "server-world/permission" or "server/permission"
  226. #
  227. # Within conditions, permission nodes MUST be escaped using "<" and ">". See the example below.
  228. #
  229. # Explanation of the examples below: (they're just to demonstrate the features & use cases)
  230. #
  231. # rule1:
  232. # If a user is either in the vip or vip+ group, and they have the "titles.titlecollector" permission set to true, and the
  233. # "some.random.permission" set to false... if they're not in the group "prison_titlepack" on the "prison" server, then
  234. # give add them to the "prison_titlepack" group on the "prison" server, and remove "some.random.permission".
  235. #
  236. # rule2:
  237. # If the user isn't in any of the following groups on the skyblock server: sb_level1, sb_level2, sb_level3, then add
  238. # them to sb_level1 on the skyblock server.
  239. #
  240. # rule3:
  241. # If the user is a member of the default group, remove them from default, add them to member, and set their primary group
  242. # to member.
  243. #
  244. # WARNING: Unlike internal commands, this system does not ensure that a group exists before adding a user to it.
  245. # It also does not unsure that a user is a member of a group before making that group their primary group.
  246. #
  247. # Before you use "give: group.<name>" or "set-primary-group", make sure that the group exists, and that the user is
  248. # a member of the group.
  249. default-assignments {
  250. # rule1 {
  251. # if {
  252. # has-true="(<group.vip> | <group.vip+>) & <titles.tilecollector>"
  253. # has-false="<some.random.permission>"
  254. # lacks="<prison/group.prison_titlepack>"
  255. # }
  256. # give = [
  257. # "prison/group.prison_titlepack"
  258. # ]
  259. # take = [
  260. # "some.random.permission"
  261. # ]
  262. # }
  263. # rule2 {
  264. # if {
  265. # lacks="<skyblock/group.sb_level1> & <skyblock/group.sb_level2> & <skyblock/group.sb_level3>"
  266. # }
  267. # give = [
  268. # "skyblock/group.sb_level1"
  269. # ]
  270. # }
  271. # rule3 {
  272. # if {
  273. # has-true="<group.default>"
  274. # }
  275. # take = [
  276. # "group.default"
  277. # ]
  278. # give = [
  279. # "group.member"
  280. # ]
  281. # set-primary-group="member"
  282. # }
  283. }
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement