Commands & permissions

Player commands under /gym — register, rename, unregister, info, list, points, showcase and tp — do not require operator permission. The administrative branches /gym admin, /gym debug, /vendor, /league, /trainer and /brecher_trainers skins require permission level 2.

Only the player who placed a spawner can open its configuration screen. Operators can use privileged tools and administrative commands, but there is no ownership-transfer command.

Command overview

Command	What it does
/gym points	Show your LP balance and league stats
/gym list	List all Gym Controllers you own, including unregistered gyms
/gym info	Show details for a nearby owned gym
/gym register	Validate and register a gym
/gym rename, /gym unregister	Rename or unregister an owned gym
/gym showcase	Show the current Frontier showcase
/gym tp <name>	Prints a reminder to use a Gym Anchor; it does not teleport
/gym admin ..., /gym debug ...	Operator subcommands (level 2)
/league info	Show deployment and tier configuration
/league reload	Reload league.yaml when its live-safe settings change
/league tier <player>	Inspect a player's tier
/league tiers	Summarize the online tier distribution
/trainer spawn <namespace:id>	Spawn an installed native trainer template (world-authority backend only)
/trainer migration report	Report unresolved templates, malformed legacy rosters and loaded legacy-backed trainer entities
/vendor spawn [pos [preset [name]]]	Spawn a League Vendor; a preset requires a position, and a name requires both
/vendor preset <id>, name <name>, info, remove	Operate on the nearest vendor
/vendor list	Show the available vendor presets
/vendor reload	Reload shop.yaml
/vendor addtrade, removetrade, settier, cleartrades, listtrades	Manage vendor trades
/brecher_trainers skins status, reload, refresh <entity>	Trainer skin resolver status, policy reload, and per-entity refresh

Vendor presets and trade offers are configured in config/brecher_trainers/shop.yaml.

Routine checks

• /league info — configuration and deployment identity.
• /trainer migration report — migrated spawner count, malformed legacy rosters, unresolved templates, and remaining legacy-backed entities.
• /gym admin registry stats and /gym admin registry validate — registry health.
• /gym admin showcase prune — remove stale showcase tracking.
• /brecher_trainers skins status — skin provider/cache state.

Ownership and range rules

Player-owned gym commands (/gym register, rename, unregister, info, list, and points) require a player source. The nearby-controller commands (/gym register, /gym rename, /gym unregister and /gym info) select the nearest owned controller in the player's current dimension within 50 blocks; operator status does not silently substitute for ownership on those commands. /gym list returns all non-orphaned Gym Controllers owned by the player, including unregistered gyms; /gym points reads the player's league record and has no range requirement. Use the level-2 /gym admin commands for operator actions. Name-based admin mutations refuse duplicate legacy display names, and mutations that need a controller refuse an unloaded chunk rather than loading it or treating it as destroyed.

/gym admin registry validate is read-only. It reports unloaded/unavailable controllers separately from loaded positions whose controller is missing, cross-store reference errors, and ambiguous display names. Its command result is failure while any category is unresolved, so command blocks and scripts can use the return value as a health gate.

/vendor, /league, /trainer, and /brecher_trainers skins administration requires permission level 2. Nearest-vendor commands use the invoking entity's dimension and a 10-block search. For automation or destructive removal, prefer an explicit selector such as /vendor remove @e[type=brecher_trainers:league_vendor,limit=1,sort=nearest]; successful removal feedback includes the UUID and position. Console callers must supply positions/selectors for commands that otherwise depend on the invoking entity. Vendor names are limited to 128 characters and configured vendors to 256 custom trades.

The Masquerade Visor intentionally suppresses owner and operator block access while held in Creative mode, so visitor behavior can be tested.