Before tapping Publish
When a legitimate testing path is present, complete a final gameplay inspection and verify:
- The player can understand the goal.
- The core loop begins, progresses and ends correctly.
- Controls and interface labels are readable.
- The game contains no disallowed or unintended content.
- If a legitimate private-testing path is available to the intended account and tester, observe whether they can complete the main loop without creator guidance. Otherwise mark external feedback not checked; do not claim a creator-only run proves newcomer understanding.
A private playtest link is appropriate only after observing sharing controls and authorized recipient entry. Official Playtest wording conflicts. Do not invent another external-testing route or broaden the audience to bypass that restriction; keep the current legitimate audience controls and the untested coverage visible in the release decision.
Publish and safety check
Tap Publish. Build performs a quick safety check before release. If the check identifies an issue, follow the Build won’t publish checklist, revise the game through Build chat and try again; do not look for a moderation bypass.
After publishing, Roblox says the game appears on the creator’s profile.
Initial audience
Source check needed for build.audience. The supporting documentation has not been verified within its review window. Consult the current official sources before relying on this rule.
Source check needed for publishing.select-entry. The supporting documentation has not been verified within its review window. Consult the current official sources before relying on this rule.
Build games remain unavailable to Roblox Kids ages 5–8. The audience and Roblox Select guide explains the entry benchmark, the unverified general maintenance claim and fee-specific refund conditions, and where to check progress.
Discovery without guarantees
Roblox Support describes capturing gameplay during playtesting for Moments. This does not guarantee access to a particular capture control or distribution surface for every account. Creator Hub's video-thumbnail guidance says approved authentic gameplay videos appear on a game's detail page and may also appear on Home. Approval is not a promise of Home placement. Current discovery guidance describes engagement and retention signals in Roblox's recommendation system. The discovery guide explains the signals and upload boundaries.
Roblox's July launch announcement states that Build games join the same candidate pool and retention-based discovery system as other games. That dated statement is not a promised ranking result for this release.
There is no guarantee of placement, traffic level or ranking benefit for AI-generated content. Design for a clear first session and improve the game from real playtest feedback.
Broader younger-audience publishing requirements
Source check needed for publishing.account. The supporting documentation has not been verified within its review window. Consult the current official sources before relying on this rule.
Source check needed for publishing.refund. The supporting documentation has not been verified within its review window. Consult the current official sources before relying on this rule.
Source check needed for publishing.maintenance. The supporting documentation has not been verified within its review window. Consult the current official sources before relying on this rule.
Build games still cannot reach Kids ages 5–8 by paying that fee. Read the audience and Select guide for the entry/refund distinction and media-feed restriction.
An earlier RDC roadmap reference described a November reduction to 100 HEP. Its DevForum body could not be reverified on September 26; this dated announcement is not a current rule. Use the current entry documentation and Audience Reach.
Use the launch checklist to prepare the current release and the monetization hub for optional earning methods.
Common problems
- Safety check fails: use the reason shown to revise and retry.
- The game is not visible to younger players: the initial audience is age-checked 16+, subject to regional exceptions.
- Discovery is low: do not assume a ranking benefit; focus on player experience rather than repeated low-quality generation.
- Studio edits changed the rating flow: complete the required content and maturity questionnaire.
After release, continue with the Build-chat update workflow. Use Creator Analytics to distinguish low discovery, early bounce and weak repeat play before choosing the next update.
Record the actual release outcome
Illustrative release record, not a publication we performed: intended version—delivery-feedback revision; core loop inspection—record actual result; external feedback—not checked unless legitimately completed; Publish response—copy only after the action; player-facing destination and version—unconfirmed until inspected; audience restriction—record from the actual flow. A successful editor preview cannot fill the public-version field.
After a reported publication, inspect the intended destination through an eligible path and compare its opening goal, completion cue and retry with the release candidate. If the destination, version or audience differs, retain the discrepancy and investigate without repeatedly publishing or widening access as a test. Keep a displayed safety failure separate from an unobserved discovery outcome.