This page covers platform problems. For bugs inside your game (broken mechanics, visual glitches), see Debugging your game — that’s a prompting workflow, not a support ticket.

​
A generation seems stuck

Builds legitimately take minutes (why) — the progress feed in chat shows the AI working. If there’s been no new activity for a long time:
  1. Refresh the page — the Studio re-syncs with the build’s real state, which often resolves a stale-looking UI.
  2. If it’s genuinely wedged, hit Stop (cancel) — you’re only charged for work actually done — and resend the prompt.
  3. If the game itself stays locked in “generating” even after cancel + refresh, contact support with the game name; the team can reset it.

​
”Waiting for your input” — the build paused

Not stuck: the AI asked you a question or is waiting for plan approval. Open the game’s chat and answer — the build continues from where it paused.

​
Game won’t load / “Restoring from archive”

  • “Restoring from archive” — games idle for a long time get moved to cold storage; the first open pulls them back. This takes a moment and is fully automatic — wait for it to finish and the game loads normally.
  • Preview won’t load at all — hard-refresh (Cmd/Ctrl+Shift+R), check for browser extensions blocking WASM/WebGL, and try another browser. Godot web builds need WebGL: very old GPUs/drivers or disabled hardware acceleration can block them.

​
Build errors over the preview

A red error banner over the preview means the game hit a runtime error. Use its Fix button — it sends the full error log to the AI, which is exactly the evidence it needs. Repeated crashes right after a build often mean the last change was bad: reverting one version is a clean way out.

​
”It charged me but nothing happened”

Check the Usage page and expand the charge:
  • Millions of tokens processed → the AI really worked; the result just missed. That’s a prompting or debugging problem — and the work done is usually recoverable with a follow-up.
  • A charge on a session that visibly produced nothing (engine crash, no output, game unchanged) → that’s on us. Write in with the game and time; the team audits session transcripts and adjusts credits for platform failures. See Failed & cancelled generations.

​
Can’t start a run

  • “Top up to start your next run” — your balance is at/below zero. See Negative balance.
  • A small minimum balance (15 credits) is required to start any run. A single day’s free allowance clears it, so this should only ever bite an overdrawn account.

​
Sign-in and account issues

  • Signed up with Google/Discord and asked for a password? Set one in Settings → Account & Security; your OAuth sign-in keeps working alongside it.
  • Push notifications not arriving → browser permission, see Notifications.
Still stuck? Getting help — include the game name, what you did, and when.