AuthResult
Data structure
If the game uses the FirstLogin
field to determine whether the player is a new user, when clearing data, the game needs to inform Player Network SDK to clear the relevant data.
FINTLAuthResult: Inherits from FINTLBaseResult, include login information.
Name | Type | Description |
---|---|---|
OpenID | FString | Player Network SDK unique user ID |
Token | FString | User token generated by Player Network SDK |
TokenExpire | int64 | Token expiration timestamp For example, 1600844518 |
FirstLogin | int32 | Whether this is the first login -1: Unknown 0: No 1: Yes |
UserName | FString | User defined nickname |
Gender | int32 | Gender 0: Undefined 1: Male 2: Female |
Birthdate | FString | Returns empty, collection of player birthdate is not allowed according to compliance requirements |
PictureUrl | FString | User avatar URL |
Pf | FString | pf value For Midas payment |
Pfkey | FString | pf key For Midas payment |
NeedRealNameAuth | bool | Whether real-name verification is required |
ChannelID | int32 | Channel ID |
ChannelName | EINTLLoginChannel | Channel name |
ChannelInfo | FString | Third-party channel login information JSON data, each Channel has its own value |
BindList | FString | Linking information JSON data in array type |
LegalDocumentsAcceptedVersion | FString | The accepted version of legal documents |
DeleteAccountStatus | int32 | Account deletion status For more information, see DeleteAccountStatus. |
DeleteAccountInfo | String | Reach out to the Player Network representative if DeleteAccountInfo is requiredDelete account information, JSON data. For more information, see DeleteAccountInfo. |
TransferCode | FString | Transfer code |
TransferCodeExpireTime | int32 | Expiration time for transfer code |
DeleteLIAccountStatus | int | LEVEL INFINITE PASS account deletion status For more information, see DeleteLIAccountStatus. |
string | Email address |
The ExtraJson in FINTLAuthResult
contains the JSON strings for the protocol version and compliance result of the player queried from the backend.
DeleteAccountStatus
Reach out to the Player Network representative to configure DeleteAccountStatus
, otherwise DeleteAccountStatus
returns -1.
Value | Description | Remark |
---|---|---|
0 | No account deletion or account deletion has been canceled | Allow player to enter the game |
1 | Account deletion cooling-off period | Stop player login, prompt player whether to cancel account deletion and enter the game |
2 | Account deletion completed | Stop player from entering the game |
3 | Account deletion in progress | Stop player from entering the game |
4 | Account deletion failed | Stop player from entering the game |
-1 | Status not returned from backend | Recommend allowing player to enter the game |
-2 | Network unstable for the account deletion status service | Recommend allowing player to enter the game |
-3 | DMCS response data format is wrong (return status or err_code fields missing in JSON) | Recommend allowing player to enter the game |
-4 | Internal error (parameter verification is incorrect or configuration verification is not equal to internal authorization logic) | Recommend allowing player to enter the game |
-10 or -11 | Internal error in the account deletion status service | Recommend allowing player to enter the game |
>= 5 | Undefined | Recommend allowing player to enter the game |
Games should review the consequences of allowing players to enter the game when the return value is negative, and if the game data may be impacted.
Stopping players from entering the game while the return value is negative may affect other players, and is therefore not recommended as an essential step in account deletion.
DeleteAccountInfo
JSON data:
{
"ret": 0, // int, return code, 0 indicates normal
"err_code": -10, // int, error code for INTL, games no need to pay attention
"msg": "", // error message, empty when the request is successful
"status": 0, // int, 0: no record or account deletion is cancelled; 1: cooling-off period; 2: account deleted successfully; 3: deleting account; 4: account deletion failed
"created_at": 12345678, // int64, timestamp when the account deletion request is created (when status is 0, timestamp is 0)
"target_destroy_at": 12345678, // timestamp to execute the account deletion (when status is 0, timestamp is 0)
"destroyed_at": 12345679 // int64, timestamp when the account is actually deleted (when status is not 2, timestamp is 0)
}
DeleteLIAccountStatus
Value | Description |
---|---|
-1 | Account deletion query failed or status not returned from backend |
0 | No account deletion records or deletion has been withdrawn |
1 | Account deletion requested |
2 | Account deletion succeeded |
3 | Account deletion in progress | |
4 | Failed to delete account |