Skip to main content

Login callback information (GUALoginResult)

Data Structure

GUALoginResult: Login callback information, inherits from GUABaseResult, contains login information.

ParametersTypeDescription
OpenIDstringPlayer Network SDK User Unique Identifier
TokenstringUser credential
TokenExpirelongToken Expiration Timestamp
For example, 1600844518
FirstLoginintIs first login
Unknown: -1
No: 0
Yes: 1
UserNamestringNickname
GenderintGender
0: Undefined (WeChat and QQ channels always return 0)
1: Male
2: Female
BirthdatestringReturns empty due to compliance requirements that prohibit collecting the player’s date of birth
PictureUrlstringProfile picture URL
Pfstringpf value
Used for Midas payment
Pfkeystringpf key
Used for Midas payment
RealNameAuthboolIs Real-Name Verification Required
ChannelIDintChannel Number
ChannelstringChannel Name
ChannelInfostringThird-party channel login information
ConfirmCodestringVerification Code
ConfirmCodeExpireTime
[MSD only]
longConfirm code expiration time
BindListstringBinding information
JSON Data, array type
LegalDocumentsAcceptedVersion
[Player Network SDK only]
stringLegal Document Version Information
DeleteAccountStatus
[Player Network SDK only]
intAccount deletion status
See DeleteAccountStatus for more info.
DeleteAccountInfostringIf `DeleteAccountInfo' is needed, contact Player Network Assistant
Account deactivation info, JSON data.
For more information, see DeleteAccountInfo.
TransferCode
[Player Network SDK only]
stringVisitor transfer code for special areas
TransferCodeExpire
[Player Network SDK only]
longVisitor transfer code expiration time for special areas

DeleteAccountStatus

caution

For businesses that require DeleteAccountStatus, please contact Player Network Assistant for configuration. Otherwise, DeleteAccountStatus will return -1.

ValueDescriptionNote
0No account deletion performed or account deletion canceledAllow player to enter the game
1Account Deletion Cooling-off PeriodBlock user login and prompt the user to choose whether to cancel account deletion before entering the game
2Account deletion completeDo not allow player to enter the game
3Account deletion in progressDo not allow player to enter the game
4Account deletion failedDo not allow player to enter the game
-1No account deletion status returned from the backendIt is recommended to allow the player to enter the game
-2Account deletion status service network anomalyIt is recommended to allow the player to enter the game
-3DMCS response data format is incorrect (missing return status or err_code field in JSON)It is recommended to allow the player to enter the game
-4Internal error (parameter validation failed or configuration validation does not match internal authorization logic)It is recommended to allow the player to enter the game
-10 or -11Account deletion status service internal errorIt is recommended to allow the player to enter the game
> = 5UndefinedIt is recommended to allow the player to enter the game

Reasons for recommending allowing the player to enter the game:

  • If player login is denied, it will affect all users. It is not recommended to make this a critical path for account deletion.
  • At the same time, the game side also needs to evaluate whether allowing the player to enter when the return value is negative will have any other impact on the game data.