Skip to main content

Login Callback Information (AuthResult)

Data Structure

caution

Business needs to use FirstLogin field to determine if new user.Then business must also remind Player Network SDK to clear relevant data during file clearing.

INTLAuthResult: Inherits from INTLBaseResult and contains login information.

NameTypeExplanation
OpenIDStringPlayer Network SDK Unique User Identification
Defaults to 64-bit unsigned integer string, supports 32-bit as well
TokenStringPlayer Network SDK generated 40 byte user token
TokenExpirelongToken expiration timestamp
For example, 1600844518
FirstLoginintIs first login
Unknown: -1
No: 0
Yes: 1
UserNamestringNickname
GenderintGender
0: Undefined
1: Male
2: Female
BirthdateStringReturns empty due to compliance not allowing collection of player's birth date
PictureUrlStringAvatar URL
Pfstringpf value
Used for Midas payment
Pfkeystringpf key
Used for Midas payment
NeedRealNameAuthboolRequires real name authentication
ChannelIDintChannel Number
ChannelStringChannel Name
See INTLChannel for details
ChannelInfostringThird-party channel login information
JSON Data, values differ per channel
BindListstringBinding information
JSON Data, array type
LegalDocumentsAcceptedVersionstringLegal documentation version info
DeleteAccountStatusintAccount deletion status
See DeleteAccountStatus for more info.
DeleteAccountInfoStringIf `DeleteAccountInfo' is needed, contact Player Network Assistant
Account deactivation info, JSON data.
See DeleteAccountInfo for more.
TransferCodestringVisitor transfer code for special areas
TransferCodeExpireTimelongVisitor transfer code expiration time for special areas
DeleteLIAccountStatusintLEVEL INFINITE PASS account cancellation status
See DeleteLIAccountStatus for more.
EmailstringEmail address
HealthScoreintCurrent account security level; the higher the value, the greater the security.
HealthScoreRetintReturn code, 0 indicates normal.

The ExtraJson in INTLAuthResult contains a JSON string with the user's protocol version and compliance status queried from the backend.

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
oneAccount Deletion Cooling-off PeriodBlock player login, prompt the player to decide whether to cancel the account deletion and enter 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 backendRecommend allowing player to enter the game
-2Account deletion status service network anomalyRecommend allowing player to enter the game
-3DMCS response data format is incorrect (missing return status or err_code fields in JSON)Recommend allowing player to enter the game
-4Internal error (incorrect parameter verification or configuration does not match internal authorization logic)Recommend allowing player to enter the game
-10 or -11Account deletion status service internal errorRecommend allowing player to enter the game
> = 5UndefinedRecommend allowing player to enter the game
note

游戏侧需评估返回值为负数时,如果允许玩家进入是否会对游戏数据有其他影响。

If players are not allowed to enter the game with negative return values, this may affect other players, so it is not recommended to treat this as a key path for account deletion.

DeleteAccountInfo

JSON data:

{
"ret": 0, // int, return code, 0 means normal.
"err_code": -10, // int, Player Network SDK error code, not needed by the game
"msg": "", // Error message, empty if the request was successful
"status": 0, // int, 0: no record or account deletion canceled; 1: cooldown period; 2: account delete successful; 3: account deletion in progress; 4: account deletion failed
"created_at": 12345678, // int64, timestamp when account deletion request was created (timestamp is 0 when status is 0)
"target_destroy_at": 12345678, // timestamp for executing account deletion (timestamp is 0 when status is 0).
"destroy_at": 12345679 // int64, timestamp when account was actually deleted (timestamp is 0 when the status is not 2)
}

DeleteLIAccountStatus

ValueExplanation
-1Account deletion status query failed or backend did not return status
0No account cancellation record or delete request has been withdrawn
oneAccount cancellation requested
2Account cancellation successful
3Canceling account
4Account cancellation failed