Make your first game

In this tutorial, you use AI GAME BUILDER to make a game where you roll a ball to collect 10 stars. Then you play it yourself with Launch, have the AI fix the defects you find, and change the ball's look with a model from the asset store. By the end, you'll have gone once through the basic OasisW workflow: "build with the AI → check it yourself → fix → polish."

It takes 40 to 60 minutes. Most of that is waiting for the AI to work. You send 4 to 6 AI requests.

Before you start

• You must be signed in. See Sign in and create an account.
• Each AI request uses credits. Failed requests also use credits. For details, see Credits.
• Keep the editor tab open until you finish.

1Create a new project

1. On the dashboard, click New project.
2. Make sure Blank project is selected. Enter star-game in Project name, and choose Private under Visibility.
3. Click Create and open editor. The editor opens in a new tab and the SCENES window appears.
4. In the SCENES window, click the star-game scene.

2Have the AI build the game

1. Click the AI icon near the bottom of the vertical toolbar on the left. The AI GAME BUILDER panel opens where the right panel is. You can also click the AI button floating at the bottom right of the viewport.
2. In the 만들고 싶은 게임을 설명하세요 (Describe the game you want to make) input box at the bottom of the panel, enter the following prompt exactly.

PromptCopy

Make a game where you roll a ball on the ground to collect 10 yellow stars. The ball rolls with the arrow keys. When the ball touches a star, the star disappears and the collected count on the screen goes up. The game ends when all 10 are collected. Name the ball Ball, and name the stars Star1 through Star10.

3. Click 보내기 (Send). The button changes to 중단 (Stop), and AI가 생각하는 중 (AI is thinking) appears.
4. After 20 to 30 seconds, an 이대로 진행할까요? (Proceed as planned?) card appears. Sometimes the AI shows what it will build as a plan (1 of 2 runs), and sometimes only the question appears. Click 예 (Yes). The work doesn't start until you answer this card.
5. Wait until the button changes back to 보내기. In our tests, it took 10 to 12 minutes after clicking 예.

While you wait, the following appear in the AI panel in order.

• [확인] 예 ([Confirm] Yes) — the record of your answer to the plan
• 기획 체크 5개 · 단계 3개 (5 design checks · 3 steps) — how many steps the work was split into. Step names (for example, 단계 1/3 · 핵심 플레이 (Step 1/3 · Core gameplay)) varied from run to run
• Work lines such as Ball 생성 (Ball created), Ball ← 레시피 player_controller (Ball ← recipe player_controller), and 게임 실행 3초 (Ran the game for 3 seconds) — one line for each thing the AI did
• Progress lines such as AI가 작업하는 중 · 단계 2/3 경기장과 환경 · 도구 96회 · 4분 53초 (AI is working · Step 2/3 Arena and environment · 96 tool calls · 4 min 53 s)
• A summary at the end of each step, and an 자동 점검: … (Auto check: …) line. English lines starting with Visual check: are problems the AI found by looking at the game screen. The AI sometimes fixes these problems on its own

While the AI is working, HIERARCHY and the viewport don't change. When the work finishes, the AI's changes are applied to the scene all at once, and a 씬에 반영했습니다 · 엔티티 N개 추가 · … (Applied to the scene · N entities added · …) line appears. For what each line means, see Read the plan and work steps.

In both test runs, the work ended with 문제 1건 남음 (1 issue remaining) or 문제 2건 남음 (2 issues remaining), and 2-1 was needed.

2-1If it isn't finished, have it continue

Don't start over. In the same conversation, send whichever of the following prompts fits.

If the 이대로 진행할까요? card appears for this request too, click 예. In our tests, this took 6 and 11 minutes. One run ended with 문제 없음 (no issues), and in the other, 문제 1건 남음 remained. You can have it continue once more, but it's faster to check yourself in step 3 whether the remaining problem actually shows up in the game. For detailed guidance, see When the AI stalls, stops short, or loops.

3Play it yourself with Launch

1. Click ▶ Launch at the right of the top bar. You can click it with the AI panel still open. The game opens in a new tab.
2. Click the game screen once, then hold down an arrow key. The ball rolls. Short taps barely move it.
3. Touch a star, and collect all of them.
4. Write down anything odd, exactly as you see it.

