Registration and teams

The short version

A team is created first, filled with players, and then registered. Registration is a deliberate final step: it tells the organiser that the roster is ready and may lock further edits. Qualification is a later, separate state.

The usual captain workflow is:

1. Create the team and choose its public name, image, description and URL.
2. Invite every player by Discord ID. Players must accept their invitations.
3. Check whether the captain should also play. On a non-solo team, captains are not automatically players and must join the roster too.
4. Complete any required registration questions.
5. Check the roster size and eligibility messages, then register the team before the deadline.

Registration windows and eligibility

The tournament controls when registration opens and closes. A team can only register during that window unless an authorised organiser intervenes. Each player may also need to meet tournament requirements such as:

• a linked BeatLeader, ScoreSaber or Twitch account;
• an allowed platform or country;
• membership in a required Discord server;
• a verified email domain; or
• acceptance of tournament-specific questions and declarations.

Public tournament visibility only makes a tournament discoverable. It does not open registration by itself.

Captains and players

The captain manages the team but does not necessarily occupy a player slot.

• For a solo registration, the captain is normally the only player.
• For a team registration, the player list is the accepted roster. If the captain intends to compete, they must also appear in that list when captain play is allowed.
• When captain play is disabled, the captain remains an administrative contact and does not count toward minimum or maximum team size.

Owners and developers can transfer captaincy when operational intervention is needed. A new captain cannot already belong to another team in the same tournament. Changing the captain does not silently move unrelated staff permissions.

Invitations

Inviting someone does not immediately add them to the roster. The invitation remains pending until that user accepts or declines it. A captain can cancel a pending invitation while team changes are allowed.

An invitee may be prevented from accepting when they are already registered with another team, do not meet a tournament requirement, the team is registered or qualified, or roster modification has been disabled. The team page shows the current roster and pending invitations separately so captains can see which step is incomplete.

Editing and roster locks

The Allow team modification setting determines whether captains can change team details, images, invitations and players. Even when it is enabled, registered and qualified teams are locked for captains.

When the registration window is still open, a registered team can normally unregister, make its changes, and register again. Unregistering removes its active tournament registration state; it is not the same as deleting the team. Qualified teams may require organiser assistance.

If editing controls are absent, read the lock message on the team page. It explains whether the tournament setting, registration state or qualification state is preventing changes.

Registered and qualified are different

Registered means the roster has been submitted to the tournament. Qualified means the team has advanced or has been accepted into the competitive field. Qualification may come from standings, a cutoff, an algorithm or an organiser decision.

The public visibility options for registered and qualified teams only affect presentation. They do not grant eligibility or bypass registration rules.

Removing players and deleting teams

Removing a player removes their roster link and their participant permissions for that tournament. It does not remove unrelated organiser or staff roles. Deleting a team removes the roster, invitations, registration state and the roster-specific tournament permissions of its participants.

Deletion is permanent. Captains should unregister when they only need to correct a roster, and use deletion only when the team itself should no longer exist.

Guidance for organisers

Before opening registration:

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

Treat later eligibility or team-limit edits as rule changes. Announce them, keep a decision log, revalidate affected entries and provide a fair correction window.