Skip to main content

The Power of Pride Bundle 2026 — $10 PWYC Edition
On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

DevQuo

3
Posts
1
Topics
A member registered 24 days ago

Recent community posts

Bug Deck demo: tester finds a bug, reviews the report, then exports a clean bug report.

sorry for the delayed response for game internal state v1 wont automatically have the ability to capture deep internal game state because i dont want it to be invasive, 

The first version will focus on screenshot, notes, logs, PC specs, severity, and game version. long term id like to support an easy lightweight SDK where developers could choose what state gets attached like player pos or level name but this is only if the developer enables it manually

(4 edits)

I’m building a desktop app idea called Bug Deck for indie game developers.

The problem I’m trying to solve is playtest feedback being too vague, like: “it broke,” “game crashed,” or “I got stuck somewhere.”

The idea: Bug Deck helps testers create clear, privacy-aware bug reports during controlled playtests/QA.

Instead of automatically grabbing everything, the planned v1 would be local-first and review-based. The tester/dev chooses what gets included before exporting the report.

A report could include:

  • game-window screenshot
  • tester notes
  • logs chosen by the developer
  • basic PC specs shown before export
  • severity
  • game version
  • clean Markdown/JSON export

Bug Deck is meant for controlled playtests, not random public players. It would not automatically upload data in v1, and any deeper internal game state would only come later through an optional developer-controlled plugin/SDK.

I made a landing page and short demo video before building the full desktop app because I want to know if this actually solves a real problem.

Would this be useful for your playtesting workflow, or is it unnecessary?

Bug Deck Website

Privacy / Safety FAQ

Does Bug Deck upload data automatically? No. The planned v1 is local-first and export-based. Reports stay on the tester’s machine unless the tester/dev chooses to share them.

Does it screenshot the whole desktop? No. The goal is game-window capture, not full-desktop screenshots.

Can players use it to expose private game data? Bug Deck is meant for controlled playtests/QA, not random public players. No internal game state would be captured automatically.

What about internal game state? That would only come later through an optional developer-controlled plugin/SDK. The developer would choose exactly what data can be attached.

Can the hotkey be changed? Yes. The shortcut should be configurable so it doesn’t conflict with engines like Godot.

What makes this more than a screenshot note tool? The goal is the full workflow: consistent reports, selected logs, build/version info, specs previewed before export, severity, repro steps, and clean exports for wherever the developer already works.

Would this be useful for your playtesting workflow, or is it unnecessary?