Permissions

Frontier uses six permission nodes. Most servers only need the two defaults — player commands are open to everyone, admin commands are locked to ops.

Permission Nodes

Permission	Description	Default
frontier.user	All player commands: queue, stats, history, leaderboard, challenges, spectating, surrender.	All players (level 0)
frontier.admin	All admin commands: reload, rating management, match management, bans, arena builder.	Op level 2
frontier.bypass.queue	Skip queue cooldowns. Useful for staff testing.	Not granted by default
frontier.bypass.validation	Skip team validation when joining a queue. Lets a player queue with a team that would normally fail format checks.	Not granted by default
frontier.tournament	All tournament player commands: menu, join, leave, bracket, spectate, camera.	All players (level 0)
frontier.tournament.admin	All tournament admin commands: forcestart, pause, disqualify, addnpc, autofill, etc.	Op level 2

How They Work

frontier.user

Granted to every player by default. Covers everything a normal player needs:

• Opening the hub GUI (/ranked)
• Queuing, viewing stats, checking leaderboards
• Sending and receiving challenges
• Spectating matches
• Surrendering

Revoking this permission locks a player out of all ranked features.

frontier.admin

Restricted to ops (level 2+) by default. Gives access to:

• Hot-reloading configs (/ranked reload)
• Setting and resetting player ratings
• Force-ending matches
• Banning and unbanning players
• The arena builder wizard

Caution

frontier.admin doesn’t inherit frontier.user. If an admin account somehow lacks frontier.user, they can manage the system but can’t play ranked matches themselves. In practice this rarely matters since frontier.user is granted to everyone by default.

frontier.bypass.queue

Not granted to anyone by default. When assigned, the player skips the cooldown applied after declining a found match (declineQueueCooldownSeconds). Handy for staff who need to test queue behavior repeatedly.

frontier.bypass.validation

Not granted to anyone by default. Skips team validation entirely when joining a queue — the player’s team won’t be checked against format clauses, species bans, move bans, or legality rules.

Caution

Only grant frontier.bypass.validation for testing or debugging. In normal play, it defeats the purpose of format rules.

frontier.tournament

Granted to every player by default. Covers everything a player needs for tournaments:

• Opening the tournament hub GUI
• Joining and leaving tournaments
• Viewing brackets
• Spectating tournament matches
• Using the cinematic camera
• Opting out of auto-spectating during finals

frontier.tournament.admin

Restricted to ops (level 2+) by default. Gives access to:

• Force-starting, pausing, and unpausing tournaments
• Opening/closing registration
• Restarting tournaments from specific rounds
• Disqualifying players
• Adding NPC participants and autofilling brackets
• Testing commands (fake players)

LuckPerms Examples

Grant admin access to a staff group:

/lp group staff permission set frontier.admin true

Let a specific player bypass queue cooldowns:

/lp user Steve permission set frontier.bypass.queue true

Revoke ranked access from a player (alternative to in-game bans):

/lp user Steve permission set frontier.user false