Treat Sign-In as Part of Match Preparation
A working account should be confirmed before the event check-in window, not for the first time when the lobby is already open.
Most access problems can be narrowed down by checking the account identifier, device time, network stability and current app version. Recovery should follow the official path, because sharing a password or OTP creates a larger problem than a delayed login.
Confirm the account and environment before requesting another code
Make sure the email or mobile number belongs to the intended player profile. Remove accidental spaces and check whether the device clock is automatic. A clock that is far from the correct time can affect short-lived codes and secure session checks.
Switching repeatedly between networks or requesting many codes can make the sequence harder to follow. Use a stable connection, wait for the latest request and enter only the most recent OTP. Never reuse a code sent for a different action.
- Check the registered identifier carefully.
- Use automatic date and time on the device.
- Install only the current official app build.
- Enter the newest OTP and keep it private.
Use account recovery without handing control to someone else
Open recovery from the recognised IX6 entry point and complete the requested verification yourself. Do not accept remote-control help from a stranger or send a screen recording that reveals a code. If the registered contact is no longer available, use the account-support process rather than creating a conflicting duplicate profile.
After access returns, review active sessions and update the password to a unique phrase. Confirm that the profile name and event registrations still belong to you before joining a lobby.
Resolve account issues while there is still time to document them
Sign in early enough to confirm check-in, roster and app permissions. If access fails near a deadline, capture the error and time before changing settings. That evidence may help support determine whether the issue was local, account-related or platform-wide.
Event rules decide how late arrival is handled. A support case does not automatically reserve a place or pause a bracket, so competitors should understand the check-in policy before match day.
Questions worth settling early
Use only the newest code. Earlier codes may expire as soon as a later request is created.
No. Do not share a password or one-time code with support, teammates or anyone contacting you through an unofficial channel.
Not automatically. Check-in and late-arrival treatment follow the event rules.
