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-0283 · TROUBLESHOOTING

Editorial review 2026-09-27

Why Roblox Asks for a Content Questionnaire

Automatic Moderate rating: Support separately says changes beyond prompting—such as adding custom code—can remove the automatic rating and require the content/maturity questionnaire. Merely viewing an editor is not evidence of a change. When the questionnaire is required, inspect the actual current content and use official definitions rather than choosing answers for a desired audience.

Symptom

The creator is asked to supply content information and is unsure what evidence should support the responses.

Immediate action

Inspect the current experience and connect responses to actual content and official definitions.

Diagnostic branches

A relevant content path has not been inspected.: Keep the local review incomplete instead of treating unseen content as absent.
A definition is unclear.: Consult official guidance rather than guessing the answer that produces a desired audience.
Content changed after an earlier review.: Reassess the affected answers for the actual new candidate.

Least-destructive change

Resolve review gaps truthfully without deleting unrelated work or misrepresenting the experience.

Retest

Responses correspond to the inspected candidate.
Optional reachable content is not omitted merely because it is not in the opening.
A maturity category is not described as an exemption from content policy.

Escalation

Use official maturity and policy guidance when a question remains unclear. The local worksheet does not determine eligibility, replace the platform's form or authorize prohibited content.

Working notes

Start with the actual candidate, not only its original brief. Generated output, later dialogue, added assets and optional interactions can differ from the concept initially requested. Build a review inventory that includes paths a normal player can reach, not just the opening scene.

For each relevant question, connect the answer to a concrete content observation and the official definition. A missing inspection is not evidence of absence. If a branch is unavailable or a feature is not yet understood, mark the local review incomplete and resolve it before asserting an answer.

Distinguish content classification from a judgment that prohibited material is permitted. Choosing a maturity label does not override Community Standards or make a refused interaction acceptable. Review the substance of the experience and use the official policy or notice for an issue outside ordinary classification.

After a substantive content change, check whether the earlier review still describes the current candidate and follow the platform's applicable update instructions. Keep version, inspected surfaces and unresolved questions together so a later edit does not silently inherit stale answers.

Examples

Inspection gap: the opening scene is benign, but an optional generated dialogue path has not been read. Do not use the opening alone as evidence about all dialogue.
Evidence row: relevant question / actual content and reachable context / official definition consulted / answer supported or review incomplete / candidate version. This is a local review aid, not an alternative official form.