ONE OF YOUR
TEAMMATES
IS LYING.

HOW IT WORKS

PHASE 01 — CREATE ROOM

The mission begins when an agent creates a secure game room. You select your preferred programming language — Python, JavaScript, or C++ — and set the difficulty level (Beginner, Intermediate, or Advanced). The system generates a unique encrypted room code that you share with your team. As the room creator, you control the lobby: you can set the maximum number of players (4–8), configure the match timer, and monitor who joins. The room exists in a standby state until the minimum player threshold is reached, at which point the launch sequence is initiated. Think of this as your secure operations base — classified, controlled, and ready for deployment.

PHASE 02 — ASSEMBLE TEAM

Players join the room using the encrypted room code shared by the creator. As agents enter the lobby, their avatars appear in the staging area. The lobby displays each player's name, skill indicator, and chosen language. Players can see who's in the room but cannot yet see roles — no one knows who will be the imposter. The chat is open during this phase, allowing the team to coordinate and strategize before the mission begins. Once the minimum player count is reached and the creator initiates launch, the team is locked in. There's no turning back. The operation is go.

PHASE 03 — ASSIGN SECRET ROLES

The most critical moment of the setup phase: role assignment. The server randomly designates one or two players as imposters — the exact number scales with room size. Every other player receives the Good Coder designation. Roles are displayed privately to each player via an encrypted modal. Good Coders see: "ROLE: DEVELOPER — Collaborate. Complete the mission. Find the imposter." Imposters see: "ROLE: IMPOSTER — Sabotage the code. Avoid detection. Win." No one else can see your role assignment. This is the last moment of certainty. From here, trust becomes a strategy, not a given. The game clock starts immediately after all players confirm their roles.

PHASE 04 — CODE TOGETHER

The game is live. All players share a synchronized code editor where a pre-set programming challenge awaits. The challenge is modular and complex — multiple functions, logical dependencies, intentional bugs, and incomplete components. Good Coders work collaboratively to fix, complete, and optimize the code. They also receive individual mini-tasks in their personal task panel: fix this specific bug, complete this function, debug this snippet. Completing tasks fills the team's shared progress bar. Meanwhile, imposters pose as helpful contributors while secretly inserting bugs, triggering sabotage events, or sending misleading hints. Every change in the shared editor is visible to all players in real time. Watch the cursors. Watch the edits. The imposter is active.

PHASE 05 — FIND THE IMPOSTER

At any point during the match, any player can call an Emergency Meeting. All coding pauses. The chat opens fully. Players discuss suspicious behavior — who edited that function incorrectly? Who added that rogue loop? Who was idle during the critical section? Evidence is presented. Accusations are made. After a timed discussion, a vote is cast. The player with the most votes is eliminated and removed from the match. If the eliminated player is the imposter, Good Coders win instantly. If an innocent developer is eliminated, the game resumes with the team now one member shorter. The tension escalates. The imposter grows bolder. Or does the evidence trail lead to their exposure? Only one outcome is possible. Mission complete — or mission failed.

EXPERIENCE A MATCH

Play through a guided demo match against bots. No account needed. Takes about 2 minutes.

ROLE DOSSIERS

BLOG & ARTICLES

Field reports, research briefings, and developer dispatches from the Devception team.

INTEL BRIEFING

18 answers to your most pressing questions.