REPO lives and dies by its co-op tension. The game is built around shared fear, split-second decisions, and the constant risk of one bad pull aggroing something the whole squad can’t DPS down. Playing solo is possible, but REPO’s systems clearly expect multiple players juggling objectives, covering angles, and recovering from mistakes together. Understanding how its online co-op actually works is the difference between a smooth night of scares and 30 minutes stuck at a “connecting” screen.
How REPO Handles Online Co-Op
REPO uses a lobby-based online co-op system, meaning one player hosts and others join their session. The host’s connection effectively becomes the backbone of the match, so latency, hit detection, and enemy behavior all hinge on host stability. If the host stutters, everyone feels it, from delayed interactions to enemies rubberbanding through hitboxes. For horror games where timing and positioning matter, that makes lobby setup more important than most players realize.
The game supports drop-in co-op before a run starts, but once you’re deep into a mission, invites are typically locked out. This design keeps pacing tight and avoids late joins trivializing encounters or loot RNG. Plan your party before launching, not halfway through a run.
Supported Platforms & Crossplay Reality
As of now, REPO is primarily supported on PC, with the online infrastructure built around Steam’s networking services. That means Steam friends integration, overlay invites, and platform-level matchmaking handling most of the heavy lifting. Console versions, if announced later, are not currently part of the online ecosystem.
Crossplay is not supported in the current build. PC players can only match with other PC players, and there’s no workaround through invites or private codes. If your group spans multiple platforms, everyone needs to be on the same ecosystem before you even think about forming a lobby.
Matchmaking, Invites, and Session Types
REPO gives players two core ways to play online: private lobbies with direct invites, and public matchmaking. Private lobbies are the cleanest option for friends, letting the host invite directly through Steam or an in-game friends list. This avoids randoms, reduces disconnect risk, and keeps communication tight if you’re using external voice chat.
Public matchmaking fills empty slots automatically but can introduce wildly different skill levels and playstyles. One player sprinting ahead can break formation, pull enemies early, and snowball a wipe. For coordinated co-op, private lobbies are strongly recommended.
Common Connection Issues Players Run Into
The most frequent problem players hit is failed joins caused by NAT restrictions or strict firewalls. If invites fail repeatedly, the host should verify their NAT is open and that Steam’s networking services are online. Restarting Steam, not just the game, often resolves phantom connection errors.
Desync is another issue, especially if the host’s upload speed dips. Symptoms include delayed enemy reactions, missed interactions, or teammates appearing out of position. If this happens consistently, swap hosts to the player with the most stable connection before starting another run.
What You Need Before Playing Online (Accounts, Version, Network Requirements)
Before you troubleshoot invites or blame matchmaking RNG, it’s worth making sure your setup actually meets REPO’s online requirements. Most failed co-op attempts come from version mismatches, missing accounts, or unstable connections rather than in-game bugs. Lock these basics in first, and the rest of the process becomes frictionless.
Required Accounts and Platform Setup
REPO’s online play is fully tied to Steam. Every player in your group needs an active Steam account, the Steam client running in the background, and visibility set to Online so invites actually register. If Steam thinks you’re offline, REPO will too, even if the game boots normally.
Steam Friends integration handles invites, lobby joins, and session handoffs. There’s no separate REPO account system, no in-game friend codes, and no cross-platform workaround. If you can’t see your friends in the Steam overlay, you won’t be able to pull them into a lobby.
Game Version and Build Sync
All players must be on the exact same game version to connect. Even minor hotfix differences can block lobby joins, leading to vague “failed to connect” messages with no clear explanation. If one player opted into a beta branch or hasn’t updated, the session will never stabilize.
Before hosting, have everyone verify their game files and confirm they’re on the default public build. This is especially important after patches, since Steam doesn’t always auto-update immediately. Version desync is the silent killer of co-op sessions.
Network Requirements and Connection Quality
REPO uses peer-to-peer networking, meaning the host’s connection directly impacts everyone else. A stable upload speed is more important than raw download numbers, since enemy behavior, interactions, and player positions are synced in real time. If the host’s upload tanks, desync and rubber-banding will follow.
A wired Ethernet connection is strongly recommended for whoever hosts. Wi-Fi can work, but packet loss or interference increases the risk of dropped sessions, delayed hit detection, and failed joins. If your runs keep falling apart mid-mission, the network is usually the culprit.
NAT Type, Firewall, and Background Interference
An open or moderate NAT is essential for reliable hosting. Strict NAT settings, aggressive firewalls, or router-level filtering can block incoming connections even if Steam itself is online. If players can send invites but can’t join, this is the first thing to check.
Close bandwidth-heavy background apps before hosting, especially streaming software, cloud backups, or large downloads. REPO doesn’t demand much individually, but co-op sessions stack network load quickly. Cleaning up background traffic can be the difference between a smooth run and a hard disconnect at the worst possible moment.
Creating an Online Lobby in REPO (Step‑by‑Step)
Once everyone’s version is synced and the host’s network is clean, actually spinning up a co-op session in REPO is refreshingly straightforward. The game doesn’t bury its multiplayer behind confusing menus, but a few key choices during setup can make or break your run before it even starts.
Step 1: Navigate to Online Co‑op from the Main Menu
From the title screen, select Online Play rather than jumping straight into a solo run. This routes you into REPO’s peer-to-peer matchmaking layer, where hosting and joining are handled through Steam.
If Steam isn’t fully online or your overlay isn’t responding, stop here and fix that first. Everything that follows depends on Steam’s backend behaving correctly.
Step 2: Choose Host Lobby
Select Host Lobby to create a new online session. This immediately designates you as the peer host, meaning your connection becomes the authority for enemy behavior, physics interactions, and player sync.
If you’re the one with the most stable upload speed, this is where you want to be. Hosting on a shaky connection is the fastest way to introduce rubber-banding and delayed interactions once combat ramps up.
Step 3: Set Lobby Privacy and Player Slots
Before the lobby goes live, you’ll be prompted to set privacy options. Friends Only is the safest choice if you’re playing with a known group, while Public opens the door to randoms through matchmaking.
You can also confirm the maximum player count here. Make sure this matches your group size, since changing it later often requires recreating the lobby entirely.
Step 4: Invite Friends Through the Steam Overlay
With the lobby active, open the Steam overlay and invite friends directly from your friends list. REPO does not use invite codes or in-game friend searches, so Steam invites are the only reliable method.
Once invited, players should accept through Steam, not by clicking around inside REPO. If someone doesn’t appear in the lobby after accepting, have them restart the game before trying again.
Step 5: Confirm Everyone Loads into the Lobby Properly
Wait until all players visibly appear in the lobby before proceeding. If someone is stuck loading, missing, or drops out immediately, that’s a red flag for version mismatch or NAT issues.
Do not start the session until everyone is fully synced. Launching early can cause players to spawn incorrectly or fail to load into the mission at all.
Step 6: Start the Session
Once all players are present and ready, the host can start the run. At this point, REPO locks the lobby state and begins syncing game data across all clients.
If the game hangs or someone disconnects during the transition, recreate the lobby rather than retrying from the same one. A clean lobby rebuild fixes more issues than brute-force reconnect attempts ever will.
Inviting Friends: Friends List, Lobby Codes, and Privacy Settings
Once the session is live, the real co-op setup begins. REPO keeps things intentionally lean here, which is great for speed but confusing if you’re expecting modern matchmaking conveniences. Understanding exactly how invites and privacy work will save you from endless restarts and ghost lobbies.
Using the Steam Friends List (The Only Reliable Method)
REPO is fully dependent on Steam’s friends system for online play. There is no in-game friends list, search function, or cross-platform workaround, so every invite starts from the Steam overlay.
As the host, open the overlay, right-click a friend, and send a game invite. Invited players must accept through Steam, not from any in-game menu, or the join attempt may silently fail.
If someone accepts the invite but never appears, have them fully restart REPO before retrying. This usually clears cached lobby data that causes failed joins.
Lobby Codes: Why You Won’t Find Them
Unlike many co-op horror games, REPO does not use lobby codes or manual join strings. There’s no option to paste a code, join by ID, or browse private rooms.
This design puts all the weight on Steam’s backend. It’s faster when it works, but it also means non-friends cannot join private sessions under any circumstance.
If you’re planning repeated runs, make sure everyone adds each other on Steam ahead of time. There’s no shortcut once the lobby is live.
Friends Only vs Public: Picking the Right Privacy Setting
Privacy settings determine who can see and join your lobby once it exists. Friends Only is ideal for coordinated groups and prevents random players from filling slots mid-setup.
Public lobbies allow matchmaking to pull in strangers, which can be useful for learning runs but risky if you’re coordinating loadouts or roles. A random joining at the wrong time can desync expectations fast.
Once the lobby is created, changing privacy settings is limited. If you picked the wrong option, recreating the lobby is usually faster than trying to fix it mid-session.
Common Invite and Visibility Issues (And How to Avoid Them)
If invites aren’t going through, double-check that everyone is appearing online on Steam. Invisible or Offline status can block invites even if you’re friends.
NAT issues can also prevent players from showing up after accepting an invite. When that happens, switching who hosts or restarting both Steam and REPO often resolves it.
The golden rule is patience before launching. If a player isn’t fully visible and idle in the lobby, the game hasn’t finished syncing them yet, and starting early almost guarantees a failed run.
Joining a Friend’s Game: All Matchmaking Options Explained
Once a lobby exists, joining a friend’s game in REPO is deceptively simple, but only if you follow the rules the game never clearly explains. There are no in-game join buttons, no server browser, and no fallback systems if Steam hiccups. Everything hinges on how and when you connect.
Understanding the different ways Steam handles joining is the difference between loading in smoothly and staring at an empty lobby wondering what broke.
Joining Through Steam Invites (The Primary Method)
The most reliable way to join a friend is through a direct Steam invite sent from the host’s Steam friends list. When the host creates a lobby, they should right-click your name on Steam and select “Invite to Game,” not rely on any in-game prompt.
When you receive the invite, accept it directly through Steam’s overlay or chat notification. REPO will automatically boot, sync the lobby data, and place you into the session if everything lines up correctly.
If you already have REPO open, it’s still safer to accept the invite from Steam rather than clicking anything inside the game. Steam needs to handle the handshake, or the join request may fail without an error message.
Joining via “Join Game” on a Friend’s Profile
Steam also allows you to right-click a friend who is already in a REPO lobby and select “Join Game.” This works, but it’s slightly less consistent than a direct invite, especially if the lobby was just created.
This method is best used when the lobby has been idle for a minute or two and the host hasn’t started the run yet. Jumping in too early can cause REPO to misread the lobby state and dump you back to the main menu.
If “Join Game” is greyed out, the lobby is either full, set to Friends Only and you’re not whitelisted yet, or Steam hasn’t refreshed the host’s session data. Waiting or restarting Steam usually fixes it.
Public Lobby Matching Into a Friend’s Session
Technically, you can join a friend by queueing into Public matchmaking and hoping the system places you together. Practically, this is pure RNG and not recommended for planned co-op.
Public matchmaking prioritizes filling open slots, not grouping friends. Even if a friend’s lobby is public, there’s no guarantee you’ll land in it unless the player pool is extremely small.
Use this method only as a last resort or during off-hours when matchmaking traffic is low. For coordinated runs, Steam invites remain the only consistent option.
Late Joining and In-Progress Lobbies
REPO is not friendly to late joins. If a run has already started, joining mid-session is either disabled or highly unstable depending on the build and host settings.
Even if Steam allows you to connect, you may load into a broken state with missing UI, desynced objectives, or no control over your character. From a systems perspective, the game simply wasn’t built for drop-in co-op.
If someone disconnects or crashes, the safest fix is to abandon the run, reform the lobby, and reinvite everyone. It’s slower, but it prevents compounding bugs that can ruin the entire session.
Why “Nothing Happens” When You Try to Join
One of REPO’s biggest pain points is failed joins with zero feedback. If you accept an invite and the game does nothing, it usually means Steam and REPO desynced during the lobby handshake.
The fastest fix is a full restart of REPO for the joining player. If that doesn’t work, restarting Steam itself clears lingering session data that blocks new connections.
Avoid spamming invites back-to-back. Each failed attempt increases the chance Steam caches bad lobby info, making the next join even less likely to succeed without a restart.
Recommended Co‑Op Settings for Smooth Multiplayer Sessions
Once everyone is actually inside the same lobby, the next hurdle is making sure the session stays stable. REPO’s co-op isn’t plug-and-play yet, and the wrong settings can turn a clean run into a desync nightmare within minutes. Locking in the right options before you hit Start is the difference between tense horror and unplayable chaos.
Lobby Privacy and Invite Flow
Set the lobby to Friends Only before sending any invites. Public lobbies are more likely to bug out during the initial handshake, especially if matchmaking tries to backfill an empty slot mid-setup.
Have the host create the lobby first, then invite players one at a time through Steam. Let each player fully load into the lobby UI before sending the next invite, which reduces failed joins and invisible player slots.
Host Selection and Network Stability
Always choose the player with the most stable connection as the host, not necessarily the one with the best PC. REPO uses a host-authoritative model, so lag, packet loss, or Wi‑Fi drops on the host side directly affect enemy behavior, hit detection, and objective syncing.
If possible, the host should be on a wired connection. Even minor latency spikes can cause rubber-banding enemies, delayed damage ticks, or interactions failing to register for non-host players.
Player Count and Session Size
Stick to smaller groups if you want consistency. Two to three players is currently the sweet spot, offering the best balance between difficulty scaling and network stability.
Full lobbies increase the odds of desyncs, delayed spawns, and AI behaving unpredictably. If you’re learning the game or planning a longer run, fewer players means fewer systems fighting each other behind the scenes.
Difficulty and Modifier Choices
Avoid stacking high-difficulty modifiers until you know your group’s limits. Aggressive enemy scaling combined with latency can make hitboxes feel unfair and remove any margin for error during tight encounters.
For smoother sessions, start on standard difficulty and add modifiers gradually. This keeps combat readable and prevents situations where lag turns manageable DPS checks into unavoidable wipes.
Voice Chat and External Comms
Disable in-game voice chat if your group is using Discord or another external app. Running both can introduce audio glitches and, in rare cases, contribute to performance drops during intense moments.
Clear communication is critical in REPO, especially when managing aggro or coordinating objectives under pressure. External voice chat is more reliable and keeps the in-game systems focused on syncing gameplay instead of audio.
Pre-Run Checks Before Hitting Start
Before launching the run, have every player move their character and open at least one menu. This confirms inputs and UI are syncing correctly across the lobby.
If someone can’t move, see objectives, or interact with menus, back out immediately and reform the lobby. Catching these issues early saves you from discovering a broken state twenty minutes into a run.
Common Connection Problems & How to Fix Them (Failed Invites, Desync, Lag)
Even with smart pre-run checks, REPO’s online co-op can still throw curveballs once matchmaking actually begins. Most connection issues stem from how sessions are hosted and how aggressively the game syncs enemy AI, physics, and objectives in real time.
If your group knows what symptoms to look for, you can usually fix problems in minutes instead of burning an entire night reforming lobbies.
Failed Invites or Friends Can’t Join
If invites aren’t going through, the first thing to check is who’s hosting. The host must be fully loaded into the lobby menu, not transitioning between screens, or invites can silently fail without an error message.
Have the host send invites directly through the platform overlay (Steam or console friends list) instead of the in-game invite button. Platform-level invites are more reliable and bypass some of REPO’s session handshake quirks.
If a friend sees the invite but gets stuck on “Joining,” back out completely and restart the game. REPO doesn’t always recover cleanly from a failed join attempt, and retrying without a restart often just loops the error.
Lobby Forms, But Players Desync Immediately
Desync usually shows up as players seeing different enemy positions, delayed damage numbers, or objectives completing for one person but not others. When this happens early, don’t try to push through it.
Disband the lobby and reform with a different host if possible. Host-side desync tends to snowball, especially once combat ramps up and multiple AI entities start tracking different players.
Also double-check that everyone is on the same game version. Even a minor patch mismatch can cause subtle syncing errors that only become obvious once enemies start attacking.
Mid-Run Lag and Rubber-Banding
Lag in REPO often feels worse than it looks on paper because enemy behavior is tightly synced to the host. Rubber-banding enemies, delayed hit confirmation, or sudden damage spikes usually mean the host’s connection is struggling to keep up.
Have non-host players reduce background bandwidth usage, but more importantly, confirm the host isn’t streaming, downloading, or on unstable Wi-Fi. REPO prioritizes combat and AI syncing, so packet loss hits gameplay hard.
If lag persists, pause the run and have the host restart their game before reforming the lobby. A fresh session often stabilizes performance better than trying to brute-force through a degraded connection.
Input Delay and Interactions Not Registering
When doors won’t open, items won’t pick up, or abilities trigger late, it’s usually a sync delay rather than a control issue. These problems get worse the longer a session runs under unstable conditions.
Backing out to the main menu and reforming the lobby can reset interaction syncing without needing a full game restart. If the issue returns quickly, swap hosts or lower player count to reduce network strain.
Avoid alt-tabbing or suspending the game during active runs. REPO doesn’t always resync cleanly when a player drops focus, especially mid-combat.
Matchmaking Region and NAT Issues
If your group consistently struggles to connect, check that everyone is matchmaking in the same region. Cross-region hosting increases latency and raises the odds of invite failures and mid-run lag spikes.
Strict NAT types can also block smooth peer-to-peer connections. Opening recommended ports or enabling UPnP on your router can dramatically improve invite reliability and session stability.
When in doubt, have the player with the most stable, open connection host. In REPO, a strong host does more for the group than perfect individual performance.
Co‑Op Best Practices: Staying Connected and Avoiding Session Breaks
Once your group is consistently getting into matches, the next challenge is keeping those sessions stable from start to extraction. REPO’s co‑op is unforgiving when connections wobble, and even minor desync can snowball into wipes, lost loot, or forced restarts. These best practices are about minimizing friction so the game’s tension comes from monsters, not matchmaking.
Lock in a Reliable Host Before You Queue
Everything in REPO runs through the host, from enemy AI to hit detection and item sync. Before creating the lobby, decide who has the strongest, most stable connection rather than defaulting to whoever clicks first.
Wired Ethernet beats Wi‑Fi every time, especially during longer runs where packet loss stacks up. If the host’s connection stutters, everyone feels it through delayed damage, broken interactions, and enemies snapping across the map.
If you notice consistent lag across multiple runs, don’t push through it. Disband, rotate hosts, and reform the lobby until combat and movement feel crisp again.
Invite Smart and Keep the Lobby Clean
Always send invites from the in‑game lobby instead of platform overlays when possible. REPO handles session handshakes better internally, reducing failed joins and partial connections that can corrupt a run.
Once everyone is in, avoid rapid ready‑ups and last‑second menu changes. Give the lobby a few seconds to fully sync before launching, especially after someone joins late or reconnects.
If a player disconnects mid-run, finishing the objective before reforming is risky. You’re better off pausing, exiting cleanly, and re‑inviting to prevent long-term desync from lingering in the session.
Stabilize Performance During Runs
Background apps matter more than players expect. Voice chat, streams, cloud backups, and downloads can all spike bandwidth at the worst possible time, right when the game is syncing enemy aggro or damage rolls.
Non-host players should also keep their systems stable. While the host does the heavy lifting, unstable clients can still cause interaction failures or animation desyncs that ripple through combat.
If things start to feel “off” mid-run, trust that instinct. Strange hitboxes, missed pickups, or delayed abilities are early warning signs that the session is degrading.
Know When to Reset Instead of Forcing It
REPO doesn’t reward stubbornness with bad connections. If rubber-banding or input delay shows up repeatedly, backing out and reforming is almost always faster than trying to survive a broken run.
Restarting the host’s game clears memory and network hiccups that menu resets can’t fix. It’s a small time loss that prevents bigger frustrations later.
Treat session stability like resource management. A clean connection is just as important as ammo, health, or team positioning.
Final Tip: Consistency Beats Convenience
Playing REPO online with friends works best when your group builds habits around stable hosting, clean invites, and smart resets. The smoother your sessions run, the more the game’s tension comes from enemy pressure and decision-making, not tech issues.
Lock in a reliable setup, respect the warning signs, and REPO’s co‑op transforms from fragile to brutally satisfying. When the network disappears into the background, that’s when the horror really shines.