EtnoCraft

LuckPerms 2.9.11 - Configuración

Sep 13th, 2016
517
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.36 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: global
  10.  
  11. # If users on this server should have their global permissions applied.
  12. # If set to false, only server specific permissions will apply for users on this server
  13. include-global: true
  14.  
  15. # If users on this server should have their global world permissions applied.
  16. # If set to false, only world specific permissions will apply for users on this server
  17. include-global-world: true
  18.  
  19. # If users on this server should have global (non-server specific) groups applied
  20. apply-global-groups: true
  21.  
  22. # If users on this server should have global (non-world specific) groups applied
  23. apply-global-world-groups: true
  24.  
  25. # If this server is in offline or online mode.
  26. # This setting allows a player to have the same UUID across a network of offline mode/mixed servers.
  27.  
  28. # You should generally reflect the setting in server.properties here. Except when...
  29.  
  30. # 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
  31. # AND 'ip-forward' set to true in the BungeeCord config.yml
  32. # In this case, set online-mode in LuckPerms to true, despite the server being in offline mode.
  33.  
  34. # 2. You are only running one server instance using LuckPerms, (not a network)
  35. # 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)
  36.  
  37. # 3. If your proxy is running in offline mode, and you are using PaperSpigot (https://ci.destroystokyo.com/job/PaperSpigot/),
  38. # you should set "bungee-online-mode" to false in the paper.yml, and set "online-mode" to true in all LuckPerms configs.
  39. # This approach is thoroughly recommended for offline mode networks.
  40. online-mode: true
  41.  
  42. # If the plugin should apply wildcard permissions.
  43. # If set to true, LuckPerms will detect wildcard permissions, and resolve & apply all registered permissions matching
  44. # the wildcard.
  45. apply-wildcards: true
  46.  
  47. # If the plugin should parse regex permissions.
  48. # If set to true, LuckPerms will detect regex permissions, marked with "r=" at the start of the node, and resolve &
  49. # apply all registered permissions matching the regex.
  50. apply-regex: true
  51.  
  52. # If the plugin should complete and apply shorthand permissions.
  53. # If set to true, LuckPerms will detect and expand shorthand node patterns.
  54. apply-shorthand: true
  55.  
  56. # If the plugin should send log notifications to users whenever permissions are modified.
  57. log-notify: true
  58.  
  59. # If LuckPerms should print to console every time a plugin checks if a player has a permission
  60. debug-permission-checks: false
  61.  
  62. # 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.
  63. enable-ops: true
  64.  
  65. # If set to true, any user with the permission "luckperms.autoop" will automatically be granted server operator status.
  66. # This permission can be inherited, or set on specific servers/worlds, temporarily, etc.
  67. # Additionally, setting this to true will force the "enable-ops" option above to false. All users will be de-opped unless
  68. # they have the permission node, and the op/deop commands will be disabled.
  69. #
  70. # It is recommended that you use this option instead of assigning a single '*' permission.
  71. auto-op: true
  72.  
  73. # 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
  74. commands-allow-op: true
  75.  
  76. # The name of the server used within Vault operations. If you don't want Vault operations to be server specific, set this
  77. # to "global".
  78. vault-server: global
  79.  
  80. # If global permissions should be considered when retrieving meta or player groups
  81. vault-include-global: true
  82.  
  83. # Mirrors world names. Whenever LuckPerms checks what world a user is in, if the world name is in this list, the value assigned
  84. # will be sent forward for permission calculation instead.
  85. world-rewrite:
  86. #world_nether: world
  87. #world_the_end: world
  88.  
  89. # Rewrites group names. The underlying name of the group does not change, just the output in commands / placeholders / Vault.
  90. group-name-rewrite:
  91. default: Jugador
  92. administrador: Administrador
  93. operador: Operador
  94. moderador: Moderador
  95.  
  96. # Which storage method the plugin should use.
  97. # Currently supported: mysql, sqlite, h2, json, yaml, mongodb
  98. # Fill out connection info below if you're using MySQL or MongoDB
  99. storage-method: mysql
  100.  
  101. # This block enables support for split datastores.
  102. split-storage:
  103. enabled: false
  104. methods:
  105. user: h2
  106. group: h2
  107. track: h2
  108. uuid: h2
  109. log: h2
  110.  
  111. data:
  112. address: 127.0.0.1:3306
  113. database: 33533
  114. username: 33533
  115. password: '61a3547b1c'
  116.  
  117. # Set to -1 to disable. If this is the only instance accessing the datastore, you can disable syncing.
  118. # e.g. if you're using sqlite or flatfile, this can be set to -1 to save resources.
  119. sync-minutes: 3
Advertisement
Add Comment
Please, Sign In to add comment