Forge Logger — In-Game Bug Reporting & Player Feedback for Godot

Your playtesters press one key, type what broke, and you get a structured bug report — with a screenshot and the exact scene, build, and environment it happened in — instead of a blurry screenshot dumped in Discord.

A free, open-source Godot 4.x plugin. Drop it in, set one project ID, and your game can collect real bug reports from real players. Triage them yourself against your own backend, or connect the optional hosted dashboard for AI summaries and one-click export to GitHub.

Why

Playtest feedback is chaos. Testers paste screenshots into Discord with "it crashed lol", you can't tell which build they were on, and triage becomes archaeology. Forge Logger turns that into something you can act on — captured from inside the game, the moment the bug happens.

• Player-facing, not just a crash logger. Testers report what they noticed, in their words, with a screenshot attached.
• Context comes for free. Each play session is stamped with the scene, game version, build hash, and environment, and every report links back to its session — no "which version were you on?" round-trips.
• Works offline. Reports that fail to send are queued to disk and retried after an unclean shutdown — or whenever you call retry_queued() — with idempotency so retries never duplicate.
• Godot-native. Built for Godot first, not a Unity tool with Godot bolted on. One autoload, configured in Project Settings.
• Yours to keep. MIT-licensed. Point it at your own ingest backend, or use the hosted dashboard — your call.

Install

From the Godot Asset Library (recommended)

1. In the editor: AssetLib tab → search "Forge Logger" → Download → Install.
2. Project → Project Settings → Plugins → enable Forge Logger.

Manual

1. Copy the forge_logger/ folder into your project's addons/ directory (so it lives at addons/forge_logger/).
2. Project → Project Settings → Plugins → enable Forge Logger.

Enabling the plugin registers the ForgeLogger autoload singleton. The forge_logger_report input action (default key F8) is registered automatically the first time your game runs — rebind it under Project Settings → Input Map.

Quick start

1. Point it at a project. Open Project → Project Settings, turn on Advanced Settings, and find the forge_logger/ section:

Using the hosted dashboard? Both values are one click away: create a free project, then mint a logger token under Project → Tokens and paste the flg_… value into api_key.

Privacy: session telemetry carries engine version, platform, and current scene. The device model and locale are sent only if you turn collect_device_info on — off by default. Point base_url at your own backend and no report data reaches Forge Logger's servers.

2. Let players report. The smallest possible integration — bind the built-in popup to the report action:

func _unhandled_input(event: InputEvent) -> void:
    if event.is_action_pressed("forge_logger_report"):
        ForgeLogger.show_report_popup()

The player types a title and description; the report is sent with session metadata attached (plus a screenshot if you've turned on enable_screenshot). Done.

3. Or wire your own UI / fire reports from code:

# Submit from your own form (attach_logs, attach_screenshot)
ForgeLogger.submit_ui_report("Stuck in wall", "Walked into the crate near spawn and clipped through.", true, true)

# Capture a bug programmatically — e.g. from an error handler
ForgeLogger.capture_bug({
    "title": "Null inventory",
    "description": "Opened shop with no save loaded",
    "severity": "high",
    "tags": ["inventory"],
    "custom_data": { "scene": get_tree().current_scene.name },
})

# Drop lightweight events onto the session timeline
ForgeLogger.record_event("level_started", { "level": "forest_02" })

Public API

Free plugin + optional hosted dashboard

The plugin and the Discord bot are free forever and MIT-licensed. Point base_url at your own backend and you never pay a thing.

If you'd rather not run infrastructure, the hosted dashboard is optional:

→ Create a free project — no card required.

Unity & Unreal: the ingest backend is engine-agnostic and ports are on the roadmap. Want one? Join the waitlist and tell us which engine.

How it talks to the backend

Project scope is carried by the logger token, not the URL. The plugin targets the forge-logger-ingest-be service:

Reports carry a client-generated clientRequestId (UUID), persisted in the offline queue. Retries with the same key return { idempotent: true, ... } and never create duplicates server-side.

Attachment limits: screenshots png/jpeg/webp ≤ 10 MiB · log bundles ≤ 50 MiB · save states ≤ 100 MiB · video webm/mp4 ≤ 500 MiB. Aggregate ≤ 600 MiB/report (otherwise 413).

Roadmap

• Crash dialog: prompt the player to send diagnostics after an unclean shutdown
• Replay / save-file attachments
• Configurable retry backoff
• Custom popup theming
• Unity & Unreal clients (engine-agnostic backend already in place — waitlist)

Links

• 🌐 Website: https://forgelogger.dev · Dashboard: https://forgelogger.dev/auth · Docs: https://forgelogger.dev/docs/plugins/godot
• 📦 Asset Library: [ASSETLIB_URL]
• 💻 Source — issues & PRs welcome: https://github.com/stoneforgelabs/forge-logger-godot

License

MIT. Use it in commercial games, fork it, ship it. See LICENSE.