Plan and test game mechanics

A mechanic needs an observable rule: an action, a change in state and feedback to the player. Before adding more systems, test whether the first action, win condition and restart work together. The existing guides below provide the starting workflow and debugging checks.

Open Mechanics collection ↗

Prepare a game for publishing

Publishing starts with a game that can be tested, understood and maintained. Check the available creator controls, audience settings and safety requirements before a release. Use the publishing guide for the sequence, and the troubleshooting guide for an actual blocked step.

Open Publish collection ↗

BC-0276 · TROUBLESHOOTING

Editorial review 2026-09-27

Roblox Build Game Was Removed

If a Build game was removed, preserve the moderation notice and identify the affected game, asset or account before changing anything. A missing search result alone is not removal evidence. Use the official review route offered for the actual action, and do not reupload unchanged material to evade it.

Symptom

A game or related content appears removed, with or without an actual moderation notice.

Immediate action

Preserve the notice and identify its affected object; if no notice exists, retain the observed absence without guessing a reason.

Diagnostic branches

A notice names a game, asset or account action.: Follow the scope and official options stated for that action.
Only search or recommendation absence is observed.: Use visibility diagnosis instead of assuming moderation.
The creator disputes an actual decision.: Use the official appeal guide with relevant evidence and no restoration promise.

Least-destructive change

Preserve the record and avoid evasive reuploads, replacement identities or unnecessary destructive changes.

Retest

The affected object matches the notice.
Absence without a notice is not labeled a proven moderation action.
A remediation edit is not presented as reversal of an account consequence.

Escalation

Use the notice's official review or assistance route and current eligibility terms. A guide cannot establish restoration, a deadline exception or permission to resubmit the same disallowed material.

Working notes

Separate confirmed moderation from unexplained absence. A notice naming an affected object establishes a different situation from an unavailable link or a missing recommendation. If no notice exists, record the actual destination error and investigate visibility without inventing a moderation reason.

Identify the scope precisely. Removal of a particular asset, action against a game and restriction of an account can require different next steps. Preserve the object identifier and the reason stated, but do not post personal account or identity information to a public guide or discussion.

Choose whether the next task is correcting identified content, requesting review of a decision, or clarifying an ambiguous notice. These can be related but are not interchangeable. A later content change does not itself establish that the original moderation action was reversed.

Keep the original evidence available when safe. Do not reproduce harmful material to build a test case, create replacement accounts or disguise the same content under a different name. Restoration and review outcomes remain unconfirmed until the official process provides a result.

Examples

Scope record: notice names an asset used by the game, while the game destination still exists. Investigate the named asset action instead of reporting deletion of the entire account.
Absence-only case: the game is not found through a particular search query, with no moderation notice. Begin with the known direct destination and visibility guidance rather than composing an appeal for an assumed removal.