Co-op Play: Communication and Role-Splitting Tips

Polygon and Kotaku both land on the same idea: Big Walk is not just a puzzle game that happens to support multiplayer. It is a multiplayer game where the quality of your communication changes the quality of your puzzle-solving.

Give the group clear roles

Even a small team benefits from a light division of labor. Let one player scout, one player confirm what was seen, and one player act on the instruction. The point is not to formalize everything, but to stop the whole group from speaking at once.

When the group grows, this matters even more. Without clear roles, useful details disappear into chatter.

Use short calls, then repeat them

Long explanations tend to collapse in motion. A much better pattern is “direction, landmark, action.” For example: ridge, left side, check the structure. Short calls are easier to repeat, and repetition matters in a game built on distance and separation.

That is also why review coverage often describes the game as a trust exercise. You do not always stay close enough to verify every step in real time.

Review the process, not just the result

If a puzzle attempt fails, ask what information got lost instead of asking who made the mistake. Did the group skip confirmation? Did someone describe a place differently? Did the acting player leave before the others fully understood the plan?

A short recap after each confusing moment usually improves the whole evening faster than brute-force retrying.

Key Takeaways

• Light role-splitting keeps group information readable.
• Short, repeatable calls work better than long explanations.
• Confirmation is a mechanic, not a luxury.
• When a plan fails, inspect the communication chain first.

Reference Sources

• Polygon Review
• Kotaku Review
• Big Walk Official FAQ