How sent messages count

Roblox Creator Hub currently defines every message sent to Build as one prompt, including follow-up changes. Roblox Support describes the same messages as consuming part of the account’s daily AI allowance.

In practice, assume every AI instruction consumes usage. Playing the game and running playtests remain separate and do not use the allowance. The playtest guide explains how to separate testing from revisions.

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. Start with the creation workflow, then use the prompt framework to make each iteration testable.

Reset and unfinished generations

Free prompts reset daily. Roblox does not publish one universal reset clock or prompt count in the reviewed official pages, so use the in-app usage display as the account-specific source of truth.

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.

That allowance-exhaustion statement is not a guarantee against unrelated generation failures. Record an actual stopped response separately instead of treating it as proof that the daily allowance changed.

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 official pages.
  • 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.

If the visible problem is an unfinished response rather than the allowance display, use the generation-stuck recovery steps first.

Keep a usage activity record

Illustrative record to fill, not an account test we performed: current allowance label and state—copy if shown; intended change—restore the missing parcel on retry; action—drafted locally, sent, or inspected; observed display afterward—leave blank until seen; next decision—inspect again, revise, or wait. Do not assign a purchase price or message count to an unlabeled progress bar.

Before another instruction, retry after collecting the parcel and note whether it returns, whether carrying clears and whether completion becomes active again. This checks the requested game behavior; it is not a paid experiment to infer charging. Keep any observed allowance change separate from the gameplay result, and do not send a new message merely to fill a missing measurement.