Bugs are a normal part of game development — including AI game development. Tesana gives the AI unusually good debugging inputs; this page shows how to use them.

​
Find bugs by playing like a player

The live preview is your test bench. Play the way a player would: try every interaction, push the edges of the rules, do things you “shouldn’t”. Watch for visual glitches, broken mechanics, flow problems (stuck screens, win conditions not firing), performance dips, and odd edge cases.

​
Report bugs like a pro

The quality of the fix tracks the quality of the report. Include:
Great report: “When the player jumps while standing on the moving platform on level 2, they get stuck inside the platform and can’t move. Happens every time. They should land back on top.”Weak report: “Jumping is broken.” The fix will be a guess — and guesses break other things.

​
Give the AI evidence, not just words

  • Screenshots — the camera button in the preview attaches a screenshot to your next prompt. For visual bugs this is the single highest-value thing you can do. (When you send an edit without screenshots, the Studio also auto-captures the current preview so the AI can see the game’s state.)
  • Console logs — runtime errors from the preview are captured and attached automatically. When an error banner appears over the preview, its Fix button sends the full error log straight to the AI.
  • Ask for investigation first — for gnarly bugs: “look into why X happens before changing anything.” The AI explains its diagnosis before touching the game, like plan mode for fixes.

​
When the first fix doesn’t work

Normal. Reply with what you observed after testing: “the character no longer gets stuck, but now falls through the platform instead.” Each round narrows the search. If a bug keeps coming back, reframe from the glitch to the desired behavior: instead of “fix the jump bug on level 2”, try “the player should always land on top of solid platforms, even moving ones.” Reframing usually produces the cleaner, structural fix.

​
Escape hatches

  • Revert — when a build made things worse overall, roll back and re-prompt rather than patching a bad state.
  • Support — if the platform seems broken (build crashed, game stuck in generating, charged with no output), that’s not a prompting problem; see Troubleshooting and write in.