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

Editorial review 2026-09-26

Score Does Not Update in Roblox Build

A score that does not update needs an event-to-score trace: what action qualifies, whether its prerequisite was met, what visible response followed and whether the displayed value changed. Test the scoring rule before redesigning the scoreboard. A stale label and an unrecognized scoring event require different repairs.

Symptom

The score display does not change as expected after an intended scoring event.

Immediate action

Write the qualifying event and compare its prerequisites with the action actually performed.

Diagnostic branches

The performed action does not satisfy the intended scoring rule.: Test the qualifying sequence before changing the scoreboard.
No visible event acknowledgement or score change occurs.: Request recognition of the valid event without guessing its internal wiring.
Other event feedback changes but score text does not.: Describe the display/feedback mismatch and request consistent visible state.
A repair awards again on invalid repeat contact.: Restore the consumed-event guard before adding more scoring features.

Least-destructive change

Correct event qualification and visible feedback without altering reward amounts or unrelated progression.

Retest

A valid scoring sequence changes the displayed value by the intended design amount.
An invalid approach and repeated consumed event do not award.
The next attempt begins with the score state defined for that round.

Escalation

Preserve the qualifying-action trace and before/after display values if a scoped repair fails. A screenshot of an unchanged number alone cannot identify a storage, networking or script cause.

Working notes

State the scoring event precisely. Touching an item, picking it up and delivering it to a destination are different candidate rules. Compare the written intention with the actual sequence you performed. If points are meant to arrive on delivery, carrying an item alone is not a failed score update.

Record the displayed value before the event and after its visible response settles. Note any pickup disappearance, deposit feedback or progression effect without treating those signs as access to hidden score state. If a goal condition appears to respond while the label stays unchanged, describe that discrepancy rather than asserting the internal value is correct.

Check an action that should not qualify, such as approaching a delivery point empty or revisiting an already consumed collectible. This protects the repair from simply awarding points on every contact. Do not use a paid purchase or real-money reward to test a basic score label.

Ask for the intended qualifying event, its visible update and its duplicate guard together. Preserve the amount already specified by the design; changing the reward size while repairing event recognition makes the comparison ambiguous. Finally inspect the intended round-start score so a successful award is not confused with stale progress from the previous attempt.

Examples

Scoring rule example: points are awarded when a carried parcel is deposited, not when the depot is touched empty. The trace records carrying state, deposit feedback and displayed score change separately.
Proposed correction: Update the visible score when a valid parcel delivery completes. Empty visits and continued contact after that delivery must not award again. Keep the existing score amount and movement rules.
Mismatch record: valid event appears acknowledged, progress feedback changes, but score text stays unchanged. Report the visible disagreement; do not claim that the hidden counter definitely updated.