Codename BugTracker

In-game bug reporting for Unity playtests. Tester presses F1, types what broke, and the report lands in a web dashboard with a screenshot, machine specs, the active scene, the log tail and a breadcrumb trail of what they were doing.

Unity setup

1. Copy Unity/Assets/Playtester/ into your project's Assets/.
2. Add BugReporter to one GameObject in your first scene. It survives scene loads via DontDestroyOnLoad and de-dupes itself if it ends up in two scenes.
3. Set Endpoint to http://<host>:5080/v1/reports and Api Key to match the server.

Put breadcrumbs through gameplay code wherever a tester does something notable:

using Playtester;  
Breadcrumbs.Drop("Picked up keycard"); 
Breadcrumbs.Drop("Entered room {0}", room.name);

Consecutive identical entries collapse (Called elevator (x6 over 9.4s)), so a tester mashing one input doesn't flush the interesting history out of the 20-entry window.

The panel: F1 opens it, Esc or Cancel closes it, Send report submits. Send stays greyed out until the message box has text.

Notes on the Unity side:

• pauseWhileOpen (on by default) sets Time.timeScale = 0 while the panel is up and restores the previous value on close. Without it the tester's typing also drives gameplay — WASD walks away from the bug being reported. Uncheck it if your game manages its own pause state.
• Gate your own input reads on BugReporter.IsOpen if you read raw keys anywhere, since IMGUI focus doesn't stop Input.GetKey from firing.
• The screenshot is captured at end-of-frame before the report UI is drawn, so the overlay never appears in the attachment.
• Screenshots are downscaled to screenshotMaxWidth (default 1280) and JPEG-encoded at jpegQuality (default 70) — roughly 60–120 KB per report.
• The log tail hooks logMessageReceivedThreaded and keeps the last 50 lines; errors and exceptions carry their stack traces.
• Works with both the legacy Input Manager and the new Input System (compile-time switch).
  
  Jira Cloud forwarding
  Publishing is manual — a Publish to Jira button on each report — so duplicate reports of the same bug don't each spawn an issue. Credentials are server-side only. 
• Create an API token at https://id.atlassian.com/manage-profile/security/api-tokens, then either put it in appsettings.json: