Getting started with PlayableForge

Everything you need to go from an existing Unity project to a network-ready playable in about ten minutes.

Requirements

• Unity 2021.3 LTS or newer
• A PlayableForge account (free during beta)
• Windows or macOS editor

1. Install the package

In Unity, open Window → Package Manager → + → Add package from git URL and paste the URL from your dashboard. The package adds a PlayableForge entry to the Window menu.

2. Sign in

Open Window → PlayableForge and sign in with your account. Exports are tied to your dashboard so the team can see history and downloads.

3. Mark the playable scene

Select the scene to export. Add the PlayableEntry component to the object that starts gameplay and the PlayableCTA component to the button that should send users to the store. Everything not reachable from that scene is excluded from the build.

4. Set the end-card

Fill in the store URLs (iOS and Android), the CTA label, and the moment the end-card should appear (on win, on lose, or after a timer). Networks that draw their own CTA will override yours automatically.

5. Export

Tick the networks you need and press Export. The inspector shows the size budget for each selected network and turns red if the build exceeds it. Downloads appear in the dashboard under Builds.

Troubleshooting

"Build exceeds size budget"

Open the Size report tab. It lists every asset by compressed size. Audio and uncompressed textures are the usual culprits; drop audio to 22 kHz mono and let the exporter re-encode textures.

"Unsupported API"

The playable runtime does not include every Unity subsystem. The error names the API; usually it is a networking or file-system call that has no meaning inside an ad and can be wrapped in #if !PLAYABLEFORGE.

Blank screen in the network's preview tool

Most often the ad is starting before the network signals it is visible. Make sure gameplay begins from PlayableEntry and not from Awake() or Start() on another object.