Step 1: Open Build

Open the Build tab on an eligible account and device. Android/iOS remain in Support’s checklist; RDC now announces desktop expansion, with Mac separately named in Support. Check desktop status and region, age and age check before treating a missing tab as an error.

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.

Keep the first concept within the simpler formats Creator Hub currently recommends. If the idea depends on full 3D generation, review the current 3D support status before committing to the scope because Roblox’s official pages do not yet agree.

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

Use the controls available to your account. Creator Hub includes a coming-soon notice alongside testing instructions, while Support describes Playtest as a current step. The playtest status page preserves that conflict; do not assume every account has private sharing.

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

Use the prompt builder to preserve a clear brief and the iterative-control guide to separate a mechanical change from a visual one. RDC's asset and scene announcements are not a reason to enlarge the first game before its loop works.

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.

If the generation stops, follow the please continue recovery. If it finishes with the wrong behavior, use the bad-generation repair loop. The game-types guide helps reduce an over-broad concept before the first prompt.