GRAIN ROT Multiplayer: Public Lobbies and Co-op Setup

Does GRAIN ROT support multiplayer?

Yes. The official Steam store lists Online Co-op alongside Single-player. Recent 1.0 gameplay also shows a four-person group descending and interacting with the game’s physical systems together. The official FAQ says the game is balanced and best played around four, while describing broader support in terms of what the host setup can handle.

Patch 1.04 added a configurable maximum player count to the lobby settings. Patch 1.07 then added a public server browser, password protection, and more host settings. Neither patch note nor the Steam store publishes the player setting’s numeric range, so this guide does not turn a community screenshot into an official hard ceiling.

Choose public or private joining

GRAIN ROT sessions remain player-hosted. Patch 1.07 added an in-game browser for public servers, so the launch FAQ’s statement that there was no public matchmaking is now outdated. The browser is a discovery path for hosted sessions; the patch notes do not describe an automatic skill-based queue.

Friends-only and invite-only privacy modes still exist. Patch 1.07 says these modes now allow friends of anyone already in the server to join, not only friends of the host. Password-protected servers provide another option when a group wants public discoverability with controlled access.

Patch 1.04 added the configurable player limit, a view-lobby menu, individual microphone volume, and host kick or ban controls. Patch 1.07 added more host settings under the multiplayer options tab. Use the current controls rather than following a pre-patch menu recording.

Because invitation interfaces can change, this guide does not pretend to provide a screenshot-perfect menu path without a current UI capture. The practical preparation is straightforward:

1. Decide whether the session should be public, friends-only, invite-only, or password protected.
2. Have the host create the session and review the current player and host settings.
3. Share the password, send a Steam invite, use a friends-list join, or locate the host in the public browser.
4. Confirm everyone is present before committing the group to a descent.

The official FAQ also says each player needs a copy of the game.

How the public server browser works

Patch 1.07 confirms that public servers can be joined through an in-game browser. It does not document ranking, regional filtering, persistent dedicated servers, or automatic team assignment. Treat it as a live list of joinable player-hosted sessions unless the current interface says otherwise.

Public groups add coordination and host-control risk. Read the visible session details, confirm the current objective after joining, and do not assume another crew shares your extraction threshold. Hosts should review the current moderation and privacy controls before opening a room.

GRAIN ROT mic not working: check these first

Work from the local input toward the lobby. If Windows cannot provide microphone input, changing the room or host will not fix it. If Windows sees the microphone but only one teammate cannot hear you, the per-player lobby control becomes the stronger lead.

Use this order:

1. Open Windows Settings → Privacy & security → Microphone and confirm microphone access is enabled.
2. Confirm Let desktop apps access your microphone is enabled. GRAIN ROT and Steam are desktop applications and may not appear as individual Store-app toggles.
3. Check that Windows shows microphone activity when you speak. If it does not, test the selected headset or microphone outside the game before changing lobby settings.
4. Have the host or affected teammate open the current lobby view and check your individual microphone volume. Patch 1.04 added per-player microphone volume controls, so one player can be silent for one listener without the whole lobby voice system being down.
5. Make sure everyone is on the same current patch, then leave and recreate the lobby after changing device permissions or input hardware.

Microsoft documents the relevant Windows microphone privacy controls. Patch 1.04 verifies the in-game per-player volume control, but the current official notes do not publish a universal push-to-talk key or a fixed microphone-device menu path.

Divide jobs before the elevator opens

Co-op reduces the “one pair of hands” problem, but it introduces coordination risk. Before descent, agree on the run’s main job. A squad that does not share a stop condition can lose time while one player prepares the exit and another keeps extending the route.

Useful responsibilities include:

• keeping track of the elevator and the cleanest return path;
• moving required objects or extraction value toward the anchor;
• watching for enemies while another player uses noisy machinery;
• identifying recovery points and communicating when the group’s margin is gone.

These are roles, not permanent classes. Swap them when damage, carried objects, or route position changes.

Keep the group’s map synchronized

Procedural layouts make silent exploration expensive. Call out meaningful junctions, recovery points, and the branch that returns to the elevator. A player who discovers a useful room but cannot explain the route back has created information the squad cannot reliably use.

When the group splits, keep the distance small enough that one side can still respond to trouble. Co-op is strongest when tasks happen in parallel without turning into isolated solo runs. If the squad’s route knowledge diverges, regroup at the elevator or another unmistakable landmark.

Agree on the extraction threshold

The team should decide when a run is already successful. Required task items, completed elevator conditions, low recovery, and a confused return route are all reasons to lower the appetite for another branch.

A teammate’s ability to carry more does not remove the risk to the group’s unextracted haul. If the whole squad fails, the items that did not return are lost. Make the final push a group decision, not the result of the most optimistic player walking into the next room.

If one Vessel breaks, switch the squad’s immediate priority to the Living Spark recovery route. One broken body is recoverable; letting the situation cascade into a full crew loss threatens every unsecured item.

If joining fails

Start with the narrowest checks before assuming the game is broken:

• confirm Steam shows the players as friends and online;
• have the host recreate the lobby and resend the invitation;
• ensure everybody is on the same current game version;
• restart Steam and the game if the friends-list state looks stale;
• consult the official Discord or Steam Community for a live service issue.

Patch 1.05 fixed a bug that prevented some players from joining when lobby privacy was set to friends. If that exact failure continues, confirm every player is on Patch 1.05 or later before changing router settings.

Patch 1.07 changes who can join friends-only and invite-only sessions: friends of any current player may be eligible, not just friends of the host. If an unexpected person can see the session, review privacy and password settings before treating it as a connection bug.

This page intentionally avoids inventing port-forwarding steps or network settings that current sources do not require. If a later patch introduces a documented technical fix, it should be added with a direct source and verification date. Hardware and network requirements are tracked separately in the PC compatibility guide.