FAQs
Custom accounts are only available for games released in 2023 or earlier. New games must integrate LI PASS. For more details, see LEVEL INFINITE PASS.
For custom accounts, the verification code can be used to register, log in, change the password, and perform other functions. Because each verification code is valid for one use only, if a player clicks multiple times, they might receive a callback message that the older verification code is invalid. During player login, the game should set a function to prevent re-entry and wait for a callback to be received, before allowing the the player to click to log in again.
When using the request verification code to create a custom account, the game needs to prevent re-entry or set a countdown to avoid multiple requests for the verification code from the same player, causing waste of resources and other login errors.
Symbols supported by password verification include uppercase and lowercase letters, numbers, and some special symbols (including !@#$%^&*()+=\-_/?<>,.:;|), with a length of 8~20 bits.
What are the rules for a user name?
The user name should start with a lower case letter and consist of lower case letters, underscores, and numbers (a-z_0~9). The length of the user name should be between 6 to 16 letters.
What are the rules for a password?
The password should contain upper case letters, lower case letters, numbers, and !@#$%^&*()+=\-_/?<>,.:;|. The length of the password should be between 8 to 20 letters.
Failed to register a custom account because email address contains a special character.
Only SDK V1.9 and later versions support certain special characters.
Can a custom account be used in both the production environment and testing environment?
No, accounts are only valid for their specific environments.
When Player Network is switched to the production environment, can I still log in to custom accounts from the testing environment?
You can still log in to the testing environment. This does not impact the production environment.
After I log in with a custom account, why was I not logged in automatically?
Before logging in with a custom account, call SetAccountInfo and check if AutoLogin has been called previously.
What is the validity period of login authentication?
By default, authentication expires after 30 days. Contact the Player Network representative to configure the validity period.
Can the username of a custom account be blank?
Yes, the username of a custom account can be blank.
Why does QueryIsReceiveEmail return 0 for a custom account?
You need to configure a welcome email at the backend, then pass 1 for is_receive_email during registration. Otherwise, the return value will be 0.