SHARE
TWEET

Permissions

a guest Jun 29th, 2018 31 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. config-version: 19
  2.  
  3. # Enable database support. Disabling database support switches
  4. # zPermissions to its flat-file-based permissions store.
  5. database-support: true
  6.  
  7. # Set to true if this server should be in read-only mode. Only valid when
  8. # actually using a database. If set to read-only, the database account
  9. # for this server should also be granted read-only permissions on
  10. # zPermissions tables. (Not strictly required though.)
  11. database-read-only: false
  12.  
  13. # Settings for database (if enabled). This used to be in bukkit.yml before
  14. # Minecraft 1.12.
  15. database:
  16.   username: us3r
  17.   isolation: SERIALIZABLE
  18.   driver: org.sqlite.JDBC
  19.   password: passw0rd
  20.   url: jdbc:sqlite:plugins/zPermissions/zPermissions.db
  21.  
  22. # Whether region-based permissions are enabled. Requires a region plugin such
  23. # as WorldGuard or Residence. Setting this to false will save some processing
  24. # if you use a region plugin but don't use region-based permissions. Has no
  25. # effect if a region plugin is not present.
  26. region-support: true
  27.  
  28. # Groups may have a group permission node automatically assigned to their
  29. # members. This is the name of that permission node. It must be a string
  30. # suitable for Java's String.format() with one argument: the group name.
  31. # Omit or leave blank ('') to disable this feature.
  32. # This may also be a list of strings to automatically assign multiple
  33. # permissions.
  34. group-permission: group.%s
  35.  
  36. # Similar to group-permission, but only applied to "assigned" groups (groups
  37. # that the player is explicitly a member of, including the default group, but
  38. # not any inherited groups).
  39. # Omit or leave blank ('') to disable this feature.
  40. # This may also be a list of strings to automatically assign multiple
  41. # permissions.
  42. assigned-group-permission: ''
  43.  
  44. # Set to false if you want your assigned-group-permission (above) to never
  45. # include the default group.
  46. assigned-groups-can-include-default: true
  47.  
  48. # The default group. Players that are not explicitly members of any group
  49. # are considered members of this group.
  50. default-group: default
  51.  
  52. # Normally, membership in the default group is implicit, i.e. you are considered
  53. # a member of the default group if you are not a member of any group. Setting
  54. # this to true makes the membership explicit, writing out the default group
  55. # membership to storage on login.
  56. explicit-default-group-membership: false
  57.  
  58. # The default track. When the track name is omitted while using the /promote,
  59. # /demote, /setrank, and /unsetrank commands, this is the track used.
  60. default-track: default
  61.  
  62. # Directory where to load/store dumps. If this is not an absolute path, it
  63. # will be interpreted as relative to the server root.
  64. dump-directory: zPermissions-dumps
  65.  
  66. # Default timeout for temporary permissions, in seconds
  67. default-temp-permission-timeout: 60
  68.  
  69. # Track definitions. Each key should be the name of the track. The value
  70. # should be a list of group names in ascending order.
  71. tracks:
  72.   default:
  73.   - default
  74.   - somegroup
  75.   - someothergroup
  76.  
  77. # Name of the track used to determine a player's "primary group," a
  78. # concept often used by other plugins via the native API or Vault. A
  79. # player that does not have a track explicitly set via the
  80. # /permissions .. player .. settrack command will use this track
  81. # instead. Leave blank ('') to disable and use the highest-weight group
  82. # as the primary group.
  83. default-primary-group-track: ''
  84.  
  85. # If any problems occur while determining a player's permissions (e.g.
  86. # SQLExceptions, network errors, etc.), kick the player. This may be more
  87. # desirable to having the user have free reign with indeterminate permissions.
  88. kick-on-error: true
  89.  
  90. # Only valid if kick-on-error is true. If a problem occurs while determining
  91. # an op's permissions, then the op will only be kicked if this is true.
  92. kick-ops-on-error: false
  93.  
  94. # Interval, in minutes, in which to automatically refresh permissions from
  95. # the database. Set to a non-positive number to disable. Has no effect on
  96. # the flat-file storage method. DO NOT SET IT TOO LOW. Otherwise you run
  97. # the risk of refreshes overlapping or permissions changes inexplicably
  98. # being "forgotten."
  99. # Unless you have an external process modifying zPermissions tables, you
  100. # should have no need to enable this feature! (And even then, its use is
  101. # questionable...)
  102. auto-refresh-interval: -1
  103.  
  104. # By default, the refreshes set by auto-refresh-interval are conditional.
  105. # That is, the refreshes do not actually occur unless the data version
  106. # number (found in the table named DATA_VERSION by default) is different.
  107. # Set this to true if you wish to perform an unconditional refresh instead.
  108. # (Prior to 1.1, the refreshes were always unconditional.)
  109. auto-refresh-force: false
  110.  
  111. # Determines how inherited groups and assigned groups are resolved. When
  112. # true, each assigned group is fully resolved (itself + all ancestors)
  113. # before applying its permissions in assignment priority. (That is, groups
  114. # are flattened before being applied.) When false, all assigned groups and
  115. # their ancestor groups are treated as individual groups and are applied
  116. # in "topological order." <http://en.wikipedia.org/wiki/Topological_sorting>
  117. opaque-inheritance: true
  118.  
  119. # Determines when to apply player permissions. If true, player permissions
  120. # are interleaved with group-resolved permissions at every "level"
  121. # (universal, world, region, region/world). If false, all player permissions
  122. # are applied once all group permissions have been applied.
  123. interleaved-player-permissions: false
  124.  
  125. # If true, rank commands will broadcast changes to admins by default.
  126. # Otherwise, rank commands will broadcast to players with a custom
  127. # permission, e.g. zpermissions.notify.promote, etc.
  128. rank-admin-broadcast: false
  129.  
  130. # If region-support is enabled, this is the order in which region manager
  131. # plugins will be detected. The first plugin detected will be used.
  132. region-managers:
  133. - WorldGuard
  134. - Residence
  135. - Factions
  136. - Factoid
  137.  
  138. # If true, metadata resolution will follow group inheritence rules, exactly
  139. # like permissions.
  140. inherited-metadata: false
  141.  
  142. # If true, the Vault bridges included with zPermissions are used. If false,
  143. # the bridges that come with Vault are used. Has no effect if Vault is not
  144. # installed. The included ("native") bridges will almost always certainly
  145. # be more advanced/featureful. However, the option to turn them off is
  146. # provided should there be any compatibility problems.
  147. native-vault-bridges: true
  148.  
  149. # If true, the Vault Chat API methods getPlayerPrefix() and getPlayerSuffix()
  150. # will fall back to the player's primary group's prefix/suffix. Only matters
  151. # if native-vault-bridges is true. This should be enabled if you use a
  152. # chat formatting plugin that does not perform this fallback behavior
  153. # itself.
  154. vault-prefix-includes-group: true
  155.  
  156. # If true, the Vault Chat API methods getPlayerInfo*() will fall back to the
  157. # player's primary group's metadata. Only matters if native-vault-bridges
  158. # is true. This should be enabled if you use a metadata-using plugin
  159. # that does not perform this fallback behavior itself. Note it will affect
  160. # all Vault-using plugins.
  161. vault-metadata-includes-group: true
  162.  
  163. # Affects the behavior of the Vault Permission playerInGroup() method. If
  164. # true, playerInGroup() will only test against assigned groups. Otherwise,
  165. # it will test against assigned groups and their inherited ancestor groups.
  166. # Only matters if native-vault-bridges is true.
  167. vault-group-test-uses-assigned-only: false
  168.  
  169. # Affects the behavior of the Vault Permission getPlayerGroups() method.
  170. # If true, getPlayerGroups() will only return assigned groups. Otherwise,
  171. # it will return assigned groups and their inherited ancestor groups.
  172. # Only matters if native-vault-bridges is true.
  173. vault-get-groups-uses-assigned-only: false
  174.  
  175. # Specify a totally customized player prefix. Use an empty string to disable.
  176. # The following tokens in the format string are recognized:
  177. # %p - The player's prefix/suffix
  178. # %g - The player's primary group's prefix/suffix
  179. # %a - The prefixes/suffixes of *all* the player's groups. Affected by
  180. # vault-get-groups-uses-assigned-only above.
  181. # %A - Same as %a, but the with the order reversed.
  182. # To merge player and primary group prefixes/suffixes, you might set
  183. # vault-player-prefix-format to '%g%p' and vault-player-suffix-format to
  184. # '%p%g'
  185. vault-player-prefix-format: ''
  186.  
  187. # Same as vault-player-prefix-format, but for the player's suffix.
  188. vault-player-suffix-format: ''
  189.  
  190. # If true, any permissions/membership/metadata changes made through Vault
  191. # are logged at INFO level. Otherwise, they are logged at FINE (debug).
  192. log-vault-changes: false
  193.  
  194. # Enable debug logging.
  195. debug: false
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top