Quick answer: A one-key bug reporter beats a six-step menu. Bind a shortcut, capture state, queue offline, send when ready - here's the minimal contract that ships.
The most valuable shortcut you'll ever ship: F2 opens a one-field bug form with screenshot, log, system info, and last-input replay attached.
Bind a single key
F2 is conventional. Make it unbindable in the rebinder UI - this is a developer/QA shortcut, not a gameplay action.
Capture before showing UI
Take the screenshot, snapshot the log buffer, freeze the input replay - all before drawing the form. Otherwise the form itself is in the screenshot.
Queue offline
If network is down, write the report to disk and retry on next launch. SDK ships an offline queue you can plug into.
One field, one button
POST /api/bugs
{ "description": "...", "context": {...} }The Bugnet SDK is essentially this. Keep your wrapper that thin.
“The bug report that gets sent in 5 seconds is worth ten that take 5 minutes.”
Ship the shortcut in production builds gated behind a config flag. Power users will discover it; you'll discover bugs you didn't know about.