Prepare for Release

During development the SDK runs on your developer token, and AI usage is billed to your account. A packaged build should instead use player authentication, so each player signs in with their own PlayKit account and pays for their own AI usage. This page covers the switch.

Developer Token

No action is required to remove the developer token. It is stored in the editor-per-project configuration (EditorPerProjectUserSettings.ini, under the [PlayKit] section), which is not part of a packaged build. Every packaged build uses the device authentication flow (UPlayKitDeviceAuthFlow) automatically.

To clear the stored token entirely, open Edit > Project Settings > Plugins > PlayKit SDK and empty the Developer Token field. This is optional, since the token never ships in a packaged build either way.

To rehearse the player login flow inside the editor, enable Ignore Developer Token under Edit > Project Settings > Plugins > PlayKit SDK > Advanced.

Production Settings

In Edit > Project Settings > Plugins > PlayKit SDK:

• Game ID is set to the game being shipped.
• Enable Debug Logging (under Advanced) is turned off for release builds.
• Default AI models are set correctly.

Branding

Configure the name, description, logo, and key art shown on the player sign-in and authorization screen. This is set on the PlayKit platform, not in Unreal — see Setting Up Branding.

Release Checklist

• Branding (name, logo, key art) is configured — see Setting Up Branding.
• The game presents the device login flow (UPlayKitDeviceAuthFlow) — see the Login Example in the plugin's example content.
• A packaged build lets a real player sign in, and AI calls are billed to the player's account.
• Enable Debug Logging is disabled.

Next Steps

• Core Concepts — authentication and SDK architecture
• Getting Started — installation and configuration