Player
Player identity, profile data and platform authorization.
Authorization Support
Check this before showing a login button. Authorization support depends on the host platform.
Use the PlaygamaBridge Is Player Authorization Supported condition before showing a login button.
Use the PlaygamaBridge Is Player Authorization Supported condition before showing a login button.
Is the Player Currently Authorized
Use this to decide whether protected features are available right now, such as account-based saves, personalized content, or social actions.
Use the PlaygamaBridge Is Player Authorized condition to decide whether protected features are available right now.
Use the PlaygamaBridge Is Player Authorized condition to decide whether protected features are available right now.
Is Guest
Returns true when the player has no persistent platform identity: they are not authorized, or the platform runs them as a guest account. Use it to decide whether to show a login prompt or to warn that progress may not sync across devices.
Player ID
Returns the player's platform ID when available. Use it for display, analytics correlation, or backend verification.
Player Name
Returns the display name provided by the platform. Use it for profile UI, leaderboards, friend lists, or social prompts.
Returns null when no name is available; otherwise returns a string.
Player Avatar
Returns available player avatar URLs. Use the largest suitable image for profile UI, lobbies, or leaderboard rows.
Number of Player Avatars:
Get Avatar by Index:
Number of Player Avatars:
Get Avatar by Index:
Possible values: an array of avatar URLs sorted by increasing resolution, or an empty array.
Player Extra Fields
Returns platform-specific authorization data. Properties vary by platform.
Use this data on your backend to verify authorization. Playgama API verification currently supports only playgama, msn, and microsoft_store.
Player Authorization
Start the platform authorization flow. Call this from a direct player action, such as tapping a login button, before enabling account-only features.
In the event sheet:
On a trigger (e.g. Button → On clicked), add the Authorize Player action.
Add the On Authorize Player Completed condition. Inside it, check Is Last Action Completed Successfully for the success branch and its inverted form for the error branch.
In the events sheet:
On a trigger (e.g. Button is clicked), add the Authorize Player action.
Add the On Authorize Player Completed condition. Inside it, check Is Last Action Completed Successfully for the success branch and its inverted form for the error branch.
Last updated