Advertisement
Guest User

Untitled

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