Machine Party Lobby Setup Guide

Machine Party multiplayer runs through Steam online co-op for two to four players. There is no substitute for a clean lobby: everyone on the same build, controllers configured, voice chat live, and a host who knows how to keep downtime short between lethal minigames. This guide walks through practical setup steps, then points to party sizes, tier lists, and planning tools so your facility nights start on time.

Before anyone accepts an invite, confirm each player meets system requirements — Windows 11 or Linux with Vulkan, 8 GB RAM, and GPU classes around RX 6500 XT or GTX 1660. Latency spikes hurt timing modes tied to achievements like Quick draw! and Mind the gap. more than raw frame rate drops.

Step 1 — Own the game on Steam

Every participant needs Machine Party (app 4108000) in their Steam library or via Family Sharing where permitted. Mixed-version lobbies fail silently or desync — host should announce when an update drops and pause until everyone patches.

Step 2 — Choose the host

Pick the player with the most stable connection and a habit of showing up on time. Host accepts join requests, starts matchmaking into the party collection, and usually controls rematch votes. If the host disconnects, be ready to reform the lobby; there is no guarantee of seamless migration at launch.

Step 3 — Send invites

Use Steam friends overlay: right-click a friend, invite to game, or share a join link in Discord. For groups larger than four, rotate subs each session using the party planner so bench players know which minigames come next.

Step 4 — Configure input

Machine Party ships with full controller support. Mixed keyboard and controller lobbies work, but agree beforehand — some dexterity modes on the difficulty tier list assume analog movement. Test buttons during the first low-chaos minigame before jumping into chaos-tier picks.

Step 5 — Voice chat

The game does not replace Discord or Steam voice. Create a channel, push-to-talk if echo is bad, and keep call active through eliminations so jokes land. Sabotage modes like crate throws (Catch this! on Steam) are funnier when victims hear the betrayal live.

Step 6 — Customize test subjects

Open customization before readying up — see test subject guide. Distinct outfits prevent “who shoved me” arguments when four silhouettes stack on an escalator tied to Stairmaster.

Step 7 — Ready check and start

Host confirms all players show ready indicators, then launches the session. First-time groups should ask for a verbal ready count even if UI shows green checks.

Between minigames

Machine Party advertises minimal downtime. Still, use gaps to:

• Hydrate and mute if needed
• Adjust party planner queue if a mode felt unfair
• Note achievement pop-ups for the achievements page checklist
• Swap host only if connection issues appear

If arguments erupt, spin the minigame picker to depersonalize the next pick.

Troubleshooting

Cannot join friend — Verify same game branch, disable VPN, restart Steam.

Controller not detected — Switch to Big Picture input test, then relaunch.

Linux player dropped — Confirm Vulkan drivers and Proton settings if applicable; details on system requirements.

Desync or rubber-banding — Lower graphics preset, use wired Ethernet, reduce lobby to three players per party sizes.

Etiquette for lethal parties

Machine Party is violent party comedy, not ranked esports — unless your group makes it one. Agree on quit rules: rage-quitting after one gory elimination kills the night. Use review tone as the baseline for whether dark humor fits everyone present.

Related guides

• Multiplayer hub — overview and checklist
• Party sizes — duos vs trios vs fours
• Tools hub — planner and picker widgets
• Updates hub — patch-day lobby changes