Tutorial Games
The examples/ folder ships six finished Godot 4 games already wired to Quest Data. Each one is a real, playable demo — not a snippet — with the SDK calls embedded in the actual gameplay code.
Use these tutorials to learn integration patterns by reading working code instead of stitching together hypothetical examples.
Pick the demo that matches your game
Section titled “Pick the demo that matches your game”| Demo | What it teaches | Best for |
|---|---|---|
| Dodge the Creeps | Full SDK round-trip — events, progression, leaderboard, achievements, cloud save, remote config, error tracking | Your first integration. Most complete tour. |
| 2D Platformer | Heatmap (jump + death positions), level screenshot, level completion funnel, remote config for physics | Side-scrollers, level-based games |
| 3D Platformer | XZ-projection heatmap, top-down screenshot capture, rich presence, cloud save with collectibles | 3D games, exploration / collect-a-thons |
| Rhythm Game | Game Data hot-reload (beatmap from dashboard), per-input UI tracking, hit-window remote config | Music games, anything with content tables |
| Save / Load Demo | Cloud-save round-trip, 409 conflict resolution, multi-slot payloads, data-loss recovery | Anything with persistent player progress |
| Bullet Shower | perf_sample events, FPS-drop error reporting, device info on session start, stress-test patterns | Performance-sensitive games (bullet hell, simulation) |
Before you start
Section titled “Before you start”These walkthroughs assume the Quest Data backend is running locally. If you haven’t set it up yet, follow the Quick Start first — it boots the stack with docker compose up and seeds the dev-key-* API keys these demos use.
If you already shipped your own game and just want the API surface, skip to Godot SDK Setup and Event Tracking.