What counts as AI usage

Each message or requested change made through Build’s AI workflow uses part of the daily allowance. That includes generation and prompt-based revisions.

Playing the game and running playtests do not use the allowance. Use that distinction to test thoroughly before spending another AI change on a revision.

A usage-aware workflow

  1. Describe one small, complete core loop.
  2. Let the first generation finish.
  3. Playtest without spending additional AI usage.
  4. Write down the highest-impact issue.
  5. Request one focused change.
  6. Playtest again before sending another message.

Bundling unrelated revisions into a vague prompt makes it harder to tell which change worked. The prompt framework helps make each iteration testable.

Reset and unfinished generations

The daily allowance resets the next day. Roblox does not state one universal reset clock or prompt count on the current Support page, so use the status shown in Build for the account’s current usage.

If usage runs out while a game is already generating, Roblox says the current generation finishes. If generation stops before completing for another reason, Roblox Support recommends typing please continue when AI usage is available.

When the free allowance is gone

Creators can wait for the next reset or, when eligible, purchase extra usage with Robux. Automatic top-ups and a daily spend limit are available. Review the Robux top-up guide before enabling automatic spending.

Common problems

  • A playtest appears to reduce usage: Roblox says playtesting itself does not; check whether an AI change was sent.
  • A precise daily count appears elsewhere: Roblox has not documented a universal count in the reviewed Support page.
  • The allowance ends mid-generation: the active generation should finish.
  • Usage is empty but the game needs testing: continue to playtest; save AI usage for the revision.