Contribute · QA Annotate Mode

Reporting Visual Bugs In-Game

Both playable demos have a built-in bug-reporting mode. Spot a misplaced, misoriented, glitched, or broken-looking model? Click it in-game and file a report — the game records exactly which asset it is, where it sits in the level, and where you were standing. No guessing about which “weird brown thing” you meant.

🎮 Boy Genius 🚀 vs. Jimmy Negatron

  1. Play normally until you see something wrong (WASD to walk, N for noclip flying if you want a closer look).
  2. Press B (think “bug”) or tap the QA: Off button in the top bar — it flips to QA: On. Your mouse cursor now inspects instead of steering the camera.
  3. Hover over any model: it lights up yellow and a label shows its name (e.g. labshak · placement or 3JIM [JIM1] · entity).
  4. Click the broken model. It turns orange and a report dialog opens.
  5. Pick a category:
    CodeMeaning
    PLCwrong position
    ORIwrong orientation / rotation
    SCLwrong size
    ANIanimation wrong or missing
    TEXtexture wrong or missing
    MISmodel missing entirely
    GFXother visual glitch
    OTHanything else
  6. Describe the issue in a sentence (“rotated 90° vs original”, “floats above the ground”, “texture is the fence instead of bark”) and hit OK. (Cancel or Esc discards.)
  7. A tag appears in the top-right corner — your reports stack up as you keep playing and survive switching levels. Hover a tag’s ✕ to re-read its note, click ✕ to delete it. Press B again to return to normal play anytime.
  8. When your session is done, hit export at the top of the tag stack — it copies the full report (a readable table plus machine-readable data) to your clipboard.

📤 Send it in

Paste the exported clipboard contents into a Discord DM to scotty (or the engine-troubleshooting channel). The paste contains everything needed to find and fix each issue — asset names, coordinates, camera position, your notes — so it goes straight into the engine’s fix queue.