Race (Competitive multiplayer race builder)

All commands are under /lasers race. Verb-first convention: <verb> <name> [args]. Build names are always after the verb, never at the root.

Admin-only (lasers.admin) except list, tp <name> and results <name> [run] [page], which are open to any player.

For the workflow and concepts, see Competitive race builder.

Admin commands

Command	Permission	Description
/lasers race create <name>	lasers.admin	Create an empty DRAFT build. The name cannot collide with reserved literal subcommands.
/lasers race edit <name>	lasers.admin	Open the builder menu (configure levels, players per copy, copies count, get the wand). Refused while a run is RUNNING.
/lasers race addLevel <name> <levelName>	lasers.admin	Append a level (downloaded from the website catalog, autocompleted).
/lasers race generate <name>	lasers.admin	Validate the footprint and build copy #1 + the spawn. Transitions DRAFT → GENERATING → GENERATED.
/lasers race continue <name>	lasers.admin	Replicate the validated copy #1 to copies 2..N. Transitions GENERATED → CONTINUING → COMPLETE.
/lasers race getExitTeleporterItem <name>	lasers.admin	Re-dispense the exit-teleporter wand (useful if the original item was lost). Requires the test copy to be placed (GENERATED or COMPLETE).
/lasers race start <name>	lasers.admin	Open a new run, promote every PENDING_START SAS-locked group to RUNNING, teleport every member to level 1, start the chronos and the per-player sidebar. Cancels any previously RUNNING run on this build.
/lasers race stop <name>	lasers.admin	Cancel the current run (and free any group still waiting in a SAS airlock), send every player back to the spawn anchor, and reopen the airlocks. The build stays GENERATED / COMPLETE, ready for another start; the run is preserved in the history as CANCELLED.
/lasers race delete <name>	lasers.admin	Delete a clean DRAFT immediately. On any other state, send a clickable chat hint pre-filling delete <name> confirm.
/lasers race delete <name> confirm	lasers.admin	Teleport occupants to the origin, wipe the world structure, delete the configuration and the entire run history. confirm is not in tab-completion.
/lasers race reset <name>	lasers.admin	Refuse on a clean DRAFT (nothing to reset). On any other state, send a clickable chat hint pre-filling reset <name> confirm.
/lasers race reset <name> confirm	lasers.admin	Teleport occupants to the spawn anchor, wipe the world structure, send the build back to DRAFT. Preserves the level list, players per copy, copies count and the run history. confirm is not in tab-completion.

Player-facing commands

Command	Permission	Description
/lasers race list	none	List available events. Players see GENERATED / COMPLETE builds only, with a "running now" flag. Admins see every state verbatim (DRAFT / GENERATING / GENERATED / CONTINUING / COMPLETE / GENERATION_FAILED / CONTINUATION_FAILED) plus readiness flags.
/lasers race tp <name>	none	Dual-mode: if the caller is a member of a RUNNING group on this build, resume them at their current level; otherwise teleport to the spawn anchor. Refused on DRAFT / GENERATING / CONTINUING and on builds with undefined exit teleporters.
/lasers race results <name> [run] [page]	none	Show recorded times. Defaults to the latest run; [run] selects a past run by index; [page] paginates 10 rows per page. History preserved across start calls.

Notes

• /lasers is interchangeable with /le and /lasersenigma (registered command aliases) — e.g. /le race list works identically.
• Level-name tab-completion for /lasers race addLevel <name> <levelName> is fetched from the Lasers-Enigma website asynchronously, so the list is empty the first time you trigger it. Delete the space before <levelName> then type it again to refresh the suggestions.
• /lasers race generate <name> pastes the whole build from the admin's position with no undo, and its footprint check only detects registered LasersEnigma Areas and other race builds — not vanilla builds or plain blocks. Stand far from any existing structure before running it.
• There is no in-world button (start or reset) — both are commands.
• Exit teleporters are defined with the wand item-tool, not by a command. The wand itself can be (re-)obtained from the builder menu or via /lasers race getExitTeleporterItem <name> if the original item was lost. Each placed exit teleporter is shown in the world as a spinning gold triangle, and triggers the level transition when a player steps on it.
• The confirm token on delete and reset is intentionally not suggested in tab-completion. It is surfaced only via chat-clickable hints, so destructive operations stay deliberate while the autocompletion tree stays clean.
• A run group's copy stays reserved for the whole run. A player who leaves automatically returns to their current level on next login / respawn / tp (resume mechanic).
• Editing a generated build opens a chat-clickable yes/no popup; the menu stays in pending state until answered. The edit wipes the world structure and regenerates — all exit teleporters must be redefined afterwards. Refused while a run is RUNNING.