• The ball rolls with the arrow keys
• When the ball touches a star, the star disappears and the on-screen count goes up by 1
• When all 10 are collected, a game-over message appears (it doesn't appear at the start)

Check these three things yourself even if the AI's last line is 문제 없음. In both test runs, the first version had 2 defects.

A fence or walls around the edge that you didn't ask for appeared in both runs, and trees appeared in 1 run. These aren't defects, so you can leave them. On-screen text was Korean in one run (별: 0 / 10 (Stars: 0 / 10)) and English in the other (Stars: 0 / 10).

4Have the AI fix the defects you found

Go back to the editor tab. The conversation that built the game is still open in the AI panel. Send the defects you noted as a numbered list. Don't guess at causes; describe only what you saw.

This is the prompt actually sent in our test. Replace the text in quotation marks with the text you see on your screen.

PromptCopy

I ran it with Launch, and two things are wrong.1. When the ball touches a star, the star disappears, but the number in "Stars: 0 / 10" doesn't go up from 0.2. As soon as the game starts, the top right shows "Stars left 9." There are 10 stars.Fix only these two things and leave everything else as it is.

To start a new line in the input box, press Shift+Enter. Pressing Enter alone sends the prompt right away. If the 이대로 진행할까요? card appears, click 예.

The test results were as follows.

The last line may be 문제 없음 or 문제 N건 남음. Run 2 ended with 문제 2건 남음, but the remaining problems concerned an unused script file, and the game worked correctly. Either way, you only know whether it's fixed by running it yourself.

When it's done, refresh the game tab and check the three things from step 3 again from the start. If you don't refresh, you still see the game from before the fix. Don't check only the fixed parts: sometimes something you thought was fixed is unchanged, or something else breaks.

4-1If it only found the causes, ask it again to fix them

Sometimes the AI explains the causes, writes something like "the fix hasn't been applied yet (tool call limit reached)," and the last line is 씬에 반영할 변경이 없습니다 (No changes to apply to the scene) (1 of 2 runs). In that case, nothing in the game has changed. Send the following prompt in the same conversation.

PromptCopy

Fix the two things based on the causes you found. Leave everything else as it is.

In our test, this request took about 5 minutes 30 seconds.

4-2Resend only what still doesn't work

If something still doesn't work when you run the game again, describe only that and send it. This is the prompt actually sent for run 1 above.

PromptCopy

I ran it again after the fix. "Stars left" now starts at 10 and goes down each time I collect a star. But even after collecting 7 stars, the number in "Stars: 0 / 10" at the top left still doesn't go up from 0.Fix only this and leave everything else as it is.

This request took about 3 minutes, and the score was fixed so it goes up (1 run). The AI again wrote that it stopped at the tool call limit and couldn't verify the fix itself, but when we ran the game, it was fixed. To find out what changed, see Check what the AI changed. For the prompt format, see Send fix prompts.

5Replace the ball with an asset store model

5-1Get the model

1. Click ASSET STORE at the right end of the ASSETS bar at the bottom. You can click it with the AI panel still open. The ASSET STORE window opens.
2. Enter ball in the search box at the top.
3. Click cannon-ball. The view changes to the detail screen, and the pack (Pirate Kit), size, dimensions, and license (CC0) appear below the preview.
4. Click IMPORT at the top right. The window closes, and cannon-ball.glb appears in the Store ▸ Pirate Kit folder in ASSETS.

For how to search and filter the store, and how to place an imported model in the scene manually, see Get models from the Asset Store.

5-2Have the AI make the change

1. Check that the same conversation is open in the AI panel.
2. Send the following prompt.

PromptCopy

Change the look of the ball (Ball) to the cannon-ball model I just imported from the asset store. Keep the arrow-key rolling controls and the star-collecting rules as they are.

3. On the 이대로 진행할까요? card, click 예.
4. Wait until the button changes back to 보내기. In 2 test runs, it took 7 and 6 minutes.

In both test runs, the ball changed to the dark gray cannon-ball model, and the controls and star-collecting rules still worked. However, even with "keep … as they are" in the prompt, the AI touched other things. In one run, the auto check rewrote a score script that was already working; in the other, it deleted stars collected during a test run and then recreated them. That's why you check everything again from the start in step 6.

6Final check

1. Refresh the game tab.
2. Check the three things from step 3 again from the start. Confirm that only the ball's look changed and the controls and rules are the same.

If all of this works, your first game is complete. You don't click a save button. The AI's changes remained after a refresh once they were applied to the scene, and a Position value changed manually also remained after a refresh (1 run). For details, see Autosave.

Troubleshooting

Next steps

• Check what the AI changed
• Send fix prompts
• Editor layout