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

Editorial review 2026-09-27

Build Game Is Not in Home Recommendations

Not seeing a Build game on your own Home page is not evidence that it is absent from everyone's recommendations. First verify publication and eligible access, then inspect any actual acquisition data available for the game. Separate no observed exposure from weak response to exposure; neither is fixed by a promised AI ranking boost.

Symptom

The creator cannot observe expected recommendation exposure for a published game.

Immediate action

Separate personal Home observation, direct access and source-specific acquisition evidence.

Diagnostic branches

Publication or eligible entry is unconfirmed.: Resolve that boundary before investigating recommendation response.
Relevant exposure data is unavailable.: Keep distribution unknown rather than asserting zero reach.
Comparable exposure exists but response is weak.: Inspect truthful presentation and the relevant player task without inventing a ranking formula.

Least-destructive change

Improve an evidenced problem without artificial traffic, copied metadata or repeated reuploads.

Retest

The acquisition source and time window are consistent.
A personal feed is not used as a universal distribution audit.
Game quality observations and reach outcomes are reported separately.

Escalation

Use official discovery guidance and any actual dashboard quality notice for the next step. No specific placement, traffic volume or ranking improvement is promised.

Working notes

Begin with the correct surface. A working direct destination, a search result and a Home recommendation are different observations. Personal recommendations are not a universal catalog, so an individual viewer's screen cannot establish the game's total distribution.

Where authorized analytics are available, compare the same acquisition source and reporting window. Missing data, no measured impressions and impressions without resulting plays are different states. Do not fill an unavailable dashboard with invented numbers or use total visits as a substitute for Home-specific behavior.

Review truthful presentation and the actual player experience before changing promotion. A mismatch between the thumbnail's promise and the opening game can be investigated without claiming to know a private ranking weight. Existing official discovery guidance describes signals and opportunities, not a deterministic distribution switch.

Choose a bounded next action from the evidence: resolve an access problem, correct misleading metadata, inspect an opening obstacle or gather adequate comparable observations. Do not buy artificial engagement, copy another game's identity or repeatedly republish to simulate activity. A revision may improve the game without producing measurable reach yet.

Examples

Evidence distinction: the creator does not see the game on their own Home page, but no Home acquisition data is available. The total exposure conclusion is unknown.
Different problem: Home impressions exist for a comparable window, but the displayed promise does not match the game's actual opening task. Investigate that mismatch without declaring it the sole ranking cause.