Skip to content

Configuration

FunnyGuilds has a handful of its own configuration value types besides the built-in ones (String, Int, boolean…). This page collects all of them, along with their possible values and examples — for what a specific option does, see the feature page it belongs to (e.g. Guilds or Territories & protection).

Startup conflict checking is optional and disabled by default. Enable it in config.yml with:

prevent-uuid-conflicts: true # default: false

When enabled, it checks for an identical username stored with different UUIDs in YAML or SQL before loading users and guilds. Comparison is case sensitive: Steve and steve can be separate, valid offline-mode accounts. A conflict aborts FunnyGuilds startup, not stopping the server from running. The plugin does not automatically merge or delete accounts or save partially loaded data. With the check enabled, unreadable YAML files or missing identity data in YAML also stop loading with a short summary. With the check disabled, unreadable YAML files are skipped with an error summary.

This option does not reject logins, account creation or username changes. Another account may use a player’s old username after that player renames their account outside the server. Both accounts may remain stored under the same name until the previous owner rejoins, so enabling the check can stop the next startup. Leave prevent-uuid-conflicts: false on servers where this is valid behaviour. FunnyGuilds does not replace authentication plugins or their username policies.

For safe recovery instructions, see the FAQ.

A type used to validate strings — names, tags, etc.

Predefined values:

Value Description
LOWERCASE Lowercase letters only
UPPERCASE Uppercase letters only
DIGITS Digits only
LOWERCASE_DIGITS Lowercase letters and digits
UPPERCASE_DIGITS Uppercase letters and digits
LETTERS Lowercase and uppercase letters
LETTERS_DIGITS Lowercase and uppercase letters plus digits
LETTERS_DIGITS_UNDERSCORE Lowercase and uppercase letters, digits and underscores

This type also accepts a custom regular expression (it can be tested with regex101, for example).

Format: <value><unit><value><unit><...>

Units:

  • s — seconds
  • m — minutes
  • h — hours
  • d — days

Example: 1m30s — 1.5 minutes.

A Bukkit material name (block or item), e.g. DIAMOND or ender_crystal — case doesn’t matter. The full list of names is in the org.bukkit.Material documentation.

Format: <amount> <MATERIAL>[:<data>] [attribute:value] [attribute:value] ...

Attributes (all optional, in any order):

Attribute Value Description
name / displayname text Item name (& colors; _ becomes a space)
lore line1#line2#... Item lore, lines separated by #
enchant / enchantment ENCHANTMENT:level A single enchantment
enchants / enchantments E1:l1,E2:l2 Several enchantments at once
skullowner nickname The owner of the player head
flags / itemflags FLAG1,FLAG2 Item flags (ItemFlag)
armorcolor r_g_b Leather armor color

Example: 1 diamond name:&bReward_for_the_first_guild_on_the_server — creates a diamond named “Reward for the first guild on the server”.

Item names and lore are non-italic by default. This also applies to guild-item-library definitions in items.yml and GUI item text. You can explicitly enable italics, for example <italic>Golden key</italic>.

# priority: <value> (0 to 127) # 1*
items: (/en/configuration/#itemstack)
- <item 1>
- <item 2>
- ...
exp: <value>
money: <value> (requires the Vault plugin)
# ranking: <value> # 2*

1* — the priority only needs to be given for requirements that depend on held permissions.

2* — the ranking value only needs to be given in contexts such as creating a guild or joining one.

The value-formatting section in config.yml controls placeholders ending in -FORMAT. The user and guild maps use metric IDs such as points, kdr, avg_points and wars_won. The ping list controls player ping.

value-formatting:
user:
points:
- '*-749 &4{VALUE}'
- '750-999 &c{VALUE}'
- '1000-1499 &a{VALUE}'
- '1500-* &6&l{VALUE}'
kills: []
deaths: []
assists: []
logouts: []
kdr:
- '0.0-1.0 &c{VALUE}'
- '1.0-2.0 &e{VALUE}'
- '2.0-* &a{VALUE}'
kda: []
guild:
points:
- '*-749 &4{VALUE}'
- '750-999 &c{VALUE}'
- '1000-1499 &a{VALUE}'
- '1500-* &6&l{VALUE}'
kills: []
deaths: []
assists: []
logouts: []
kdr: []
kda: []
avg_points:
- '*-999 &c{VALUE}'
- '1000-* &a{VALUE} points'
avg_kills: []
avg_deaths: []
avg_assists: []
avg_logouts: []
avg_kdr: []
avg_kda: []
wars_won: []
wars_lost: []
war_streak: []
ping:
- '0-75 &a{VALUE}'
- '76-150 &e{VALUE}'
- '151-* &c{VALUE}'

Entries use min-max template. Templates support spaces, legacy colors, hex and MiniMessage. Only the local {VALUE} is replaced; other placeholders and PAPI are not expanded inside a rule.

The first matching entry wins, including overlapping and duplicate ranges. Both integer boundaries are inclusive (0-1 includes 1). If either boundary is decimal, the upper boundary is exclusive (0.0-1.0 excludes 1). Use decimal boundaries for KDR/KDA. * stands for an int boundary (−2147483648 to 2147483647); a negative range can be written as *--1.

Rules match the value before rounding. New -FORMAT variants display fractional numbers with a dot and two decimal places, including when no rule matches. A missing key, [] or a gap returns the plain value. A missing guild returns neutral 0 or 0.00 without applying the rule for a real zero result. Ping is passed through unchanged: Bukkit profiles return 0 for offline players, while other profiles may return -1; a separate negative range can describe it.

Defaults color player points and both total and average guild points (up to 749: dark red, 750–999: red, 1000–1499: green, from 1500: bold gold), and ping (0–75: green, 76–150: yellow, from 151: red). Generated configuration includes an entry for every listed metric. Other metrics default to empty lists [] and remain neutral; replace these with rules to set thresholds and colors (as shown for KDR in the example). Existing placeholders without -FORMAT and default messages retain their appearance.

Malformed entries, missing templates, reversed ranges and empty decimal ranges stop loading with the error location. This also applies to existing top-list, point-change and ELO-constant lists. Valid older ranges remain supported, including the lower boundary -*; use the canonical * in new configuration. Apply changes with /funnyguilds reload. A complete new set of formatting rules is published only after validation; a failed reload retains the previous set. This does not make the rest of the plugin configuration transactional.

When moving from 4.9.x, copy points-format into the appropriate value-formatting.user/guild maps and ping-format into value-formatting.ping. Replace {POINTS} or {PING} with {VALUE} in templates. There is no automatic migration of the entire 4.x configuration. See Rankings & combat for top-list inheritance.