Registration and teams

Registration model

Registration combines time window, eligibility, supported modes and team limits. Public visibility aids discovery but is not itself a registration switch.

1. Set start/end timestamps and publish the timezone.
2. Choose solo, team or both paths.
3. Configure roster limits, team cap and whether captains play.
4. Set linked-account, platform, country, Discord and domain requirements.
5. Decide whether registered and qualified teams are public.
6. Test an eligible and intentionally ineligible account.

Linked identities

Accounts originate from Discord authentication and can link BeatLeader, ScoreSaber and Twitch. A requirement checks the link; it does not expose third-party credentials. Platform IDs also resolve TA participants against a selected BeatKhana match.

Teams and captains

An organiser can create a team from a captain's Discord ID or BeatKhana GUID, with optional name and shareable ID, then manage members. If Allow team modification is off, roster changes need staff. If on, changes still satisfy window and limits. Publish roster-lock dates.

Qualification and privacy

Registered and qualified are distinct states. Qualification may come from TA standings, a cutoff, an algorithm or an organiser decision. Public toggles only affect presentation. Organisers do not receive player email addresses; domain checks expose only the suffix needed for eligibility.

Changes after opening

Treat eligibility and team-limit edits as rule changes: announce them, keep a decision log, revalidate entries and give affected teams a fair correction window.