What to Do When a Color Block Jam Video Is Mislabeled

How do you spot a mislabeled source?

The title may name a nearby level, but the board is the stronger signal. Compare visible blocks, gates, countdowns, empty spaces, and first moves. The site’s troubleshooting page specifically recommends checking nearby levels when a mislabeled video or shifted sequence is possible.

Treat the title as a search hint, not as proof. First write down the level number shown in your game and pause on the source’s opening frame. Compare colors, shapes, empty lanes, exits, doors, and fixed obstacles before copying a move. Then compare the first demonstrated state change. If the opening board matches but the first move produces a different state, stop at that first divergence.

Why can a nearby number look plausible?

Level directories and videos often make adjacent numbers easy to discover, but discovery does not establish identity. The official Help Center notes that updates can make the same number look different from an older video. That is a documented possibility, not proof that a particular video is mislabeled. Keep the observed board difference separate from any explanation about versions, regions, devices, or tests.

Signal	Record	Stop when
In-game number	Number visible in the current game	It differs from the source context
Opening board	Colors, shapes, doors, exits, obstacles	Any material piece is different
First move	Resulting block and countdown state	The state cannot be reproduced
Version context	Visible source date or app version if available	The context is unknown and the board is uncertain

A safe nearby-level workflow

Open the range page for your current number, inspect adjacent guides, and compare each opening board. Keep the source URL with the page that matches rather than copying the title into a new claim.

Use the levels directory to reach the correct range, but keep numeric ownership on the exact /level/{number} route. The source-backed method gives the evidence ladder for deciding whether a public link is still only a lead. A nearby page can help you search; it cannot become your solution merely because the thumbnail looks familiar.

How should you report it?

Use the report instructions: include the guide page URL, current in-game number, visible version, and first visible difference. Avoid publishing personal account information in a screenshot.

If the opening board matches but a later checkpoint fails, report the first failed checkpoint rather than guessing a replacement move. That distinction helps editors separate a mislabeled source from a route that changed after an update.

What should you avoid?

Do not merge the first moves from one video with the ending from another, and do not “repair” a failed sequence by moving a block that the source never shows. Those choices create a new unverified route. A clean report is more useful than a confident theory: include the source URL, the current number, the first visible mismatch, and the timestamp where it appears. Leave out account names, player IDs, and private screenshots.

If the board matches at the start and the source later changes, note whether the divergence follows a move, a timer, or a newly revealed obstacle. That detail helps distinguish a recording gap from a different layout and gives the next reviewer a bounded question to answer.