Wiki

FAQ and Troubleshooting

Common setup, sign-in, map generation, and progression issues with direct remedies.

Last updated: 2026-02-27

Key Mechanics

  • OAuth configuration requires client ID, secret, session secret, and matching callback URL.
  • Map generation can gate gameplay until Gemini image is ready.
  • Paused worlds do not progress in background catch-up.
  • Start Over resets world state but preserves shared narrative variants.

What You Control

  • Retry map generation from gate state when image request fails.
  • Use pause/resume intentionally before leaving session.
  • Use catch-up summary to review elapsed progression.

What Remains Autonomous

  • If map gate is locked, play interaction is intentionally blocked until resolved.
  • Background progression depends on pause state and elapsed real time.

Deep Dive

For OAuth redirect errors, confirm Google Authorized Redirect URI exactly matches `/auth/callback` under your deployed base URL.

For local development with no Postgres, unset `DATABASE_URL` to use in-memory fallback.

For deployment, verify DNS/HTTPS before OAuth testing.