Co-op, split screen and cross-play
Co-op is two players only, online or split screen on one machine; PC and Xbox can play together, PlayStation cannot join them, and there is no friend pass so both players need a copy.
Escape Academy 2 is a two-player game, and almost every wrong expectation about it comes from that number. It is not four-player. It is not drop-in. There is no friend pass, so a guest cannot play on the host's licence. What it does have is online play and local split screen, and a cross-play arrangement with one specific hole in it.
The details here come from the developer's own pinned FAQ on the Steam forum, the store's category tags, and a co-op bug thread with a confirmed fix.
The rules, in one table
| Question | Answer | Source |
|---|---|---|
| Maximum players | 2 | Pinned FAQ, "co-op only supports 2 players" |
| Online co-op | Yes | Store tags |
| Local split screen | Yes | Store tags, "shared/split screen co-op" |
| Friend pass | No | Pinned FAQ, both players need the game |
| PC to Xbox cross-play | Yes | Pinned FAQ |
| PC or Xbox to PlayStation | No | Pinned FAQ |
| Remote Play Together | Yes | Store tags |
| Family sharing | Yes | Store tags |
| Player count per machine | One per screen; split screen means two on one machine | Store tags |
That last row is the one people get wrong. Split screen is not a way to bring a third and fourth person; it is a way to play the same two-player game without a second machine and a second copy.
Cross-play, precisely
The FAQ's answer is unambiguous and worth quoting because it is the single most load-bearing sentence for anyone coordinating a group: "Cross-play is supported between PC and Xbox. Cross-play is not supported with PlayStation."
In practice:
- PC and Xbox players can share a lobby. That covers Steam, the Microsoft store version and Game Pass.
- A PlayStation player cannot join a PC or Xbox lobby. They can play with other PlayStation players.
- There is no workaround. This is not a port flag or a settings toggle; it is the supported matrix.
If your group is split across all three platforms, the two-players-only cap means you are already choosing who plays together, and this decides which pair can.
The local co-op controller bug, and the fix
The first major co-op bug reported after launch is specific and has a confirmed fix from the person who reported it.
The symptom: in local co-op, the second player cannot do anything in a level. Both controllers work in the menu, but once a level loads, one controller drives player one and the second controller does nothing at all. Going back to the menu makes both work again. The reporter noted it reproduces constantly, survives power-cycling both the game and the controllers, and also happens with a keyboard for player one and a controller for player two - so it is not a specific controller.
| Fix | Where it is done |
|---|---|
| Enable Steam Input explicitly | Steam, game properties |
| Assign devices manually | In-game pause menu |
Two routes, both reported to work. The reporter's own edit says the fix is to explicitly enable Steam Input. A community reply suggests the other half - open the pause menu once you are in the level and manually select which player uses which device, because the default is automatic detection and it misreads in some setups.
Do both. Steam Input first, then assign in the pause menu, and the problem stops recurring.
The multiplayer puzzle-token desync
A second co-op issue is more serious when it happens, because it can look like progression loss: each player having a different number of puzzle tokens.
The reported sequence is a non-host who talks to the headmaster, gets a key, and then watches the host open the locker and take the piece. After that the host shows one piece and the guest shows zero, and the guest is teleported to detention when entering the library. The locker is empty for both.
The developer's reply explains the model and the fix:
- The count is based on the host. The game is peer-to-peer and the host acts as the server for synchronising state.
- Remaking the lobby re-syncs the guest from the host's save. Not replaying the room - remaking the lobby.
- Logs from both players are wanted for diagnosis, through the studio's own support channel.
That behaviour is consistent with how the rest of the game works: quest flags, room unlocks and collectibles all live in the host's save. A guest whose world looks emptier than the host's is usually seeing a desync rather than a bug in their own save.
Playing with someone who does not own it
There is no way to do this. The FAQ says both players need the game, and the same rule extends to the DLC - buying the Season Pass on one account does not unlock the expansions for a partner. What exists instead: Remote Play Together, which streams a local co-op session to a friend through Steam rather than granting a second copy; split screen on one machine, the intended couch route; and family sharing, which shares a library but cannot be used to play the same game simultaneously.
What co-op changes about the puzzles
Three things. Some rooms assume two perspectives - nothing is gated behind co-op, but rooms are built with a second pair of eyes in mind, so a solo player holds more at once. The No-Timer question is sharper, because two people solve at different speeds and the mode exists so the slower partner is not a liability. Achievements are per account, so playing as a guest does not give you the host's achievements, because the state that fires them lives in the host's save.