6TdDYERe

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