iiinova — where your digital self keeps evolving

Forge Logger @forgelogger.dev · 01/10/2026

Your demo is on Steam, itch, Discord and in a creator's video. Which of those players actually answer your feedback form? Building now in Forge Logger: one form, a separate link for each place you share it, with visits, responses and conversion per link. forgelogger.dev #GodotEngine #gamedev

Forge Logger dashboard listing five links to the same demo feedback form: Steam Next Fest, itch.io page, Discord, Creator video and In game. Each has its own URL, UTM source and counts of visits and responses. Sample data.

Forge Logger responses overview for one form: 124 responses, average rating 3.8, star rating and 'Would you buy it?' price distributions, and a links funnel with visits, responses and conversion per link, from 8% on the Steam Next Fest link to 24% on the creator video link. Sample data.

162

Forge Logger @forgelogger.dev · 29/09/2026

A survey link can't tell you which answers came from players who quit after 3 minutes. Building now in Forge Logger: demo feedback forms, in-game in Godot or as a web link, with each answer tied to the player's session: playtime, build, crashes. forgelogger.dev #GodotEngine #gamedev

End-of-demo screen of a Godot game with the Forge Logger feedback form on top: 4 of 5 stars, the answer 'Loved the fog puzzles — more levels please!' and $10 picked for 'What would you pay for the full game?'. Sample game Lantern Keep.

Forge Logger dashboard splitting demo feedback by playtime: under 5 minutes averages 2.4 stars, 5 to 20 minutes 3.5, 20 to 60 minutes 4.2, over an hour 4.5, with the share who would buy and the average price for each group. Sample data.

The same feedback form as a web page on a phone: game art, 4 of 5 stars and a typed answer about the fog puzzles and controller feel.

074

Forge Logger @forgelogger.dev · 24/09/2026

A tester reports a bug from a release build and the attached godot.log stops short: in exports it stays buffered on disk. On Godot 4.5+ Forge Logger captures engine output in memory instead, error backtraces included, so the log arrives complete. forgelogger.dev #GodotEngine #gamedev

072

Forge Logger @forgelogger.dev · 03/09/2026

The plugin is MIT and free forever — point it at your own backend and nothing reaches my servers. The hosted dashboard is optional: 100 reports a month free, no card. Built for indie playtests. #GodotEngine #gamedev

The Forge Logger dashboard overview showing recent reports.

052

Forge Logger @forgelogger.dev · 01/09/2026

"It crashed lol" is not a bug report. Ten minutes from now your Godot game can collect real ones: install, paste one token, press F8. Full walkthrough: forgelogger.dev/docs/plugins... #GodotEngine #gamedev

The Forge Logger reports list, each report showing its scene, build and environment

051

Forge Logger @forgelogger.dev · 27/08/2026

The same bug, reported 12 different ways by 12 testers. Forge Logger folds them into one thread instead of an inbox pileup — so you fix it once, and you know how many people actually hit it. #GodotEngine #gamedev

Forge Logger showing deduplicated event groups folded into single entries.

081

Forge Logger @forgelogger.dev · 25/08/2026

Build-in-public: the numbers are small — 8 accounts, 2 filing reports. Then one person filed 9 in a day and came back the next. Small numbers, real signal. Building Forge Logger for Godot in the open. #GodotEngine #gamedev

061

Forge Logger @forgelogger.dev · 21/08/2026

We playtest this one with our own plugin — here's the mill it reports on.

000

Forge Logger @forgelogger.dev · 20/08/2026

Nerd corner: every Forge Logger report carries a client-generated UUID and the offline queue retries idempotently. So a playtest on flaky hotel wifi never turns into six copies of the same bug. #GodotEngine #gamedev

051

Forge Logger @forgelogger.dev · 18/08/2026

Found a real bug in the pile? One click turns it into a GitHub issue — screenshot, scene, build and session context attached. No copy-paste archaeology. Forge Logger for Godot. #GodotEngine #gamedev

Forge Logger project settings with the GitHub export integration configured

072

Forge Logger @forgelogger.dev · 30/07/2026

Your testers write two rushed sentences. You read one clean paragraph with suggested repro steps — because every Forge Logger report gets an AI summary. Less triage archaeology, more fixing . #GodotEngine #gamedev

072

Forge Logger @forgelogger.dev · 28/07/2026

Before: 47 Discord messages, 3 blurry screenshots, zero build numbers. After: one filtered list of reports — each with the scene, build and environment attached. That's Forge Logger for Godot. #GodotEngine #gamedev

Forge Logger reports list, filtered, each report showing scene, build and environment."

070

Forge Logger @forgelogger.dev · 20/07/2026

Breadcrumbs for playtest bugs 🥖 ForgeLogger.record_event("boss_phase_2") Every event lines up on the session timeline next to the report — so when a tester says "it broke," you already see what they did right before. Context you didn't have to ask for. #GodotEngine #gamedev

The session event timeline in Forge Logger, showing recorded gameplay events lined up next to a bug report.

0111

Forge Logger @forgelogger.dev · 17/07/2026

Privacy by default: Forge Logger for Godot sends device info only if you opt in (off by default), and you can point the plugin at your own backend — no data has to leave your infra. Your data, your call. #GodotEngine #gamedev

0100

Forge Logger @forgelogger.dev · 15/07/2026

Forge Logger is live on the Godot Asset Library 🎉 Free MIT plugin for Godot 4: F8 bug-report popup, screenshots, offline retry queue, session context. Optional hosted dashboard adds AI summaries + triage. godotengine.org/asset-librar... #GodotEngine #gamedev

182

Forge Logger @forgelogger.dev · 13/07/2026

Playtest feedback shouldn't be "it crashed lol" + a blurry Discord screenshot. I'm building Forge Logger for Godot: press F8 in-game, type what broke, and the report arrives with the screenshot, scene, build and environment attached. #GodotEngine #gamedev

0112