How to Report Cheating in Color Block Jam Safely

What does the current official answer say?

Rollic asks players to report suspected cheating through in-game support or by email. The in-game path is Main menu, Settings, Support, Chat with Us. A concise report with screenshots, a recording, or visible player information gives the team something to review; a public accusation or a copied exploit does not.

A report is evidence for an investigation, not a verdict. Describe what you saw, when it happened, and why it appears outside normal play. Avoid sharing unnecessary personal information or attempting to reproduce a suspected exploit on your own account.

The Rollic Help Center page linked in this article was checked on 2026-08-18. It is the source of truth for the product action described here. Use this guide to understand the decision and prepare a useful next step, not to replace the live game, store, support ticket, or legal policy.

What should you check before taking action?

Check	What it means
Visible player information	Include the identifier exactly as shown
Suspicious result	Describe the action and the expected behavior
Screenshot or recording	Crop unrelated private details
No clear evidence	Report the concern without claiming certainty

Use neutral language such as “suspected cheating” and separate what you observed from what you infer. This helps support review the case fairly and reduces the risk of reporting an ordinary level difference as misconduct.

A good support or settings workflow changes one condition at a time. That makes the result explainable and reduces the chance of turning a small problem into lost progress, duplicate spending, or an account-security issue.

Why can two players see a different result?

Color Block Jam can differ across app versions, store accounts, regions, devices, event windows, and local progress. A support article describes the product state it was written for, while your live screen shows the state delivered to your installation. Neither a level number nor an old screenshot is enough to prove that two sessions are identical.

When comparison matters, record the app version, platform, date, exact screen, and first meaningful difference. For puzzle mismatches, use the site’s wrong-level checklist before following a move sequence. For account, settings, event, or purchase questions, prefer the current official wording and store evidence.

What is the safest step-by-step workflow?

1. Write down the level, event, date, and visible player context.
2. Capture a screenshot or short recording if it contains no private credentials.
3. Open Settings, Support, and Chat with Us in the game.
4. Choose the Safe & Fair Play route when it is offered.
5. Send one complete report and wait for support instead of opening repeated tickets.

After each action, reopen the same screen and record whether the state changed. If the result is not the one described by the current official source, stop before deleting data, spending resources, or repeating a purchase.

What should you avoid?

Do not dox a player, publish private messages, or upload a modified game to prove that it works. Never send an account password, payment number, PIN, or one-time code to support.

Also avoid treating search snippets, forum comments, videos, or this independent guide as a replacement for the current game interface. Secondary sources can explain a concept, but the official support article, platform store, account screen, receipt, or legal policy controls the action.

Which related guides help next?

• Continue with color block jam cheating.
• Continue with color block jam fair play policy.
• Continue with color block jam contact support.

Reporting is a support workflow, not a community punishment system. Pair this page with the definition of cheating and the fair-play policy before deciding whether a report is warranted.