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

Editorial review 2026-09-27

Build Game Has Low Play-Through Rate

Before acting on a low play-through rate, identify the chart's exact metric, acquisition source, reporting window and eligible denominator. Then inspect whether the presentation accurately invites the intended player task. A rate change without comparable exposure is not proof that the title or thumbnail caused it.

Symptom

An available acquisition chart shows a play-through measure below the creator's expectation.

Immediate action

Record the metric definition, source, window and denominator before proposing a presentation change.

Diagnostic branches

The comparison mixes definitions or traffic sources.: Align those conditions or leave the comparison inconclusive.
Presentation makes a concrete inaccurate promise.: Correct the mismatch while preserving the game's actual task.
Evidence is sparse or unavailable.: Record the limitation instead of inventing a benchmark or claiming causality.

Least-destructive change

Change a supported presentation hypothesis without unrelated gameplay redesign or misleading click incentives.

Retest

The same metric and population are compared.
The listing remains faithful to the opening experience.
Observed rate movement is separated from an unproven causal explanation.

Escalation

Use official acquisition guidance for unclear chart definitions. No universal target rate, traffic gain or ranking outcome is supplied here.

Working notes

Read the definition attached to the actual chart. Play-through and qualified play-through should not be treated as interchangeable simply because their names are similar. Keep the numerator and denominator together; a count of plays without its corresponding exposure cannot establish the rate being discussed.

Compare like with like. A broader recommendation audience, a different traffic source or a changed window can alter the mix of people who see the game. Record those differences before attributing a movement to a recent image edit. If the relevant data is unavailable or too sparse for a useful comparison, label the conclusion inconclusive.

Audit the promise made by the title, image and first visible description against the actual opening task. Does the listing identify the real activity? Does the imagery suggest a mechanic that is absent? Correct a concrete mismatch rather than adding unrelated keywords or reward claims solely to attract more clicks.

If a presentation experiment is appropriate, state the specific expectation it changes and preserve truthful content. Record when and where the change applies. Evaluate the same metric and source afterward, including downstream player behavior where available; a more enticing but misleading promise is not a successful correction.

Examples

Definition mismatch: an image report uses qualified plays while another chart counts a broader play event. Do not combine the rates until their definitions and populations match.
Promise audit: the thumbnail emphasizes racing while the game actually opens as a delivery puzzle. Correct the expectation mismatch; do not claim that doing so has already improved the measured rate.