Room and host guide

Meccha Chameleon multiplayer with friends

Steam recommends 2–10 players and says the maximum depends on the host's network environment. That means the useful question is not “what is the biggest number?” but “what group can this host run clearly and reliably?”

Use the room checklist Verify on Steam

Pick group size by the experience you want

2–4 players: learn the loop

Use a smaller room when people are still learning paint controls, poses, and seeker movement. Fewer bodies make mistakes easier to explain, but hiding routes become easier to predict. Rotate roles often so one person does not spend the whole session teaching.

5–8 players: balanced party

This is our editorial recommendation for a mixed-skill friend group. There are enough hiders to create uncertainty without making voice chat, explanations, and host load difficult to manage. It is not an official “best” number.

9–10 players: more noise

Use the upper end of Steam's recommendation when the host connection is stable and everyone knows the rules. More players increase simultaneous painting, spectating, and communication, so test one short round before committing to a long session.

Beyond the recommendation

Steam explicitly ties the maximum to host network conditions. Avoid publishing or relying on a universal hard cap. Add players gradually, watch latency and synchronization, and reduce the room if the match becomes unreliable.

Private-room checklist

Choose the strongest host. Prefer the player with stable wired or strong Wi-Fi, low background uploads, and enough system headroom.
Confirm the privacy setting. The official description says a server that is not private can be joined by anyone. Check privacy before sharing room details.
Align game versions. Everyone should restart Steam and confirm updates before troubleshooting invitations or immediate disconnects.
Start with a short test round. Verify that painting, discovery, spectating, and role changes synchronize before adding Workshop content.
Add one variable at a time. Increase player count first; add custom maps or unusual options only after the base room is stable.

Public-room and Workshop safety

Public matching is part of the official feature set, but other players and Workshop authors are third parties. Do not treat a lobby name, chat message, or mod description as a developer endorsement.

Keep Steam Guard and account protections enabled.
Do not follow links that ask for a separate login, giveaway claim, or executable download.
Use the no-mods or server-tag controls documented in official updates when you want a simpler room.
Leave and report harassment, impersonation, or suspicious file requests instead of arguing in the lobby.
Review current official security and Workshop notices before subscribing to unfamiliar items.

Troubleshoot in a fixed order

Symptom	First check	Next isolation step
Friend disconnects immediately	Compare game versions and restart Steam.	Create a new private room with no Workshop content.
Room is visible but cannot be joined	Check privacy, capacity, and whether a match is already in progress.	Try a different host and a base official map.
Paint or player state lags	Pause host downloads and background uploads.	Reduce room size until the base match is stable.
Problem starts after adding a map	Return to an official map.	Remove the newest Workshop item and retest one change at a time.

This sequence separates version, host, capacity, and third-party-content failures. If the base room still fails, check the latest official announcements before reinstalling or changing several settings at once.

A simple 45-minute friend session

5 minutes: version check, privacy check, and one explanation of the paint-and-hide loop.
10 minutes: two short rounds on an official map with role rotation.
20 minutes: normal rounds using the group size that stayed stable.
10 minutes: add one new map or option, then stop if reliability drops.

This schedule is editorial advice, not an official mode. Its purpose is to find problems while they are still easy to isolate.