Bug reports, screenshots and shake to report

Players describe bugs in many languages and many ways. Inngame attaches what your team needs and helps you close the loop when you ship a fix.

🎮 Player experience2 min read

On this page
  1. Screenshots in one gesture
  2. Context with every message
  3. From reports to one bug

Screenshots in one gesture

  • The chat has a screenshot button (the chat itself is never in the capture).
  • Desktop: a hotkey, F8 by default (ScreenshotHotkey), captures and opens the chat.
  • Mobile: turn on ShakeToReport (off by default) and players shake the phone to capture and open the chat.
  • From code: Inngame.CaptureScreenshot().

Photos are moderated before they're stored.

Context with every message

Each player message carries the device, OS, app version and build, scene, GPU, memory, FPS and the last 50 log lines (Unity), or the page, browser and console errors (web). Your team sees it next to the conversation; players never do.

From reports to one bug

  1. Link a conversation to a bug from the inbox (or let the AI group reports automatically, when bug detection is turned on for the app).
  2. The Bugs page shows reports, versions, platforms and log excerpts, with spike alerts in the inbox, Telegram and Discord.
  3. One click opens a GitHub issue (no player identity), and you can ask the coding agent on your repository for a fix PR. Inngame never merges.
  4. Set fixed in version: players are told, in their language, the first time they open that version.

Still need help?

Chat with us: our assistant answers right away, and hands you to the team when it can't.