Section 10. Publishing and troubleshooting
Reference
Troubleshooting by symptom
This page collects symptoms actually observed in the editor, in AI work, and when running with Launch, listed as symptom · cause · fix. The links in the fix column lead to detailed steps.
In tests where we built a game 7 times from the same prompt and then added rules, three symptoms came up most often. They are the top three rows of the "AI work" table. Check these three rows first.
This page doesn't cover problems with publishing a game (Publish / Download). Publishing symptoms are covered in Publish your game.
AI work
| Symptom | Cause | Fix |
|---|---|---|
The last line says 자동 점검: 문제 없음 (Auto-check: no issues), but the game is wrong (a win message or game over shows as soon as it starts, the score doesn't go up from 0) | The AI's auto-check is based on a run of a few seconds. It is not the result of playing to the end. In some cases the AI didn't revert values it changed for testing (for example, 1 life) | Reload the game tab and check again. If it's still the same, send a prompt listing what you saw as numbered items. Read the last line and the auto-check, Send fix prompts |
The work isn't finished (the last line is 자동 점검: 문제 N건 남음 (Auto-check: N issues remaining), or the summary just above it says "couldn't finish" or "remaining work") | The AI couldn't finish the work within one prompt | Don't have it rebuild from scratch; tell it to continue in the same conversation. Of the 7 first builds, all 3 that we told to continue were finished. When the AI stalls, stops short, or loops |
| Things you didn't ask for changed (a perimeter wall appeared or disappeared, lighting, materials, or the camera were replaced wholesale, the text color changed when you only asked for an explanation) | In some cases the AI changed things outside the scope of the prompt to make the game look plausible or to fix auto-check results. 5 of 7 builds got a perimeter wall. It happened even with "Leave everything else as is." added | Check the change report and the changed assets. We haven't yet tested a prompt that points out the changes and asks to revert them. Fix things you can change by hand, such as material colors, manually. Check what the AI changed |
| A game in another scene of the same project broke | Scenes share scripts. There were 2 cases where the AI edited a shared script in one scene and broke another scene | Send a prompt in the broken scene describing exactly what you see (we haven't yet tested the result of the fix in this case). If you have a game you want to keep, do AI work only in that scene. What's per scene and what the project shares |
| The AI couldn't create a new script file | The name collided with a file left over from work in another scene (observed once) | First ask the AI whether the colliding file is in use. Check what the AI changed |
| The first build takes a long time | This is normal. The first build took 6 to 10 minutes, and adding one rule took 2–3 prompts and 10 to 30 minutes | If the button in the AI panel is 중단 (Stop) and the ✓ rows or the tool count on the progress row keep increasing, wait |
| The AI is working but HIERARCHY and the viewport don't change | This is normal. The AI applies its results to the scene all at once when it finishes | Wait until the 씬에 반영했습니다 · … (Applied to the scene · …) row appears. Open the AI panel and send a prompt |
The progress row has stayed at AI가 생각하는 중 (AI is thinking) for several minutes | It may be waiting for AI work in another project to finish (observed once) | Send AI work one prompt at a time. When the AI stalls, stops short, or loops |
| The button went back to 보내기 (Send), but it finished without a summary | If there is a 씬에 반영했습니다 row, it finished without a summary (2 fix prompts, results correct); if that row is missing too, it stopped partway | If the applied row is there, check with ▶ Launch. If not, send a prompt in the same conversation asking it to continue building. When the AI stalls, stops short, or loops |
In under a minute the AI said "I couldn't finish this request," but the last line is 문제 없음 (no issues) | Nothing was changed, so there was nothing to check | Treat it as unfinished and tell it to continue |
| The summary says it "hit the run limit and couldn't finish the final behavior check" | The AI used up the number of times it can run the game in one prompt. This happened in 3 of 7 builds | It hasn't stopped. Check it yourself with ▶ Launch. Run with Launch |
| The AI keeps repeating the same check | The AI is repeating the same check (looping). This happened in 2 of 7 builds, and in one build it went on for about 5 minutes | Click 중단, stop the checking, and ask it to just wrap up. In the one time we tried, we got the wrap-up after about 2 minutes 30 seconds. When the AI stalls, stops short, or loops |
| After you told it to continue, the AI said it "finished the rest," but some rules still don't work | Finishing is not the same as being free of defects | Send a separate fix prompt for only the remaining symptoms. Send fix prompts |
ASSETS contains a script with an unfamiliar name such as debugProbe.js | It's a file the AI created for testing. In 4 of 7 builds, the AI didn't delete this file and instead reused it for another feature | Read its contents in CODE before deleting it. Check what the AI changed |
| The AI's explanation doesn't match reality (for example, it describes a blue ball as a red ball) | The AI based its explanation on old code comments | Check explanations against the code and the Launch result. Read and edit AI-generated code |
| You only asked for an explanation, but the AI fixed something | You didn't add "Don't change anything," or you did but the auto-check changed something else (observed once) | Add "Don't change anything." to explanation prompts, and read the summary when it finishes. Send fix prompts |
| The text on the game screen comes out in English | The prompt didn't specify the screen language | State the language for on-screen text in the prompt. For a game you already built, send a fix prompt. Principles for writing prompts |
| Part of the AI's work log is in English | This is normal. Some lines of the work log appear in English | No action needed |
| You undid AI work with Ctrl+Z, but the game behaves the same | Ctrl+Z undoes only the changes the AI made to the scene, not the script files the AI edited | Restore the checkpoint from before the AI work, or fix the script by hand. Undo AI work |
network error appeared during AI work | The browser connection dropped (observed once) | Check your connection, then tell it to continue in the same conversation. When the AI stalls, stops short, or loops |
| You keep sending the same prompt | You're repeating the same sentence for a symptom that isn't getting fixed | Try different wording, and if it still doesn't work after three tries, fix a different symptom first. Failed prompts also use credits. Credits |
Running (Launch)
| Symptom | Cause | Fix |
|---|---|---|
| You typed a prompt, but the input box is empty and the viewport angle changed | What you typed while the AI panel was closed went to editor shortcuts (1 run). The AI icon opens and closes the panel each time you click it | Open the panel with AI, click the input box, and type again |
| You sent a prompt, but the AI doesn't start working | You haven't answered the 이대로 진행할까요? (Proceed as planned?) card | Find the card in the conversation and click 예 (Yes). Open the AI panel and send a prompt |
The AI only explained the cause and ended with 씬에 반영할 변경이 없습니다 (No changes to apply to the scene) | It used up the number of tool calls allowed in one prompt | Send "Fix it based on the cause you found. Leave everything else as is." Send fix prompts |
| The game tab is a black screen | It's loading | Wait about 10 seconds, and if it's still black, reload |
| The game doesn't respond to key presses | The game screen doesn't have focus. If the game rolls a ball, a short press may barely move it | Click the game screen once and hold the key for about 2 seconds |
| It says it's fixed, but the game hasn't changed | The game tab that was already open shows the state before the fix | Reload the game tab |
| You changed an attribute value, but nothing changed in the game | ① You didn't press Enter or Tab after typing ② Values read once at startup were applied on the second reload in some cases (2/2) ③ You edited the default: value in the code editor. The value in the entity's SCRIPT section takes precedence, so the change didn't reach the game | For ①, type it again and press Enter. For ②, reload once more. For ③, change the value in the entity's SCRIPT section. Change script attribute values |
| You edited the code, but nothing changed in the game | You didn't save in the code editor | Save with Ctrl+S, check that the bottom right shows 저장됨 (Saved), then reload the game tab. Code editor |
| The entity stays in place in the viewport but falls through the floor in the game | The viewport shows only placement; game behavior such as gravity and collisions happens in the game tab opened with Launch | Send a fix prompt describing exactly what you saw and the state you want. Send fix prompts |
| The game broke after you attached a script | The attached script may be the cause | First check by turning off the ON switch on that script's row. To remove it, use ··· → Remove Script on that row. Be careful: Remove Component in the header's ··· removes the whole component. Create and attach a new script |
| The game screen looks different from the description in the docs | A Launch run option may be on | Hover over ▶ Launch and check the Mini stats · Debug · Inspector checkboxes. Run with Launch |
| After a round ends, it doesn't start again | You didn't add a restart feature | Reload the game tab to start from the beginning |
Editor screen
| Symptom | Cause | Fix |
|---|---|---|
| Both side panels disappeared | Space was pressed. Typing while no input field is selected is handled as shortcuts | Press Space again, or click the hide-panels icon (four squares) in the top bar |
| You typed and all entities got selected | Ctrl+A was pressed outside an input field | When entering a value, click the field, confirm the value is selected, then type. Keyboard shortcuts |
| An entity doesn't show in HIERARCHY | It's inside a collapsed group entity | Expand the group with the + in front of it, or type the name in the Search field. HIERARCHY panel |
| The selected entity doesn't show in the viewport | The viewport camera is looking somewhere else | Press F to move the camera to the selected entity |
| The right panel shows SETTINGS instead of ENTITY | The selection was cleared. Clicking a highlighted row again deselects it | Click the entity in HIERARCHY again. Editor layout |
| You opened the project, but there are hardly any entities or a different game shows | A different scene is open | Click the scene name in the top bar and pick the scene you want in the SCENES window. Create and switch scenes |
| You pressed Enter after + New Scene and a different scene opened | You pressed Enter before the name field opened, so the scene selected in the list opened | Check that the name field has opened below the list (with Untitled selected), then type the name and press Enter. Create and switch scenes |
| The AI GAME BUILDER panel isn't visible | The panel is closed | Click AI near the bottom of the vertical toolbar on the left |
| Earlier AI conversations aren't visible | You clicked 새 대화 (New conversation), so a new conversation is open | Pick it from the conversation list at the top of the AI panel. The title is the beginning of that conversation's first prompt. If the list contains only 새 대화, reload the editor tab (observed once). Open the AI panel and send a prompt |
| You want to undo a value you changed by hand | — | Undo with Ctrl+Z (Cmd+Z on Mac). A Position changed by hand was reverted. Writing down the original value before changing it is safer |
| You're not sure whether your work was saved | Manual edits and AI edits are kept immediately without a separate save. A value stayed even when we reloaded right after changing it (1 run) | If you're worried, click Cloud Save in the bottom bar. Saved to cloud appears. Autosave |
| You wanted to change the color of one entity, but every entity with the same color changed | We confirmed that materials the AI creates (with names like Color E63946) are shared by entities of the same color (5 Enemy entities on one material) | Create a new material and assign it only to that entity. Change an entity's color |
| You clicked the ✕ in the material field and the entity didn't go back to its original color | ✕ clears the material (Empty) | Undo with Ctrl+Z. Change an entity's color |
| You changed the Text field of on-screen text, but the game shows the original text | A script overwrites the Text field at startup. The text lives in a script attribute (for example, scoreLabel) | Change the text in the SCRIPT section of the entity that handles the text. Attribute names differ from build to build. Change score and message text |
| You clicked a script file but don't know where to see the code | The code appears in the CODE section at the bottom of the right panel | Scroll down the right panel to CODE. To see it larger, click EDIT and the code editor opens in a new tab. Code editor |
| A newly created file doesn't show in the code editor | New files don't appear in a code editor tab that was already open | Reload the code editor tab. Code editor |
You set the type filter in ASSETS to Script, but only some scripts show | The filter applies only to the folder that is currently open. Scripts may be split between the root / and the Scripts folder | Move between folders in the folder tree to check. Editor layout |