Advertisement
Guest User

Untitled

a guest
Dec 28th, 2017
453
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 18.51 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: global
  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 servers own UUID cache/lookup facility should be used when there is no record for a player
  70. # in the LuckPerms cache.
  71. #
  72. # Since BungeeCord doesn't maintain it's own UUID cache, when this option is true, LuckPerms will
  73. # try to find a uuid for a username using RedisBungee, if installed.
  74. use-server-uuid-cache: false
  75.  
  76. # If set to true, LuckPerms will allow usernames with non alphanumeric characters.
  77. #
  78. # Note that due to the design of the storage implementation, usernames must still be
  79. # 16 characters or less.
  80. allow-invalid-usernames: false
  81.  
  82. # If LuckPerms should produce extra logging output when it handles logins.
  83. # Useful if you're having issues with UUID forwarding or data not being loaded.
  84. debug-logins: false
  85.  
  86. # If LuckPerms should ensure all players have permission data when they connect to the server.
  87. #
  88. # When set to true, LuckPerms will cancel login attempts if it is unable to load permissions data
  89. # for a user, of if the storage provider is unavailable.
  90. #
  91. # When set to false, LuckPerms will allow a player to connect regardless of whether their
  92. # permissions data could be loaded.
  93. #
  94. # This option does not exist on other platforms, and effectively defaults to true - however,
  95. # the option is provided on BungeeCord, as it is less likely to be so dependant on permissions.
  96. cancel-failed-logins: false
  97.  
  98. # If the plugin should send log notifications to users whenever permissions are modified.
  99. log-notify: true
  100.  
  101. # Mirrors world names. Whenever LuckPerms checks what world a user is in, if the world name is in
  102. # this list, the value assigned will be sent forward for permission calculation instead.
  103. world-rewrite:
  104. # world_nether: world
  105. # world_the_end: world
  106.  
  107. # Controls how temporary permissions/parents/meta should be accumulated
  108. #
  109. # The default behaviour is "deny"
  110. # If "accumulate": durations will be added to the existing expiry time
  111. # If "replace": durations will be replaced if the new duration is later than the current expiration
  112. # If "deny": the command will just fail if you try to add another node with the same expiry
  113. temporary-add-behaviour: deny
  114.  
  115. # How should LuckPerms determine a users "primary" group.
  116. #
  117. # Available Options:
  118. # -> stored use the value stored against the users record in the file/database
  119. # -> parents-by-weight just use the users most highly weighted parent
  120. # -> all-parents-by-weight same as above, but calculates based upon all parents inherited from both
  121. # directly and indirectly
  122. primary-group-calculation: parents-by-weight
  123.  
  124. # If set to false, the plugin will allow a Users primary group to be removed with the
  125. # 'parent remove' command, and will set their primary group back to default.
  126. prevent-primary-group-removal: false
  127.  
  128. # If the plugin should check for "extra" permissions with users run LP commands.
  129. #
  130. # These extra permissions allow finer control over what users can do with each command, and
  131. # who they have access to edit.
  132. #
  133. # The permissions are *not* static, unlike the 'base' permisssions, and will depend upon the
  134. # arguments given within the command.
  135. argument-based-command-permissions: false
  136.  
  137.  
  138.  
  139.  
  140. # +----------------------------------------------------------------------------------------------+ #
  141. # | Permission Calculation | #
  142. # +----------------------------------------------------------------------------------------------+ #
  143.  
  144. # If the plugin should apply wildcard permissions.
  145. # If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered
  146. # permissions matching the wildcard.
  147. apply-wildcards: true
  148.  
  149. # If the plugin should parse regex permissions.
  150. # If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the
  151. # node, and resolve & apply all registered permissions matching the regex.
  152. apply-regex: true
  153.  
  154. # If the plugin should complete and apply shorthand permissions.
  155. # If set to true, LuckPerms will detect and expand shorthand node patterns.
  156. apply-shorthand: true
  157.  
  158. # If the plugin should apply the permissions & groups defined in the BungeeCord config.yml
  159. # If set to false, LuckPerms will ignore these values.
  160. apply-bungee-config-permissions: true
  161.  
  162. # Define special group weights for this server.
  163. # Default is just 0.
  164. group-weight:
  165. # admin: 10
  166.  
  167.  
  168.  
  169.  
  170. # +----------------------------------------------------------------------------------------------+ #
  171. # | Meta Formatting & Stacking | #
  172. # +----------------------------------------------------------------------------------------------+ #
  173.  
  174. # Allows you to setup prefix/suffix stacking options.
  175. #
  176. # Available formats:
  177. # - highest
  178. # - lowest
  179. # - highest_own
  180. # - lowest_own
  181. # - highest_inherited
  182. # - lowest_inherited
  183. # - highest_on_track_<track>
  184. # - lowest_on_track_<track>
  185. # - highest_not_on_track_<track>
  186. # - lowest_not_on_track_<track>
  187. #
  188. # Each element is added in the order listed.
  189. meta-formatting:
  190. prefix:
  191. format:
  192. - "highest"
  193. start-spacer: ""
  194. middle-spacer: " "
  195. end-spacer: ""
  196. suffix:
  197. format:
  198. - "highest"
  199. start-spacer: ""
  200. middle-spacer: " "
  201. end-spacer: ""
  202.  
  203.  
  204.  
  205.  
  206. # +----------------------------------------------------------------------------------------------+ #
  207. # | Storage | #
  208. # +----------------------------------------------------------------------------------------------+ #
  209.  
  210. # Which storage method the plugin should use.
  211. #
  212. # See: https://github.com/lucko/LuckPerms/wiki/Choosing-a-Storage-type
  213. # Currently supported: mysql, mariadb, postgresql, sqlite, h2, json, yaml, hocon, mongodb
  214. #
  215. # Fill out connection info below if you're using MySQL, MariaDB, PostgreSQL or MongoDB
  216. # If your MySQL server supports it, the "mariadb" option is preferred over "mysql".
  217. storage-method: mysql
  218.  
  219. # When using a file-based storage type, LuckPerms can monitor the data files for changes, and then
  220. # schedule automatic updates when changes are detected.
  221. #
  222. # If you don't want this to happen, set this option to false.
  223. watch-files: true
  224.  
  225. # This block enables support for split datastores.
  226. split-storage:
  227. enabled: false
  228. methods:
  229. user: h2
  230. group: h2
  231. track: h2
  232. uuid: h2
  233. log: h2
  234.  
  235. data:
  236. # Uses standard DB engine port by default
  237. # MySQL: 3306, PostgreSQL: 5432, MongoDB: 27017
  238. # Specify as "host:port" if differs
  239. address: localhost
  240.  
  241. database: minecraft
  242. username: root
  243. password: 'MONMDP-LOL'
  244. # These settings apply to the MySQL connection pool.
  245. # The default values will be suitable for the majority of users.
  246. # Do not change these settings unless you know what you're doing!
  247. pool-settings:
  248.  
  249. # Sets the maximum size of the MySQL connection pool.
  250. # Basically this value will determine the maximum number of actual
  251. # connections to the database backend.
  252. #
  253. # More information about determining the size of connection pools can be found here:
  254. # https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
  255. maximum-pool-size: 10
  256.  
  257. # Sets the minimum number of idle connections that the pool will try to maintain.
  258. #
  259. # For maximum performance and responsiveness to spike demands, it is recommended to not set
  260. # this value and instead allow the pool to act as a fixed size connection pool.
  261. # (set this value to the same as 'maximum-pool-size')
  262. minimum-idle: 10
  263.  
  264. # This setting controls the maximum lifetime of a connection in the pool in milliseconds.
  265. # The value should be at least 30 seconds less than any database or infrastructure imposed
  266. # connection time limit.
  267. maximum-lifetime: 1800000 # 30 minutes
  268.  
  269. # This setting controls the maximum number of milliseconds that the plugin will wait for a
  270. # connection from the pool, before timing out.
  271. connection-timeout: 15000 # 15 seconds
  272.  
  273. # This setting allows you to define extra properties for connections.
  274. properties:
  275. useUnicode: true
  276. characterEncoding: utf8
  277.  
  278. # The prefix for all LuckPerms tables. Change this is you want to use different tables for
  279. # different servers.
  280. #
  281. # This should *not* be set to "lp_" if you have previously ran LuckPerms v2.16.81 or earlier with
  282. # this database.
  283. table_prefix: 'luckperms_'
  284.  
  285. # The prefix to use for all LuckPerms collections. Change this if you want to use different
  286. # collections for different servers. The default is no prefix.
  287. mongodb_collection_prefix: ''
  288.  
  289. # This option controls how frequently LuckPerms will perform a sync task.
  290. # A sync task will refresh all data from the storage, and ensure that the most up-to-date data is
  291. # being used by the plugin.
  292. #
  293. # This is disabled by default, as most users will not need it. However, if you're using a remote
  294. # storage type without a messaging service setup, you may wish to set this value to something like
  295. # 3.
  296. #
  297. # Set to -1 to disable the task completely.
  298. sync-minutes: -1
  299.  
  300. # Settings for the messaging service
  301. #
  302. # If enabled and configured, LuckPerms will use the messaging system to inform other
  303. # connected servers of changes. Use the command "/luckpermsbungee networksync" to push changes.
  304. # Data is NOT stored using this service. It is only used as a messaging platform.
  305. #
  306. # If you decide to enable this feature, you should set "sync-minutes" to -1, as there is no need for
  307. # LuckPerms to poll the database for changes.
  308. #
  309. # Available options:
  310. # -> bungee uses the plugin messaging channels. Must be enabled on all connected servers to
  311. # work.
  312. # -> redis uses redis pub sub to push changes. Your redis server must be configured below.
  313. # -> redisbungee uses redis pub sub to push changes, using RedisBungee's API. You need to have the
  314. # RedisBungee plugin installed.
  315. # -> none nothing
  316. messaging-service: none
  317.  
  318. # If LuckPerms should automatically push updates after a change has been made with a command.
  319. auto-push-updates: true
  320.  
  321. # If LuckPerms should push logging entries to connected servers via the messaging service.
  322. push-log-entries: true
  323.  
  324. # If LuckPerms should broadcast received logging entries to players on this platform.
  325. #
  326. # If you have LuckPerms installed on your backend servers as well as a BungeeCord proxy, you should
  327. # set this option to false on either your backends or your proxies, to avoid players being messaged
  328. # twice about log entries.
  329. broadcast-received-log-entries: false
  330.  
  331. # Settings for Redis.
  332. # Port 6379 is used by default; set address to "host:port" if differs
  333. redis:
  334. enabled: false
  335. address: localhost
  336. password: ''
  337.  
  338.  
  339.  
  340.  
  341. # +----------------------------------------------------------------------------------------------+ #
  342. # | Default Assignments | #
  343. # +----------------------------------------------------------------------------------------------+ #
  344.  
  345. # This section allows you to define defaults to give users whenever they connect to the server.
  346. # The default assignments are highly configurable and conditional.
  347. #
  348. # There is one default assignment built into LuckPerms, which will add all users to the "default"
  349. # group if they are not a member of any other group. This setting cannot be disabled. However, you
  350. # can use this section to add more of your own.
  351. #
  352. # IMPORTANT:
  353. # In order to save storage space, LuckPerms does not store users who have no permissions defined,
  354. # and are only a member of the default group. Adding default assignments to this section will negate
  355. # this effect. It is HIGHLY RECCOMENDED that instead of assigning defaults here, you add permissions
  356. # to the "default" group, or set the "default" group to inherit other groups, and then use the
  357. # group-name-rewrite rule above.
  358. #
  359. # It is also important to note that these rules are considered every time a player logs into the
  360. # server, and are applied directly to the user's data. Simply removing a rule here will not reverse
  361. # the effect of that rule on any users who have already had it applied to them.
  362. #
  363. # The "has" and "lacks" conditions below support standard boolean logic, using the 'and' & 'or'
  364. # characters used in Java.
  365. # e.g. "(some.other.permission | some.permission.other) & some.thing.else" == a user has
  366. # 'some.other.permission', or 'some.permission.other', and they also have 'some.thing.else'
  367. #
  368. # Groups are represented by the permission node: group.<group name>
  369. # Per server and per world nodes are represented by "server-world/permission" or "server/permission"
  370. #
  371. # Within conditions, permission nodes MUST be escaped using "<" and ">". See the example below.
  372. #
  373. # Explanation of the examples below: (they're just to demonstrate the features & use cases)
  374. #
  375. # rule1:
  376. # If a user is either in the vip or vip+ group, and they have the "titles.titlecollector" permission
  377. # set to true, and the "some.random.permission" set to false... if they're not in the group
  378. # "prison_titlepack" on the "prison" server, then give add them to the "prison_titlepack" group on
  379. # the "prison" server, and remove "some.random.permission".
  380. #
  381. # rule2:
  382. # If the user isn't in any of the following groups on the skyblock server: sb_level1, sb_level2,
  383. # sb_level3, then add them to sb_level1 on the skyblock server.
  384. #
  385. # rule3:
  386. # If the user is a member of the default group, remove them from default, add them to member, and
  387. # set their primary group to member.
  388. #
  389. # WARNING: Unlike internal commands, this system does not ensure that a group exists before adding
  390. # a user to it. It also does not unsure that a user is a member of a group before making that group
  391. # their primary group.
  392. #
  393. # Before you use "give: group.<name>" or "set-primary-group", make sure that the group exists, and
  394. # that the user is a member of the group.
  395. default-assignments:
  396. # rule1:
  397. # if:
  398. # has-true: (<group.vip> | <group.vip+>) & <titles.tilecollector>
  399. # has-false: <some.random.permission>
  400. # lacks: <prison/group.prison_titlepack>
  401. # give:
  402. # - prison/group.prison_titlepack
  403. # take:
  404. # - some.random.permission
  405. # rule2:
  406. # if:
  407. # lacks: <skyblock/group.sb_level1> & <skyblock/group.sb_level2> & <skyblock/group.sb_level3>
  408. # give:
  409. # - skyblock/group.sb_level1
  410. # rule3:
  411. # if:
  412. # has-true: <group.default>
  413. # take:
  414. # - group.default
  415. # give:
  416. # - group.member
  417. # set-primary-group: member
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement