Advertisement
Guest User

Untitled

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