Advertisement
Guest User

Untitled

a guest
Sep 23rd, 2017
404
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.61 KB | None | 0 0
  1. ##############################################################################
  2. # +------------------------------------------------------------------------+ #
  3. # | LuckPerms Configuration | #
  4. # | https://github.com/lucko/LuckPerms | #
  5. # +------------------------------------------------------------------------+ #
  6. ##############################################################################
  7.  
  8. # The name of the server, used for server specific permissions. Set to 'global' to disable.
  9. server: skyblock
  10. # If users on this server should have their global permissions/groups applied.
  11. include-global: true
  12.  
  13. # If this server is in offline or online mode.
  14. # This setting allows a player to have the same UUID across a network of offline mode/mixed servers.
  15.  
  16. # You should generally reflect the setting in server.properties here. Except when...
  17.  
  18. # 1. You have Spigot servers connected to a BungeeCord proxy, with online-mode set to false, but 'bungeecord' set to true in the spigot.yml
  19. # AND 'ip-forward' set to true in the BungeeCord config.yml
  20. # In this case, set online-mode in LuckPerms to true, despite the server being in offline mode.
  21.  
  22. # 2. You are only running one server instance using LuckPerms, (not a network)
  23. # In this case, set online-mode to true no matter what is set in server.properties. (we can just fallback to the servers uuid cache)
  24.  
  25. # 3. If your proxy is running in offline mode, and you are using PaperSpigot (https://ci.destroystokyo.com/job/PaperSpigot/),
  26. # you should set "bungee-online-mode" to false in the paper.yml, and set "online-mode" to true in all LuckPerms configs.
  27. # This approach is thoroughly recommended for offline mode networks.
  28. online-mode: true
  29.  
  30. # If the plugin should apply wildcard permissions.
  31. # If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered permissions matching
  32. # the wildcard. This will only work for plugins that define all of their permissions to the server.
  33. apply-wildcards: true
  34.  
  35. # If the plugin should parse regex permissions.
  36. # If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the node, and resolve &
  37. # apply all registered permissions matching the regex. This will only work for plugins that define all of their
  38. # permissions to the server.
  39. apply-regex: true
  40.  
  41. # If the plugin should complete and apply shorthand permissions.
  42. # If set to true, LuckPerms will detect and expand shorthand node patterns.
  43. apply-shorthand: true
  44.  
  45. # If the plugin should send log notifications to users whenever permissions are modified.
  46. log-notify: false
  47.  
  48. # If the vanilla OP system is enabled. If set to false, all users will be de-opped, and the op/deop commands will be disabled.
  49. enable-ops: true
  50.  
  51. # If set to true, any user with the permission "luckperms.autoop" will automatically be granted server operator status.
  52. # This permission can be inherited, or set on specific servers/worlds, temporarily, etc.
  53. # Additionally, setting this to true will force the "enable-ops" option above to false. All users will be de-opped unless
  54. # they have the permission node, and the op/deop commands will be disabled.
  55. #
  56. # It is recommended that you use this option instead of assigning a single '*' permission.
  57. auto-op: false
  58.  
  59. # If opped players should be allowed to use LuckPerms commands. Set to false to only allow users who have the permissions access to the commands
  60. commands-allow-op: true
  61.  
  62. # The name of the server used within Vault operations. If you don't want Vault operations to be server specific, set this
  63. # to "global".
  64. vault-server: skyblock
  65.  
  66. # If global permissions should be considered when retrieving meta or player groups
  67. vault-include-global: true
  68.  
  69. # Which storage method the plugin should use.
  70. # Currently supported: mysql, sqlite, h2, json, yaml, mongodb
  71. # Fill out connection info below if you're using MySQL or MongoDB
  72. storage-method: "mariadb"
  73.  
  74. # This block enables support for split datastores.
  75. # Only touch this if you're sure that you know what you're doing.
  76. # I (the author) do not endorse nor recommend the use of this feature.
  77. split-storage:
  78. enabled: false
  79. methods:
  80. user: h2
  81. group: h2
  82. track: h2
  83. uuid: h2
  84. log: h2
  85.  
  86. data:
  87. address: 66.70.180.76
  88.  
  89. database: luckperms
  90. username: luckperms
  91. password: ''
  92. pool-size: 10 # The size of the MySQL connection pool.
  93.  
  94. # Set to -1 to disable. If this is the only instance accessing the datastore, you can disable syncing
  95. # e.g. if you're using sqlite or flatfile, this can be set to -1 to save resources.
  96. sync-minutes: 3
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement