Forge Logger — in-game bug reporting for Godot 4 (free MIT plugin, F8 → structured report)

Showcase Applications
,
1

Hi all — I’ve been building Forge Logger, a small MIT-licensed plugin that turns
playtest feedback from “it crashed lol” + a blurry Discord screenshot into a
structured bug report, and it’s now on the Asset Library. Sharing it here for
Godot 4 folks and hoping for some honest feedback.

What it does: your playtesters press a key in-game (F8 by default, rebindable),
type what broke, and you get a report with a screenshot, the log file, and the exact
scene, build and environment it happened in. You can also fire reports from code with
capture_bug() and drop breadcrumbs onto a session timeline with record_event().

demo

A few things I cared about:

  • Privacy-first: device info is opt-in and off by default. You can point
    base_url at your own backend and no data leaves your infrastructure.
  • Offline retry queue with idempotent submits — reports survive an unclean shutdown
    and get re-sent on next launch, without duplicating server-side.
  • The plugin is free forever (MIT). There’s an optional hosted dashboard with a
    free tier (100 reports/month, no card) that adds AI summaries, suggested repro
    steps, duplicate detection and one-click GitHub export — but the plugin works
    against your own backend if you’d rather self-host.

Setup is ~10 minutes: install from AssetLib → enable the plugin → paste a
project id + token from the free dashboard (or your own backend URL) → run → press F8.

Being upfront about what it does NOT do (yet): this is player-triggered
reporting — it does not auto-capture hard crashes or stack traces. That’s on the
roadmap; queued reports do survive an unclean shutdown and re-send next launch.

Would love feedback from anyone running playtests — especially what you’d want out of
the in-editor setup and whether the F8 flow fits how your testers actually play.
Happy to answer questions in the thread.

1 Like