Step 1: Open Build

Open the Build tab inside the Roblox app on an eligible Android mobile device. If the tab is absent, check region, age, age check and platform access before starting.

Step 2: Describe one game loop

State what the player does repeatedly and how they know they are making progress. An original starting example:

Create a compact sky garden game. The player collects five floating seeds, returns them to a planter and earns one growth point. Show the seed count and growth points. Restart the loop when the garden blooms.

This gives Build a goal, loop, setting and visible progress without asking for an entire large game at once.

Step 3: Let Build generate

Wait for the first playable result. If generation stops before it is complete, type please continue, as Roblox Support recommends.

Avoid sending a second design request before the first state is testable.

Step 4: Playtest before changing

Run the game and test the core loop:

  • Can the player understand the goal?
  • Does the main interaction work?
  • Can the player win, score or progress?
  • Is the interface readable?
  • Can the loop restart cleanly?

Playing and playtesting do not use the daily AI allowance.

Step 5: Refine through chat

Ask for one observable change, such as “Keep collected seeds after the player returns to the planter and update the counter immediately.” Then test that change before requesting another.

Use the Build prompt framework when a revision involves controls, progression, interface or difficulty.

Step 6: Share privately

Use Share → Get Playtest Link to invite private feedback before publishing. Give testers one question to answer, such as whether the goal was clear without instructions.

Step 7: Publish deliberately

Review the full loop and use Publish. Build performs a safety check, and newly published Build games initially target age-checked players age 16 or older, with regional exceptions. Read the publishing guide before release.

Common problems

  • First prompt is too broad: reduce it to one small loop and one win condition.
  • Generation pauses: type please continue.
  • A revision breaks another part: name the behavior to preserve in the next focused request.
  • AI usage is low: playtest first; testing does not consume the allowance.