Gameplay video reference
Use this gameplay reference to watch how paint, lighting, pose, and movement create clues for a Seeker.
Quick answer
A Seeker in MECCHA CHAMELEON wins by finding every Hider before the time limit ends. The official Steam page describes the game as a hide-and-seek match with a Seeker team and a Hider team. Hiders paint a pure white body to mimic the stage, so your job is not only to chase movement. You must notice when a surface, shadow, pattern, or pose does not quite belong.
This MECCHA CHAMELEON seeker guide uses the community-friendly term “Seeker,” but you will also see “Hunter” in official patch notes. Treat them as the same role unless the page is quoting a patch note directly. The v1.1.0 notes use Hunter for FOV, and the v1.2.0 notes use Hunter for the line-of-sight ranking mechanic.
Seeker rule: do not run through a room hoping to see movement. Good Hiders stay still, so you need to hunt for visual mistakes.
How Seekers win
Seekers win when every Hider is found within the time limit. That makes the last Hider the most important player on the map. If you clear a room too quickly and miss one painted body, the Hider team can still win even if every other Hider has already been tagged.
The best Seeker habit is to search in clean layers. First, clear obvious corners and wall edges. Second, check object clusters and floor-wall seams. Third, slow down for texture, shadow, and silhouette issues. This order gives you speed without becoming random.
| Seeker goal | What to check | Why it matters |
|---|---|---|
| Find every Hider | Walls, corners, floors, props, shadows. | One surviving Hider can still win the round. |
| Avoid wasted passes | Use the same scan route each room. | Random movement causes missed zones and repeated checks. |
| Catch strong camouflage | Look for outlines and lighting errors. | Color alone may be almost correct. |
What to look for
Painted Hiders usually fail in one of five ways: color, light, texture, shape, or placement. A beginner often looks only for movement, but a good Hider will not move. Train your eye to compare each suspicious object with the surface around it.
| Tell | What it looks like | How to check it |
|---|---|---|
| Color mismatch | A painted body is close but not identical to nearby wall or floor color. | Compare the suspicious patch with the exact surface behind it. |
| Lighting error | The body is too bright, too dark, or has a shadow in the wrong direction. | Look at how light falls on real props in the same area. |
| Texture break | Tiles, wallpaper, lines, or brush patterns do not continue naturally. | Follow the pattern across the suspicious object. |
| Shape anomaly | The object looks too centered, too human, or too clean for the scene. | Check the outline from a side angle before leaving. |
| Forced stillness | A “prop” is placed where a player would choose to hide, not where scenery belongs. | Ask whether that shape makes environmental sense. |
How to scan a room
Room scanning should feel boring on purpose. Enter, choose a direction, clear the perimeter, check clusters, then move inward. The goal is to avoid the most common Seeker mistake: looking everywhere and remembering nothing.
Pause for a second when entering a room. Fast motion makes your own camera movement hide small visual errors.
Hiders like surfaces that help their outline disappear. Check seams, wall joins, and narrow shadow lines first.
Look around shelves, furniture groups, props, signs, and clutter. Painted bodies often rely on visual noise to hide mistakes.
If a patch has the right color but wrong shadow, texture, or sheen, treat it as suspicious.
Strong Hiders sometimes look convincing from the front but fail from a side angle.
Enter room -> Check walls and corners -> Change angle -> Confirm shape -> Shoot carefully
Common Seeker misses
- ×Only scanning for movement.
- ×Leaving a room after one front-facing glance.
- ×Skipping corners, signs, and ceiling lines.
- ×Shooting before confirming the silhouette.
- ×Trusting old route advice after a patch.
Better habits
- ✓Clear the perimeter before the center.
- ✓Check suspicious spots from the side or from lower height.
- ✓Compare shadow direction and pattern continuity.
- ✓Use the same room order every time.
- ✓Slow down on strong Hider routes instead of flicking past them.
Beginner checklist
Use this checklist for your first few Seeker rounds. It is better to be consistently careful than to sprint and miss hidden players.
Learn the Hider toolkit
Understand that Hiders sample colors, paint shadows, and choose poses. Knowing their tools tells you what mistakes to expect.
Do not chase only movement
Good Hiders freeze. Look for color seams, outline edges, and textures that stop unnaturally.
Check common surfaces first
Walls, corners, floor edges, prop clusters, and shadowed spots are natural Hider choices.
Use a repeatable route
Clear each room in the same order. A repeatable route keeps you from skipping zones under pressure.
Patch changes
Two recent patches matter for Seeker strategy. Patch v1.1.0 increased Hunter FOV from 90 to 100 and brightened shadows across stages. Patch v1.2.0 added line-of-sight ranking based on distance and time spent within the Hunter's line of sight. These are official patch facts, but the exact ranking formula is not public.
| Patch | Confirmed change | Seeker meaning |
|---|---|---|
| v1.1.0 | Hunter FOV increased from 90 to 100. | Your wider view helps, but it also makes Hiders more likely to enter LoS. |
| v1.1.0 | Shadows brightened across stages. | Dark-corner Hiders may be easier to inspect, so check shadows carefully. |
| v1.2.0 | Ranking based on distance and time in Hunter LoS. | Hiders may intentionally risk staying near your view, so slow glances matter. |
| v1.2.0 | Penguin Hotel added; Backrooms wall-stuck fix. | Map routes should not be trusted unless they are current and confirmed after v1.2.0. |
Line-of-sight ranking
The v1.2.0 line-of-sight ranking changes how confident Hiders may behave. A Hider who believes their disguise is strong may choose a spot where you can almost see them, because time spent within the Hunter's line of sight can now affect ranking.
For Seekers, this means very fast passes are weaker than before. If you sweep past a wall for half a second, you may give a skilled Hider exactly what they want: visibility without enough inspection. Stop, compare, and finish the check before moving on.
Note: the patch confirms distance and time in line of sight, but it does not reveal point values, medals, or exact thresholds. No confirmed formula exists.
Map notes
Penguin Hotel was added in v1.2.0. Apply the general room-scan order below while map-specific patterns build up. Backrooms is confirmed in v1.2.0 because it received a wall-stuck fix. Treat any map-specific Seeker route as unverified until confirmed by footage or official sources.
| Map note | Confirmed? | Reason |
|---|---|---|
| Penguin Hotel exists. | Yes | Confirmed in v1.2.0 patch notes. |
| Penguin Hotel route names. | No | No reliable route evidence yet. |
| Backrooms wall-stuck advice is outdated. | Yes | v1.2.0 adjusted Backrooms to prevent wall-stuck issues. |
| Exact patrol route per map. | Not yet | Needs gameplay footage or confirmed screenshots. |
Related pages: MECCHA CHAMELEON maps, Penguin Hotel early notes, and v1.2.0 patch notes.
Mistakes to avoid
| Mistake | Why it fails | Better habit |
|---|---|---|
| Reacting on impulse | You waste time on every odd shape instead of confirming real tells. | Pause and compare suspicious details. |
| Random scanning | You forget which zones are already cleared. | Use a fixed route through each room. |
| Looking only for movement | Good Hiders stay completely still. | Read color, shadow, texture, and outline. |
| Ignoring corners | Many Hiders choose wall-adjacent spots. | Clear the perimeter before the center. |
| Trusting old route advice | Patches can change collision, shadows, and map behavior. | Check current patch notes before map-specific claims. |
Open the map where this matters most
Claims to verify
| Claim | Status | Recommended approach |
|---|---|---|
| Exact line-of-sight scoring formula | Unverified | |
| False tag penalty | Unverified | False tags are treated as costly in time; no confirmed mechanic penalty has been found. |
| FPP / TPP keybinds | Community-reported | Keybinds are community-reported, not official controls. |
| Exact route for Penguin Hotel | Unverified | No confirmed route exists — see early map notes for general tips. |
| Prep phase duration | Unverified | Practical scan advice is provided; no confirmed timer number has been found. |
Seeker FAQ
What do Seekers do in MECCHA CHAMELEON?
Seekers search the stage after Hiders have painted and posed. Their goal is to find and tag every Hider before the time limit ends.
How do Seekers win in MECCHA CHAMELEON?
Seekers win by finding every Hider within the time limit. If even one Hider survives until the end, the Hider team wins.
Is Hunter the same as Seeker?
Yes. This guide uses Seeker because players commonly search that term. Official patch notes often use Hunter for mechanics such as Hunter FOV and Hunter line of sight.
How do I spot a Hider who matches the wall color?
Look beyond color. Check the outline, shadow direction, texture pattern, object placement, and whether the shape looks too human or too perfect for the scene.
What did v1.2.0 change for Seekers?
v1.2.0 added ranking based on distance and time spent within the Hunter's line of sight. Seekers should slow down and inspect suspicious areas rather than giving Hiders easy near-visibility.
Do not judge paint quality alone
July reports describe third-party auto-paint software that copies background detail onto a Hider model. Strong paint by itself is not proof of cheating. Check how quickly the texture appeared, whether complex detail was replicated without normal correction, and whether the player’s pose, outline, movement, and placement still fit the scene.
Use the July 2026 news and fair-play guide for the current evidence labels, safe reporting steps, and the difference between suspicious automation and legitimate manual camouflage.
Sources checked
Steam and SteamDB are used for official facts. Gameplay strategy is written as player-facing interpretation; unconfirmed route names, formulas, and keybinds are not included.