Guides
Fix errors
Find and fix bugs from the Output window, a description of the symptom, or both.
Debugging is one of the most useful things to hand to the agent. It can read your scripts, see the Output window, and trace a problem across scripts faster than scrolling through them.
From an error message#
If there is an error in Output, you can simply say:
Fix the error in the Output window.The agent reads recent Output messages, follows the stack trace to the script and line, works out the cause, and fixes it. It explains what was wrong in the summary.
From a symptom#
Many bugs do not throw errors. Describe what you see:
My leaderboard stops updating after a player rejoins. Coins still
go up in the shop, but the number on the leaderboard stays the same.The agent reads the scripts involved, finds where the value and the leaderboard drift apart, and fixes the cause rather than the symptom. When the bug only shows while the game is running, it may ask you to reproduce it in a playtest so it can read the Output.
Check it#
Reproduce the problem the way you found it. If it is a rejoin bug, test with Clients and Servers. If the fix is not right, say what still happens; the agent keeps the context.
Tips#
- Say how to reproduce it: "after rejoining", "only on mobile", "when two players buy at once".
- Mention what you already tried, so the agent does not repeat it.
- Ask "why did this happen?" afterwards if you want to avoid the same bug next time.