Build the Profile You Will Use on Match Day
Accurate registration makes check-in, roster validation and later result records easier for both competitors and organisers.
Use details you can maintain and verify. The display name, in-game identity, contact method and region should describe the same participant. Creating extra profiles to work around an error can split event history and complicate eligibility checks.
Enter details that can survive an event review
Choose the correct region and provide a contact method you control. Match the in-game identity exactly where the event requires it, including meaningful numbers or symbols. A nickname used only in team chat may not be enough to connect the profile to a match record.
Read age and residency conditions before submitting. Where identity verification is required, the profile should not be built around borrowed details. A mismatch discovered after advancement can affect the player and the wider roster.
- Use a contact method you can access securely.
- Record the exact in-game identity used for competition.
- Confirm age, region and device conditions.
- Avoid duplicate profiles for the same participant.
Finish security setup before joining a team roster
Create a unique password and enable any available verification control. Save recovery information in a private place rather than a shared team document. Captains may need a player ID, but they do not need the password that controls the account.
Review app permissions and notification settings after the first sign-in. Security alerts should remain visible, while nonessential notifications can be silenced during competition so they do not cover controls.
A profile is complete only when the event-specific fields are ready
Different events can request a roster role, game account, device class or team invitation. Complete those fields only after reading the current brief. A general account can exist without making the player eligible for every competition.
Before the registration window closes, open the roster from the player side and confirm that the team name, role and event are correct. Keep the confirmation until the event is finished and its results are published.
Questions worth settling early
A participant should use one accurate profile unless support directs otherwise. Duplicate profiles can divide event history and create verification conflicts.
No. Each event can have separate age, region, roster, device and capacity conditions.
No. Share only the player or roster information required for the event, never account credentials.
