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

Editorial review 2026-09-27 · Official sources conflict

Roblox Build Playtest Link Not Working

When a supplied Playtest link fails, first verify that the recipient received the actual complete destination and reached the intended project. Then separate a transport or destination error from a named account restriction. Do not guess an expiry period or bypass a notice by publishing more widely.

Symptom

A recipient has a purported test destination but cannot reach the intended playable session.

Immediate action

Compare the actual sent target with the available authorized destination and record the failure stage.

Diagnostic branches

The received target is incomplete or points elsewhere.: Correct the communication using the real destination without inventing a replacement URL.
The intended destination displays an access notice.: Preserve the notice and use recipient access guidance.
A game frame appears before a behavior fails.: Investigate gameplay rather than labeling the destination broken.

Least-destructive change

Correct only a proven destination mismatch; preserve game content and audience settings.

Retest

The target, not merely its display label, was compared.
No guessed link lifetime or cache delay is stated as a cause.
Private destinations and personal account details are not exposed in public evidence.

Escalation

Provide the observed destination-stage failure through an appropriate private official support route when unresolved; do not claim an expired link without actual evidence.

Working notes

Compare the destination provided by the authorized sharing interface with the message actually received. Formatting can leave punctuation attached, truncate a selection or present display text that differs from its target. Inspect the target without opening unrelated shortened or suspicious links, and never substitute a guessed project URL.

Record where the failure happens: before a Roblox destination opens, at an unexpected project, at an account notice, during loading, or after game entry. The same phrase 'link broken' hides different boundaries. An entered game with a rule defect is not a link-transport failure.

If the creator can still view the sharing destination, compare it with the sent one without assuming a regeneration or expiration feature. An observed difference is useful evidence; the age of a message by itself does not establish that the link expired. No universal link lifetime or propagation interval is confirmed here.

Keep any recipient-specific notice intact. Do not ask another person to lend an account, change their age inaccurately or defeat regional restrictions. If the destination is correct but entry is denied, route to legitimate recipient access rather than repeatedly changing the URL.

Examples

Transport example: the visible message label looks correct, but its actual target is another project. Correct the sent destination rather than modifying the intended game's controls.
Boundary example: the intended destination opens and shows an audience notice. The link reached its destination; access remains unresolved.
Report format: source destination verified privately / received target match or mismatch / last reached screen / exact notice / whether a game frame appeared. Do not publish the private destination in a public report.