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-0115 · CORE GUIDE

Editorial review 2026-09-26

Roblox Build and Gameplay Videos

A gameplay video demonstrates an existing Build-origin game; it does not generate the game or expand its audience permissions. Creator Hub's video-thumbnail instructions use the selected game's place and its Videos panel in Creator Dashboard. Use authentic footage and check the current rules before submission.

Objective

Create a truthful footage-to-game and submission record for a gameplay video.

Before you start

Have the actual game version represented by the footage.
Confirm the selected game's management permissions.
Review current video-specific policy and rights requirements.

Steps

Match each featured action to the current playable version.
Review edits for changes to the apparent mechanics or visual quality.
Check audio, text and external material against the current documentation.
Select the correct game and place in the documented upload workflow.
Record the actual submission and moderation state without promising reach.

Verification

The clip's main behavior can be demonstrated in the named version.
The upload targets the intended place rather than a similarly named project.
A pending submission is not labelled approved.
Possible distribution remains distinct from observed Home placement.

Limitations

This page does not upload or moderate the video.
General video-asset APIs are not interchangeable with this thumbnail workflow.
A promotional asset does not change the game's publishing or audience requirements.

Working notes

Begin with a footage-to-game comparison. Name the action shown, locate it in the current playable version and record whether the outcome can actually be reached. This catches a promotional clip that still shows a feature removed during the latest revision.

Follow the current video-thumbnail documentation for upload and moderation. The documented route is the selected game, Configure, Places, the chosen place and Videos. Approved video placement on the detail page is distinct from possible Home distribution; submission does not establish future discovery.

Authenticity does not require a blanket ban on all editing. Current guidance permits faithful camera work and limited contextual presentation while prohibiting misleading gameplay. Read the detailed audio, text and external-content rules before finalizing the clip rather than copying a stricter or looser rule from an older announcement.

Keep the video job separate from Moments. This guide's output is a promotion-ready evidence and submission record for the documented video-thumbnail workflow. The Moments guide addresses its own capture-and-sharing path. Neither path substitutes for publishing the playable game or checking its audience status.

Examples

Footage check: the clip shows a bridge opening after delivery; the current game opens the same bridge after the same action. Record the version checked and retain the unedited sequence for your own comparison.
Reject this edit: an animated overlay depicts a combat ability that the playable game does not contain. Better camera framing cannot turn an absent mechanic into authentic gameplay.
Submission record: selected game and place / footage version / behavior checked / rights and policy review / upload state / moderation message / observed placement. Keep pending review distinct from an approved asset or observed distribution.