Thick As Thieves Solo, Co-op, and Campaign Scope Guide

Quick Mode Answer

The best current summary is that Thick As Thieves supports both solo play and online co-op with one partner. That is not speculation. The official FAQ says the game is playable solo or with a partner in crime in co-op multiplayer, and Steam lists single-player, multiplayer, co-op, and online co-op. That combination is important because it tells readers this is not a co-op-only experiment and not a purely solitary stealth sim either.

The page should stay disciplined here. Readers searching for co-op answers usually want certainty, and the wrong move is to stretch a Steam tag into features that no official source has named yet.

Solo Versus Co-op

The interesting design question is not whether solo and co-op both exist. It is how the game is likely to feel in each mode. In solo, your play rhythm will probably center on personal timing, patience, and recovery from mistakes. In co-op, the obvious advantage is shared coverage: one player can watch patrols or exits while the other commits to the objective. Trailer footage and the current marketing tone strongly suggest that teamwork is part of the appeal, but the game is still sold as a stealth campaign first, not a chaotic extraction shooter.

That means the best launch-day advice is to choose your first run based on learning goals. If you want to understand the layouts, pressure, and tool timing, start solo. If you mainly want social problem solving and improvisation, start in co-op. What should not be assumed yet is that co-op automatically makes every contract easier. Early hands-on preview coverage suggests harder content can make communication more important, which fits the design: two players give you more information, but also more chances to desync.

The Two Playable Thieves

The official developer walkthrough presents two playable thieves: the SPIDER and the CHAMELEON. That is a useful answer for search users because it turns the vague "solo or co-op" promise into a more concrete choice. The SPIDER reads as the more direct thief fantasy for players who want to focus on movement and execution, while the CHAMELEON framing suggests a different style built around misdirection and social stealth. The page should still avoid pretending we know a final tier list before launch testing.

Campaign Scope Today

Megabit's current release messaging describes Thick As Thieves as an introductory campaign with 2 dynamic replayable maps, 3 mission types, 16 contracts, at least 4 hours of content, and high replayability. That wording matters. It tells readers that the launch build is scoped and focused, not pretending to be a hundred-hour forever game. For user trust, this should be explained as a strength or limitation depending on taste, not spun as a hidden massive game.

Four hours also should not be read as a strict full-completion ceiling. In stealth games, route learning, difficulty variation, contract replays, and gear experimentation can stretch a short main path into much more time. A careful first pass can easily be slower than the headline number if you are checking routes, restarting errors, and testing alternative entries. The safe public claim is that the official campaign scope is modest but intentionally replayable.

What Co-op Players Still Need to Test

Launch-week testing should answer the practical questions the store page cannot. Does the host own all story progress, or do both players retain completion state? Is there join-in-progress? Can a disconnected partner re-enter a contract without restarting? Are there invite-only rooms, public lobbies, or friend-code flows? Does each player need to own a copy on the same storefront? None of that is documented clearly enough in the sources reviewed so far.

This is exactly where launch-day content can still be useful. Instead of pretending those answers exist, the guide can help readers prepare their own checklist. If you are planning a day-one session, test one short contract before committing a whole evening. Confirm voice chat plan, controller setup, and who hosts. That is the kind of advice that respects the reader's time while the live-build details are still being verified.