Skip to main content
LiricTNT registers all of its commands through the Paper Brigadier API, which means every argument offers live tab-completion as you type. Template names, active instance names, and game type suggestions all auto-populate in the command bar — you never have to remember exact names from memory.

/tnt Commands

All /tnt sub-commands require the tnt.admin permission node by default. Individual sub-commands carry their own child permissions (tnt.admin.setup, tnt.admin.arena, tnt.admin.start, tnt.admin.stop) so you can grant granular access if needed.
The <instance> arguments in /tnt detener and /tnt espectar tab-complete with the names of currently running arena instances, not templates. An instance name looks like Endercon_1715000000 — a timestamped clone of the original template.

Arena Lifecycle Example

/gm Command

The /gm command is a Folia-safe gamemode switcher designed for use during events. It works across threaded regions without scheduling issues. Permission: tnt.gamemode
The <mode> argument accepts both numeric shortcuts and full names: If you omit [player], the command applies to yourself. Provide a player name to change someone else’s gamemode. The command also registers the /gamemode alias.

/extras Commands

The /extras command group gives operators real-time control over match dynamics. All sub-commands require the tnt.admin.extras permission.

Applying Potion Effects

Apply a potion effect to every currently alive player in the active arena:
<level> accepts values from 1 to 10. Higher levels produce extreme effects — use with caution.

Triggering Events

Trigger a special event in the active arena:
See the Special Events page for a full breakdown of each event’s behavior.
You can chain /extras efecto and /extras evento during the same match. For example, trigger the Tornado event and then immediately apply Levitation 3 to keep airborne players in danger longer.