Quick Start

Get Quest Data running in your Godot 4 game in under 5 minutes. By the end, you’ll see live events flowing into your dashboard.

Prerequisites

• Godot 4.x (4.0 or higher)
• Internet connection for sending analytics data
• 5 minutes of your time

1. Create an Account

Sign up at your Quest Data dashboard (e.g. https://quest-data-seven.vercel.app). The free tier includes unlimited events and all core features. You’ll be automatically logged in after registration.

2. Create a Game

1. Click + New Game on the Games page
2. Enter your game’s name
3. Copy the API Key shown on the game card — you’ll need it in the next step

Tip

You can always find your API key later under Configuration > API Keys in the dashboard.

3. Install the Godot SDK

Download the SDK from wolke.digitalfactory.at/index.php/s/t7zP3PP6wGD9jQt (or grab the latest tag from GitHub Releases) and copy the addons/quest_data/ folder into your Godot project:

MyGame/
├── addons/
│   └── quest_data/        ← copy this folder
│       ├── plugin.gd
│       ├── quest_data.gd
│       └── modules/
├── scenes/
└── project.godot

Then enable the plugin:

1. Open Godot and load your project
2. Go to Project > Project Settings > Plugins
3. Find QuestData and check Enable
4. Restart Godot (required for AutoLoad registration)

4. Configure the SDK

After restart, the plugin creates settings under Project > Project Settings > General > Quest Data:

Setting	Description	Default
quest_data/api_key	Your API key from step 2	dev-key-12345
quest_data/dev_api_url	API URL for debug builds	http://localhost:3010/v1/track
quest_data/prod_api_url	API URL for release builds	https://quest-api.digitalfactory.at/v1/track

Set your API key. The SDK automatically selects the dev or prod URL based on OS.is_debug_build() — no manual switching needed.

Note

Enable Advanced Settings in Project Settings to see the Quest Data section.

5. Track Your First Event

Add this to any script in your game:

func _ready():
    QuestData.track("game_start", {
        "version": "1.0.0",
        "platform": OS.get_name()
    })

Wait for SDK in your own Autoloads

If you have your own Autoload that needs SDK features in _ready() (binding balancing, fetching remote config, calling cloud saves), wait for sdk_ready first. Autoload-Order is not guaranteed in Godot — your Autoload might run before QuestData finished its sync init:

extends Node

func _ready() -> void:
    # Idempotent — returns immediately if SDK already initialized.
    await QuestData.await_ready()

    # Now safe to use SDK features
    QuestData.bind_balancing(my_resource, "buildings", "farm")

Equivalent if you prefer the explicit signal style:

if not QuestData.is_ready():
    await QuestData.sdk_ready

That’s it. The SDK handles everything else:

1. Events are queued in memory (no blocking)
2. Batched and sent every 10 seconds (or when 10+ events queue up)
3. If offline, events are saved to disk and retried later
4. On game exit, unsent events are persisted automatically

6. See It Live

1. Open your game’s dashboard
2. Enable the Live toggle in the top-right corner
3. Run your game
4. Events should appear in the Live Feed within ~10 seconds

Not seeing events?

Problem	Solution
”Undefined identifier: QuestData”	Plugin not enabled or Godot not restarted
Events not appearing	Check API key matches your game, wait 15 seconds
Network errors in console	Verify API URL (no trailing slash)
Still nothing	Force flush: QuestData.flush() and check Configuration > Logs

Next Steps

Now that events are flowing, explore what Quest Data can do for your game:

Track Game Progress

• Progression Tracking — Level starts, completions, failures with automatic duration
• Error Tracking — Crashes with stack traces and pre-crash telemetry

Monetization

• Purchase Tracking — In-app purchases, revenue, currency

Live Ops (no app update needed)

• Remote Config & Game Data — Feature flags, balance tables, A/B testing
• Leaderboards — Global rankings with score throttling
• Achievements — Unlock tracking with caching
• Cloud Saves — Save/load with version control

Player Management

• Players & Segments — Tags, properties, segment-based config overrides

Debugging

• Remote Logging — Send logs to dashboard, filter by level/player

Full Event Reference

• Event Tracking Guide — All event types, properties, limits, batching behavior