Advertisement
Guest User

Untitled

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