Send fix prompts

When you find a defect by running the game with Launch, describe it as "what you saw + what you want" and send it in the same conversation where the game was built. The AI finds the cause by opening the scene and scripts. This page covers the prompt format, how to group several defects by number, and when it's better to fix things by hand.

Before you start

• Play the game from start to finish with Launch and write down anything odd exactly as you saw it. How to run the game is in Run with Launch.
• First decide whether it's a defect or something you didn't put in the prompt. If you wrote it in the prompt and it doesn't work, it's a defect. If you don't like something you didn't specify, add it to the prompt. The criteria are in Principles for writing prompts.
• If the task stopped short, continue it before sending a fix prompt. See When the AI stalls, stops short, or loops.

Do it in the editor

If you know exactly where and what to fix, it's better to fix it by hand. It takes a few seconds, uses no credits, and changes only the field you edit. An AI prompt takes several minutes, and there have been cases where it also changed things you didn't ask for.

These are the manual fixes we made in testing that took effect in the game.

If you don't know which field on which entity holds the value, ask the AI only for the location and make the fix by hand. The prompt is in When you only want an explanation below.

Let the AI do it

Prompt format: what you saw + what you want

Write a fix prompt in two parts.

1. What you saw: what appeared, and how, when you ran the game with Launch.
2. What you want: how it should behave.

Don't write the cause. If your guess is wrong, the AI may fix something that works fine. The AI can open the scene's entities and scripts directly, so leave finding the cause to the AI and describe precisely what you saw. On the other hand, the AI can't play the game all the way through, so you have to tell it what's wrong.

Group multiple defects by number in one prompt

If there are several defects, you can number them and send them in one prompt. Write only one observation per number. This is the prompt we actually sent after finding 3 defects in the first game.

PromptCopy

I ran it with Launch and three things are wrong.1. As soon as the game starts, "You win!" is shown in the middle of the screen.2. When the ball touches a star, the star disappears, but the "Stars collected" number doesn't go up from 0.3. When I roll the ball, the camera doesn't follow it and the ball goes off screen.Fix only these three things and leave everything else as it is.

The AI first found the causes and briefly reported them, then fixed them while adding ✓ lines as in the initial build, and ran the game to check. This prompt fixed all three defects in about 4 minutes.

Results of fix prompts grouped by number:

Of the 7, 4 finished in one prompt, 2 needed a continue prompt, and 1 wasn't fixed and we had to send the remaining defects again. So after sending a grouped prompt, read the last line and the summary just above it, and if it stopped short, follow up with the "It's not finished yet…" prompt from When the AI stalls, stops short, or loops.

Even if a grouped prompt fixes most defects, check separately whether anything else changed. We haven't yet tested how this compares with sending defects one at a time.

"Leave everything else as it is"

Ending a prompt with "Leave everything else as it is" or "Don't touch anything other than what I asked for" states the scope of the fix in words. Work on stopping the AI from changing things it wasn't asked to change is ongoing, so add this sentence to every fix prompt (see Principles for writing prompts). However, this sentence didn't prevent every unrequested change. Even with it, there were cases where the surrounding walls were deleted, and where the auto-check decided the scene was "too dark" and changed materials across the whole scene. So after a fix, don't just look at the fixed spot; play the whole game again. How to find what changed is in Check what the AI changed.

When you only want an explanation

When you're only asking about a cause or where a value is, add "Don't fix anything." This is the prompt we actually sent.

PromptCopy

Tell me which field on which object sets how fast the ball rolls.Also tell me its current value.Don't fix anything.

In about 1 minute the AI answered Ball's ballMove → maxSpeed (value at the time: 11), and changed nothing. Using that answer, edit the SCRIPT field by hand.

In 1 of 3 explanation/question prompts, the auto-check changed the color and size of the on-screen timer text even though we added "Don't fix anything." The script file we asked about was left unchanged. Even after an explanation prompt finishes, read the summary to see what changed.

Check the cause and scope in the plan

When you send a fix prompt, a plan card appears before the work starts. In a test on 2026-10-27, when we sent 2 defects grouped together, the plan contained these four things.

• Cause: "Both symptoms have the same cause. The star script's scoreText/winText attributes aren't linked, so …"
• Where to fix: "recipeCollectible.js: change the script to find the Score and Win text automatically by name"
• Expected result: "The Win message is off at start, and the number goes up each time a star is eaten …"
• What to leave alone: "The 10 stars, floor, walls, trees, camera, and the rest of the UI stay as they are"

Check that the cause matches the symptoms you saw, that the expected result covers every number you sent, and that what to leave alone includes everything that must not be touched, then click 예 (Yes). If one of your numbers is missing from the plan, click 아니오 (No) and send the missing number again. How to read the plan card is in Read the plan and work steps.

There's no guarantee it finishes according to plan. In the same test, a fix prompt in another run found only the cause, hit the "tool call limit", and ended with 씬에 반영할 변경이 없습니다 (No changes to apply to the scene) without fixing anything. When we then sent the following sentence in the same conversation, the plan card appeared again, and after we clicked 예, 1 of the 2 defects was fixed (1 run).

PromptCopy

Fix it based on the cause you found.

Read the report after sending

In the runs we observed, the report for a fix prompt came in two parts. The headings varied slightly from run to run.

Some runs had all defects fixed even though the last line was 문제 N건 남음, and some still had defects even though it was 문제 없음 (no issues). The last line tells you where to start looking. How to read it is in Read the last line and the auto-check.

Check the result

1. Refresh the game tab you have open. If you don't, you'll still see the game from before the fix. If you closed the game tab, click ▶ Launch again.
2. Start with the items listed under "remaining checks" in the report.
3. Check each number you sent, then play the game from start to finish again. There have been cases where something other than the fixed spot changed.
4. If the project has other scenes, run them too. There are 2 cases where fixing a shared script changed the game in another scene. Details are in What's per scene and what the project shares.

Troubleshooting

Next steps

• Check what the AI changed
• When the AI stalls, stops short, or loops
• Read the last line and the auto-check
• Principles for writing prompts
• Undo AI work
• Credits