Move from another bot

Take your data with you

Export rosters, results, and configuration bundles from your organisation.

Imports accept structured packs so a cutover does not mean retyping every team.

Leave mention-race registration

Many BGMI servers open registration by letting captains spam a channel: first messages with enough teammate mentions claim the slots. That culture is familiar. Tournabot does **not** ship a mention-race mode and will not — Discord delivery order is not a fair allocator, ping storms are not a roster, and staff cannot audit “I posted first” disputes against a durable seat record.

What replaces it on night one:

1. Staff open the night (`registration_open`). Captains use the **Register** button on the registration panel (or `/scrim-register` / `/event-register`). The same seat path runs for tournaments. 2. Under contention, seats resolve by **server receipt / commit order** inside `claimSeat` — not by message snowflake, wall clock, or who typed faster. Capacity is a unique seat index, not a count. 3. When the lobby fills, the next team lands on the **waitlist** (`event_full_waitlisted`) with a position. Freed seats offer timed holds; captains do not re-spam the channel. 4. Optional **message-format** intake (paid / Message Content intent) still parses a team name plus Discord mentions for the roster. Mentions identify teammates; they do **not** win the race. That path shares the same claim, refusals, and audit as the panel. 5. Staff publish the **slotlist** into the mapped channel so the lobby view is a bot table, not a screenshot of who yelled first.

First-night checklist for a Quo-shaped server: bind the registration channel, post the panel before open, announce the button (not “mention N teammates”), keep the old bot’s race channel read-only or delete its sticky after cutover, and tell captains that full means waitlist — not keep posting. See `docs/domains/01-scrims.md` (Registration) and `docs/domains/18-slot-lifecycle.md` (Race authority).

Switch without a blank night

Plan the cutover: map channels, re-post panels from stored state, retire the old bot’s orphaned messages.

Slash commands and buttons both keep working after cutover — coexistence stays the rule.