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

Editorial review 2026-09-27

Published Game Title or Description Is Wrong

If a public title or description is wrong, compare the intended game, the value actually saved and the exact surface where the older or incorrect text appears. Also record the displayed language. A wrong game, an unsaved edit and a different localized presentation are different questions; do not rewrite the game to repair listing text.

Symptom

A public-facing title or description differs from the intended saved presentation.

Immediate action

Match the object, field, saved outcome, surface and displayed language before editing again.

Diagnostic branches

The object or field differs.: Correct the target selection without changing unrelated content.
The save was not acknowledged or returned a validation message.: Address the actual save outcome rather than assuming public propagation.
The language or presentation context differs.: Inspect available localization context and leave unverified causes unknown.

Least-destructive change

Correct the proven metadata mismatch while preserving accurate other-language text and working gameplay.

Retest

The compared destination is the intended object.
Typed text and confirmed saved value remain distinct.
The resulting description truthfully matches the game and no refresh interval is invented.

Escalation

Provide the exact field and matched-context discrepancy through official assistance if unresolved, excluding private account data.

Working notes

Identify the object and field before editing. A game listing, place label and in-game heading may use different text. Record the destination identifier and the exact field the creator intended to change. Similar names are not enough to prove the same object is being compared.

Inspect the current value through the authorized creator workflow actually available. Distinguish text typed into a field from an acknowledged saved value. Preserve any validation message and do not assume that leaving the screen saved the change. This guide does not supply a menu path that the account does not expose.

Compare the destination and displayed language where the discrepancy appears. If a localized value is involved, inspect the actual available localization information rather than assuming a cache fault or automatically replacing every language with the same text. If no such information is available, keep the localization hypothesis unconfirmed.

Correct inaccurate promises, stale names or wording that no longer matches the real game. Then record the actual save outcome and the relevant public observation. Do not stuff unrelated keywords, alter working gameplay or promise a fixed propagation time to solve a presentation mismatch.

Examples

Object mismatch: the creator edited a place label but expected the same value in a different game-listing field. Verify the intended field before another rename.
Language comparison: the creator's view uses different text and a different displayed language from the recipient's view. Record both facts; this is not enough to conclude that either value failed to save.