Small Account Updates Can Prevent Large Event Conflicts
Contact information, in-game identity and roster history should continue to describe the same competitor.
Review the profile before important registration windows, not after a mismatch blocks check-in. Update only the fields that genuinely changed and preserve the records that connect previous events to the account. A duplicate profile is rarely a clean solution.
Check the fields an organiser may need to validate
Confirm the display name, region, contact method and in-game identity. If the platform separates a public nickname from a legal or verified name, understand which one appears to teammates and which one is used during eligibility review. Never place sensitive identity numbers in a public biography.
Update a lost phone number or inaccessible email through the supported verification path. Do not wait until an OTP is required at check-in. After the change, test sign-in and review any security notification sent to the previous contact channel.
- Current recovery contact
- Exact competition identity
- Correct region and profile visibility
- No unnecessary private information
Keep completed events connected to the original account
Past registrations, results and conduct notices can be useful for recognition and support. Closing an account or creating a replacement can separate those records. If a displayed result appears wrong, ask for a correction using the event reference rather than rebuilding the profile.
Team transfers and name changes should be recorded without rewriting the historical roster. A current team field describes the present; an event result should continue to show who competed at that time.
Review devices after travel, repair or shared use
Sign out sessions you do not recognise and remove saved access from a device no longer under your control. If the phone was repaired or restored, reinstall from the official source and confirm security settings before opening event records.
Contact support when a profile change cannot be explained. Include the time, affected field and any security message, but never send the password or OTP. A focused account case helps protect both access and the integrity of the competitive record.
Questions worth settling early
No. Update the current profile where needed and preserve historical event records.
Use the event reference and result evidence to request a correction instead of creating another profile.
Review them after shared-device use, travel, repair, unexpected alerts or any suspected account change.
