🦸 Superheroes
A fan-made gameplay palette for Batman with hex, RGB, and HSB values for each playable color part. Study the reference, then test your color memory.
cape
rgb(26, 26, 26)
HSB(0° 0% 10%)
suit
rgb(103, 109, 115)
HSB(210° 10% 45%)
Use this round slowly. Batman is most useful when you are checking whether dark parts stay separated without inventing fake brightness.
Run the darkness test →Everyone knows Batman looks dark. The challenge is not remembering black and calling it finished — it is remembering how dark each part feels relative to the other.
That is why Batman belongs in the flagship set as a later-step page: he exposes weak brightness control far more than weak character recognition.
On bright palettes, a wrong guess often still looks obviously close. On Batman, a small brightness miss can flatten the cape and suit into one muddy block or separate them too aggressively.
If Superman teaches clean contrast, Batman tests whether you can preserve contrast when the entire palette lives in a much darker range.
See how this palette compares with another iconic challenge before you decide what to play next.
Compare Superman vs BatmanTone Trap
Use Batman to study relative darkness, not to prove that you know the character. The reveal matters here because the palette can feel right while still collapsing tonally.
Cape
darkest control point
Cape acts as the darkest control point for Batman. It is the darkest part in the palette, so even a small brightness miss can flatten the whole character. It is one of the calmer pieces, so players often forget how much restraint it needs. Use Cape against Suit to check whether your guess kept the right contrast relationship.
rgb(26, 26, 26) · HSB(0° 0% 10%)
Suit
brightest and loudest anchor
Suit acts as the brightest and loudest anchor for Batman. It is the brightest part in the palette, so players often remember it as cleaner or more glowing than it really is. This is also the most saturated piece, which makes it the easiest part to overcook. Use Suit against Cape to check whether your guess kept the right contrast relationship.
rgb(103, 109, 115) · HSB(210° 10% 45%)
These are tone errors, not character-ID errors.
Play Batman after a clean benchmark page, not before one.
If Batman still collapses into one muddy block, step back into brighter flagship benchmarks first, then return once your brightness control is steadier.
Return to brighter benchmarksBecause Batman lives in a darker brightness band where small misses are harder to see in advance, while Superman gives you louder anchors that are easier to compare on reveal.
Batman trains low-brightness contrast judgment: keeping two dark parts separate enough to feel intentional without inventing fake brightness that is not in the target palette.
Players usually make the cape too generically black and the suit too lifted or too cool, which destroys the intended tonal relationship.
Try Batman after you have a stable feel for cleaner benchmark pages like Superman or Mario. He is much more useful as a contrast test than as a first-ever flagship page.
Dark knight of Gotham, strikes fear at night
A Batman run is valuable because it removes the safety net of bright, cheerful anchors. If your eye only works on obvious palettes, this page exposes it immediately.
That is exactly why Batman should stay a flagship depth page instead of being treated like another interchangeable character SEO entry.