How to Read a Color Block Jam Checkpoint Table

What is a checkpoint?

A checkpoint is a visible state that lets you verify that your board still follows the source. On Level 275, the page pairs timestamped steps with a checkpoint table so the reader can confirm the route before committing to the next section.

Read each row as a verification stop, not as a new promise. The timestamp tells you where to pause, the state description tells you what to compare, and the next instruction tells you why that state matters. The Level 275 page is an existing example of this handoff between source frame and written explanation.

Which columns matter?

At minimum, use a timestamp, an observable board state, and the next route dependency. A note can also identify the source URL or a visible version context. Do not fill a missing cell with an inferred move. If the source never shows the state, mark it unknown and stop before presenting it as a verified checkpoint.

Table field	What to write	What to avoid
Timestamp	The source moment to pause	An approximate time with no visible state
Visible state	Blocks, doors, counters, or obstacles that matter	Hidden or guessed board facts
Next dependency	The move or route change that follows	A result outside the frame
Status	Match, mismatch, or unknown	“Probably correct” as a substitute for evidence

What should you compare?

Compare the blocks that matter to the next route, the gate or exit state, countdown values, and any revealed obstacle. You do not need to compare every pixel; compare the causal state that the next move depends on.

The official Rollic Help Center explains that updates can make a level look different from an older video. That is why a table should make its visible source date or version context clear when available. It still cannot prove which cause applies to one player’s board.

What if the checkpoint fails?

Return to the opening frame and locate the first divergence. If the initial board or source role is wrong, use Wrong Level. A checkpoint is a safety stop, not a reason to improvise an unsupported sequence.

Read the table as a sequence of verification stops, not as a guarantee that every board version is identical. The evidence is strongest when the timestamp, visible state, and next instruction all point to the same source frame.

How should you use a failed row?

Stop at the row, return to the last matching state, and identify the first difference. The video checkpoint guide covers when to pause, while Wrong Level covers how to report a board that no longer matches. Do not skip the row and continue with later instructions; later steps depend on the earlier state.

What makes a table trustworthy?

A trustworthy table is traceable, narrow, and honest about unknowns. It names the source, keeps timestamps next to claims, describes observable state, and says when the route is only source-linked. The source-backed method explains why a public link alone is not enough to publish a complete walkthrough.

If you are preparing notes for someone else, preserve the source timestamp exactly and use the same names for blocks, doors, and counters throughout the table. Consistent labels make it possible to compare two versions without accidentally treating a changed description as a changed board.