Role checklist

Chameleon! Round Planner

Choose Hider or Seeker, set your experience and risk appetite, and get a three-step checklist for the next round — generated from the official paint–blend–survive loop, not from invented classes.

Checklist logic reviewed 2026-10-10

Round setup

Choose your role and approach

RoleExperienceRisk preferenceCommunication

Hider checklist

Your three-step round plan

1
Pick an easy-to-read wall or floor color before exploring.
2
Balance color match, silhouette cover, and traffic.
3
Watch seeker movement yourself and avoid last-second corrections.

Avoid this mistake

Do not rely on color alone when your outline or movement is obvious.

Open Hider Tips

This planner creates a personal checklist. It does not claim that Chameleon! has a formal squad, class, or loadout system.

How it works

Four inputs, three steps, one honest scope

The planner is a decision tree over the choices that actually differ between players — everything else about a round is the same for everyone.

What each input changes

Role selects the whole branch: Hider plans optimize for being ignored, Seeker plans for coverage.
Experience swaps the first step — first-rounders get one easy, readable choice; returning players get a two-candidate pre-plan, because they already know the map's color families.
Risk preference sets the settling rule: Low traffic-first, High color-first with an escape, Balanced mixes both.
Communication adds a step only when it exists — solo players self-track; text or voice players get a discipline rule (call spots, never narrate your own movement).

Worked example — Balanced Hider, returning, solo

The tool returns: pick two candidate surface families before the search begins; balance color match, silhouette cover, and traffic; watch Seeker movement yourself and avoid last-second corrections. The matched mistake warning: do not rely on color alone when your outline or movement is obvious.

Note how the steps mirror the official loop — paint yourself: navigate all color pools and coat your avatar. then blending, then surviving. The checklist only sequences the decisions the description leaves to you, like which surface family and when to move. Everything it refuses to decide (timers, role selection) is decided by the server you join — up to 16 players per round.

Using the plan

From checklist to survived round

1. In the lobby: generate the plan and read the mistake line twice — it names the failure mode this specific plan must avoid.
2. Hiding phase: execute step one, then run the Camouflage Score on your chosen spot; if it lands under 55, apply the planner's risk rule instead of trusting the paint.
3. Search phase: hold unless your leave-trigger fires. The plan's communication step doubles as your discipline contract: if you said “text only for traffic warnings,” a pings-storm mid-round is you losing to nerves.
4. After the round: one-input change (risk or communication) is enough to feel the difference — regenerate and compare rather than re-rolling everything.

FAQ

Planner questions

Does PAINT OR DIE! have squads, classes, or loadouts?

The official description documents none. It defines one loop — paint, blend, survive — with Hiders and a Seeker. The planner therefore builds a personal checklist, and says so in its own footer instead of borrowing class systems from other games.

How many different plans can it generate?

Four inputs (role, experience, risk preference, communication) combine into 18 Hider checklists and 18 Seeker checklists — 36 three-step plans plus a matched mistake warning for each.

When should I set up the plan?

In the lobby or the first free seconds of a round, before you paint. The plan decides where you will hide and what will make you leave, so you spend the hiding phase executing instead of improvising under time pressure.

Why only three steps?

Because three is what fits in a working memory under pressure: where you hide, what makes you hold still, and how you communicate. Longer checklists get skipped exactly when they matter.

What changes between a Hider and Seeker plan?

A Hider plan optimizes for being ignored: surface choice, stillness triggers, and quiet communication. A Seeker plan optimizes for coverage: learning the map's natural colors first, scanning in a fixed order, and tracking cleared areas so the search never loops.

Turn the checklist into a stronger round

Hider