How to make a game with AI

1How to make a game with AI: start with a small loop

Keep the first brief small enough to play in one sitting. State three things in player language:

• Goal. What is the player trying to do?
• Action. What does the player repeat?
• Ending. What stops the round?

Add the controls and one progress signal, such as a score or timer. Save extra characters, levels, and menus for a later request. The first playtest should answer one question: can a player understand and repeat the main action?

2Create the first version in ShortGame

This is the original prompt used for the Star Catcher case:

Make a small keyboard game called Star Catcher. The player moves a basket left and right with arrow keys to catch 10 falling stars. Show a score, a 60-second timer, a clear win screen when all 10 stars are caught, a lose screen when time runs out, and a Restart button.

Follow the actual creation path:

1. 1From the homepage, paste the prompt above into the game idea box, then select Start creating.
2. 2If you are not signed in, sign in to continue.
3. 3On the create page, check the prompt and model, then select Create game.
4. 4When the editor is ready, open Preview to start the first playtest.

If the create page says Add credits to create this game, the prompt stays in place so you can add credits and retry.

3Play the first version before you polish it

Play the round as a new player. For Star Catcher, move the basket with the arrow keys and catch falling stars before the timer runs out. Check that the control responds, the instructions are easy to follow, the score or timer updates, and the round reaches an ending you can understand.

In the recorded round, the timer ended before the requested win state appeared. Treat that as a reason to inspect the first version, not as proof that every requested outcome works on the first try.

4Ask for one focused change

Turn one observation from the first round into one request. Keep the player action and timer unchanged when they are already useful; that makes the next playtest easier to compare.

Note on the recorded follow-up: it asked, “Make the moving star easier to see and add a clear win message after 10 successful taps.” Star Catcher used a basket and arrow keys, so “taps” did not describe the observed control. That sentence records the request; it is not a recommended prompt for this game.

Suggested edit (not the request used in this example)

Make the falling stars larger and easier to see. Keep the basket, arrow-key controls, objective, and timer unchanged.

5Play again, then check the player view

Run the same controls again, starting with the change you requested. Then check the requested change, the controls, and whether the round makes sense from start to finish. If the updated version is clear to someone who did not write the prompt, it is ready for a player-facing check.

The Star Catcher case stayed in a local creation workspace and was not published as a public game. Browse Play to see how other public games present their player view. When your own game is ready, use its existing Share control in the creation flow.

Common questions