Skip to content

Configuration Overview

Frontier’s configuration lives in config/frontier/. Every file uses HOCON format and auto-generates with sensible defaults on first launch. Change anything, reload, done.

config/frontier/
config.conf Queue, match, anti-boost, replay, sounds, arena return
messages.conf All player-facing text (MiniMessage format)
clauses.conf Battle clause definitions
formats.conf Format rules, bans, team preview settings
ladders.conf Ladder definitions, rating algorithms, rank tiers
arenas.conf Arena positions (auto-generated by arena wizard)
seasons/ One .conf per season
example.conf
guis/ GUI layout definitions
hub.conf
ladder_dashboard.conf
leaderboard.conf
team_preview.conf
challenge_invite.conf
rules.conf
rewards.conf

HOCON (Human-Optimized Config Object Notation) is a superset of JSON with a more relaxed syntax. No quotes required around most keys, comments with #, and lists don’t need commas between entries.

# Comments with #
queue {
tickInterval = 20
maxRatingExpansionPerSecond = 10.0
}
# Lists don't need commas
clauses = [
"species_clause"
"sleep_clause"
"evasion_clause"
]

All config files can be reloaded without a server restart:

/ranked reload

This reloads config.conf, messages.conf, clauses.conf, formats.conf, ladders.conf, arenas.conf, all season files, and all GUI definitions. Player data (ratings, stats) is unaffected.

FileDoc PageWhat It Controls
config.confMain ConfigQueue, match, anti-boost, replay, sounds, arena return
formats.confFormatsFormat rules, clauses, bans, team preview
clauses.confClausesClause definitions (Showdown rules, MoLang, validation)
ladders.confLaddersLadder definitions, rating algorithm, rank tiers
arenas.confArenasArena positions and restrictions
seasons/*.confSeasonsSeason dates, ladder bindings, rewards
messages.confMessagesAll player-facing text
guis/*.confGUI LayoutsGUI layout customization