Configuration

The plugin is mainly configured through two files:

• arenas.yml — Arena-specific settings (hardcore, timers, player limits, etc.)

• config.yml — Global settings (team limits, names, king health, coins, cooldowns, regen speed, etc.)

You will most likely want to review both files after your first arena setup. Also: be careful when editing arenas.yml after an arena is created, changing the wrong values can break regeneration or spawns.

---

arenas.yml

After creating and finishing an arena, it will appear under:

arenas:
  arena1:
    hardcore: false
    auto-start: 10
    game-timer: 35
    min-players: 1
    max-players: 16

What the settings mean

• hardcore If true, players do not respawn after dying the game is over for them.

• auto-start When min-players is reached, the auto-start countdown begins.

• game-timer How long the match lasts before Defenders win automatically (if the King is not killed).

• min-players Minimum players required to start.

• max-players Maximum players allowed in the arena. If a player joins after this, they will be put into spectator mode.

Do not change these arena-generated values

In addition to the settings above, arenas.yml also stores arena data like:

• spawn locations

• regeneration region bounds (min/max X/Y/Z)

• internal arena setup values

Do NOT manually edit the arena-generated spawn/region values unless you know exactly what you’re doing. Changing them can break the arena regeneration region and cause the map to regenerate incorrectly.

---

config.yml

config.yml contains global settings that affect all arenas.

Teams & balancing

• maxPlayersPerTeam Maximum number of players per team.

• maxTeamDiff Maximum allowed player difference between teams (helps keep teams balanced).

Team display names

You can change how team names appear (placeholders, UI, scoreboards, etc.):

• Display names (safe to change): attackersTeamName, defendersTeamName

Even if you change display names, you must still use Attackers/Defenders internally (for example: setting spawns and in kits.yml team fields).

King settings

• king-health King maximum health. Must be written with one decimal (example: 80.0).

• king-name The name displayed for the King.

Bossbar

• bossbar-enabled Enables/disables the bossbar showing the King’s health.

Coins

• coins-on-win Coins awarded for winning a game.

• coins-on-kill Coins awarded per kill.

Cooldowns & damage

• tntCooldown Bombardier TNT cooldown (seconds).

• wizardAttackSpellCooldown / wizardSupportSpellCooldown Wizard spell cooldowns (seconds).

• tntDamage TNT damage to players. TNT cannot damage the King.

Arena regeneration performance

• arenaBlockRegenPerSecond Controls how many blocks regenerate per second.

Changing arenaBlockRegenPerSecond can affect performance:

• If your server lags while regenerating, lower this value.

• If regeneration feels too slow, you can increase it (example: 5000) — but it may cause lag.

---

Example config.yml

# MAX PLAYERS IN TEAM
maxPlayersPerTeam: 8
maxTeamDiff: 2

# CHANGE TEAM NAMES (DISPLAY ONLY)
attackersTeamName: Attackers
defendersTeamName: Defenders

attackersNametagPrefix: "&c"
defendersNametagPrefix: "&b"

# GLOBAL BOSSBAR
bossbar-enabled: true

# COINS REWARDS
coins-on-win: 3
coins-on-kill: 1

# KING SETTINGS

# NOTE: Should be with one decimal (example: 80.0)
king-health: 30.0
king-name: Marcus III

# COOLDOWNS (SECONDS)
tntCooldown: 30
wizardAttackSpellCooldown: 45
wizardSupportSpellCooldown: 60

# TNT DAMAGE TO PLAYERS (TNT cannot damage King)
tntDamage: 7.0

# 7.0 damage = 2 hearts

# MAP REGEN PERFORMANCE

# If your server is lagging while regenerating, lower this number.

# If regeneration is too slow, try increasing to 5000 (may cause lag).
arenaBlockRegenPerSecond: 3000