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

Editorial review 2026-09-27

Build Status Was Lost After Studio Edit

If an edited version has lost Build status, separate continuing that Studio version from trying to recreate a concept through retained prompt history. The documented handoff is not a reversible advanced mode. Preserve the current artifact and decide which work matters before starting a separate recreation that may produce a different result.

Symptom

The creator expects a Studio-edited version to regain the earlier Build workflow.

Immediate action

Preserve the edited artifact and distinguish continuing it from recreating a concept from retained instructions.

Diagnostic branches

Important manual work exists only in the edited version.: Account for that work before choosing recreation; do not assume prompt history contains it.
The creator wants a new prompt-driven interpretation.: Treat it as a separate candidate requiring inspection, not restored state.
It is unclear whether an actual edit occurred.: Establish the version and change history before asserting the handoff consequence.

Least-destructive change

Keep the current useful artifact and avoid an invented conversion or rollback command.

Retest

Recreation is not described as reversing the edited version's handoff.
Manual changes and generated instructions are distinguished.
A new result receives new tests rather than inherited approval.

Escalation

Use the Studio handoff guide for the documented boundary and official assistance for an actual unexplained status notice. No exact restoration or conversion service is offered here.

Working notes

Establish the actual edit and version involved. Merely remembering that Studio was opened is not a precise change record. Keep the current edited artifact identified, along with the working behavior and manual changes you would lose by starting elsewhere.

Creator Hub states that prompt history is retained after editing a Build game in Studio; retained text is not a promise of exact-state restoration.

Compare continuation and recreation as different projects of work. Continuing preserves the existing edited result but uses its current workflow. Recreation starts from instructions and must be inspected as a new result; a similar prompt is not a backup of every asset, state, fix or manual adjustment.

Before deciding, inventory the parts you need to preserve and how each reached the current project. If an essential behavior only exists in the edited version, a recreation plan must account for rebuilding and testing it rather than assuming it returns automatically. Do not discard the working artifact merely to chase a familiar label.

Examples

Decision record: valuable manual route fix exists only in the current Studio version; retained prompts describe the earlier layout. Recreating from those prompts would not by itself preserve the route fix.
Comparison outcome: the creator chooses to continue the working Studio version because exact manual behavior matters more than returning to prompt-only editing. This is an editorial tradeoff, not an account capability claim.