Why LFG looks different in Big Walk
Big Walk does not have single-player, random matchmaking or public lobbies. The host owns the save, the session is built around a continuing group and the join code changes each time the host starts a run.
That means a good LFG post needs more than a simple 'need players' line. The best requests make the hosting plan, platform and session length obvious up front.
What to include in an LFG post
Use this as a template before posting in a public thread or community server.
| Field | Why it matters |
|---|---|
| Platform | Crossplay exists, but players still need to know what they are joining from. |
| Host availability | The same host should return if the group wants to keep one save. |
| Time zone and session window | Big Walk works best when the group can stay together for a while. |
| Mic or text chat | The game supports both, but the group should know the plan before joining. |
| Spoiler tolerance | Some players want blind exploration while others want route help. |
| Player-count target | The host should choose the minimum world size that matches the group. |
| Experience level | New players and route racers often want different pacing. |
Where players are gathering
The community signal changes quickly during launch week, so treat these pages as leads rather than permanent directories.
| Source | Best use | Note |
|---|---|---|
| r/BigWalk | Release-day chatter, guide links and general player reports | Monitor the New feed for the latest questions. |
| Looking For Group & Discord Megathread | Finding a stable group by platform, time zone and mic preference | The linked Discord servers are community-run, not official. |
| No public lobbies concern | Understanding why some players want a clearer join path | Useful for a 'how to group up' explainer. |
| Steam Community Hub | Discussions, screenshots, guides, reviews and broadcasts | Dynamic and worth checking daily. |
| Steam multiplayer discussion thread | Questions about 2-player+, crossplay and joining behavior | Good for troubleshooting repeated confusion. |
| r/Games and r/CoOpGaming review posts | Launch reaction, session length and co-op difficulty | Use as reception signals, not as final authority. |
Good etiquette for a stable run
Clear expectations make Big Walk's host-save structure much easier for strangers or loose friend groups to handle.
- Say whether you want a one-night session or a continuing save.
- State the platform and whether you are happy to use in-game chat only.
- Ask about spoilers before posting route or trophy requests.
- Do not share Discord IDs or private contact details without permission.
- Keep the host plan simple: who saves, who joins and when the next session starts.
Sources & attribution
No single-player, no matchmaking, host save and join-code rules.
Redditr/BigWalkMain community entry point.
Reddit / r/BigWalkLooking For Group & Discord MegathreadPlatform, time zone and mic-preference group requests.
Reddit / r/BigWalkNo public lobbies concernPlayer concern about discoverability and entry barriers.
SteamSteam Community HubDiscussions, guides, screenshots, reviews and broadcasts.
Steam CommunitySteam multiplayer discussion threadCommunity discussion of player count and joining behavior.