Color Block Jam Screenshot Guide: Capture the Useful Board State

What should a useful Color Block Jam screenshot include?

A useful screenshot answers one question: which board state am I looking at? To do that, it needs the level number and the whole board in the same frame, not just the block that looks wrong. Include every destination, exit, key, gate, and obstacle that a move could affect, because a cropped block without its destination can make two different puzzles look identical.

Capture	Why it matters
Level number	Ties the image to one board instead of a nearby level
Full board	Shows blocks, destinations, keys, gates, and obstacles together
The first mismatch	Records the earliest visible difference, not a later guess
Visible counter or timer	Explains what the state depends on at that moment
The source you compared	Keeps the screenshot connected to one guide or video

Rollic’s official My Level Is Different from YouTube / Videos article explains that an update can make a level look or play differently from an older video. That is exactly why the number and the full board belong together in one image: the number names the level, and the board shows which version of it you are actually facing. Rollic’s Obstacles in Color Block Jam article adds a second reason to keep the frame wide, since arrows, chains, ropes, and changing doors can decide whether a route is even open.

When should you capture the board instead of waiting?

Capture at the first mismatch, not at the final failed state. If you wait until the board is scrambled, the screenshot shows the result of several moves and hides the single change that started the problem. The earliest difference is the most useful one because later differences are often consequences of it.

The same rule applies when you check a walkthrough before you follow it. Take one screenshot of the opening board and one after the first meaningful checkpoint. Those two frames let you compare a guide against your puzzle without recording every tap, and they give you a clear point to stop if the boards diverge.

How do you keep a screenshot safe to share?

Treat every screenshot as something that may leave your device. Keep the board and crop out anything that is not part of the puzzle. Notifications, account names, chat previews, and device status bars do not help anyone read the board, and they can carry information you did not mean to share.

A quick safe-share order:

1. Capture the full board first, before cropping anything.
2. Confirm the level number is readable.
3. Crop the edges, not the middle of the board.
4. Check the result at phone size to be sure the details still read.
5. Store the original until the issue is resolved.

What should you leave out of the frame?

Leave out personal information and anything that changes what the board appears to be. Do not crop a block away from its destination, and do not rotate or stretch the image, because that makes a real difference harder to confirm. Keep the screenshot honest: show the board as it appears, with no marks that suggest a move you have not made.

If you want to add labels, add them on a separate copy rather than editing the screenshot itself. That keeps the original evidence clean and the explanation clearly separate from it, which matters when someone else has to re-check your board.

How do you turn a screenshot into a mismatch record?

Pair the screenshot with a short written note so the image stays useful after you close the game. Name the level, the source you compared, the first visible difference, and the time you checked it. A screenshot without that context is hard to revisit, and an editor cannot tell which board it belongs to.

The board-match workflow and the first-mismatch log both use the same idea: record the earliest observable difference, then stop. If you need to label a route on top of the image, do it in a separate board annotation and keep the untouched screenshot beside it. When several boards share similar colors, compare structural landmarks instead of color alone.

A screenshot proves only what the frame shows. It does not prove why a board differs, which version is current, or that a route will work. Record what you can see, keep the source next to it, and leave the explanation open until the evidence supports it.