Structure

Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.

Languages

Share of indexed source by file size. Binary and vendored files are excluded.

Dependencies

Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.

Feature verification

• Action completion tracking with idempotencyVerified

  Action completion tracking with idempotency guarantees

  Claimed on Devposthigh confidence

  • backend/server.js:902 — performAction checks room.completedActions.includes(actionId) and rejects if already completed
• Background music audio playbackVerified

  Not a named Devpost feature, but static mp3 files are present and wired to chase state

  Claimed on readmemedium confidence

  • frontend/src/components/Game.jsx:1072 — audio elements reference static mp3 files in public/audio, toggled by chase state; this is local static audio, not a Fish Audio API integration
• Collision detection with pre-computed collision mapsVerified

  Boundary-based collision system with pre-computed collision maps; canvas-based rendering with dual-layer composition

  Claimed on Devposthigh confidence

  • backend/server.js:76 — Loads frontend/public/data/collisions.js and builds collisionBoundaries used by checkPoliceCollision
  • frontend/public/data/collisions.js — Collision tile data file referenced by both frontend and backend
• Host-based game start authorityVerified

  Host-based game initialization with authority validation

  Claimed on Devposthigh confidence

  • backend/server.js:708 — startGame handler checks room.host !== socket.id and rejects non-host starts
• JLLM API integration with streaming responsesVerified

  JLLM (Janitor Large Language Model) API integration with streaming response handling

  Claimed on Devposthigh confidence

  • backend/server.js:26 — JLLM_API_ENDPOINT and JLLM_API_KEY defined
  • backend/server.js:428 — fetch call to JLLM endpoint with stream: true and chunked reader parsing SSE 'data:' lines
• Keyword-based item transfer and game state transitionsVerified

  Keyword-based semantic parsing for item transfer and game state transitions

  Claimed on Devposthigh confidence

  • backend/server.js:553 — Checks npcResponse.toLowerCase().includes(...) for 'shovel'/'key'/'go ahead' etc. to grant items
  • backend/server.js:583 — triggerWords array checked against NPC response to start a police chase (game state transition)
• Message batching with adaptive response timingVerified

  Message batching system with adaptive response timing (3-second delay or 2+ message threshold)

  Claimed on Devposthigh confidence

  • backend/server.js:832 — pendingMessages buffer accumulates messages; processes immediately at 2+ messages (line 842) or after 3000ms timer (line 848)
• Multiplayer room creation and joining with unique codesVerified

  Unique 6-character alphanumeric room codes; create or join rooms

  Claimed on readmehigh confidence

  • backend/server.js:128 — generateRoomCode() creates a random 6-character uppercase alphanumeric code
  • backend/server.js:636 — createRoom and joinRoom socket handlers create/join rooms by code
• Per-NPC conversation history with 20-message sliding windowVerified

  Per-NPC conversation history buffers with automatic pruning (20-message sliding window)

  Claimed on Devposthigh confidence

  • backend/server.js:489 — npc.conversationHistory sliced to last 20 messages after each response
• Police chase mechanic with pathfinding AIVerified

  Not explicitly in Devpost text verbatim, but implied by 'emergent narrative generation' and gameplay; documented in code as a core mechanic

  Claimed on Devposthigh confidence

  • backend/server.js:133 — spawnPolice and startPoliceAI implement multi-officer pathfinding, collision avoidance, stuck-detection, and catch/lose logic
• Shared inventory system accessible to all players in a roomVerified

  Shared inventory system with room-wide item accessibility

  Claimed on Devposthigh confidence

  • backend/server.js:651 — room.sharedInventory is a single room-level array (not per-player) updated on item transfer and checked in performAction
• Socket.IO event protocol with room lifecycle, movement, NPC interaction, actions, and state eventsVerified

  15+ distinct Socket.IO event types across five functional categories

  Claimed on Devposthigh confidence

  • backend/server.js:632 — io.on('connection') registers createRoom, joinRoom, startGame, playerMove, enterNPCChat, sendNPCMessage, performAction, getGameState, disconnect handlers matching claimed categories
• Support for up to 4 concurrent players per roomVerified

  Support for up to 4 concurrent players per room

  Claimed on Devposthigh confidence

  • backend/server.js:680 — joinRoom rejects joining once room.players length >= 4 and game started
• System prompt engineering for NPC character consistencyVerified

  System prompt engineering for character consistency and behavioral constraints

  Claimed on Devposthigh confidence

  • backend/server.js:38 — Each NPC object has a systemPrompt describing personality and constraints, injected into fullMessages
• Three AI-powered NPCs with distinct personalities and specified locations/inventoryVerified

  Hardware Store Clerk (2842,872, shovel), Police Officer (4106,4306, helicopterKeys), Border Guard (730,4992, borderPass)

  Claimed on Devposthigh confidence

  • backend/server.js:34 — NPCs object defines hardwareClerk/policeOfficer/borderGuard with matching inventory items and personality traits
  • frontend/src/components/Game.jsx:8 — Frontend NPC position config matches exact coordinates (2842,872), (4106,4306), (730,4992)
• Three distinct escape routes requiring specific itemsVerified

  Three distinct escape vectors, each requiring specific inventory items

  Claimed on Devposthigh confidence

  • backend/server.js:884 — actionRequirements maps digSite->shovel, helicopterPad->helicopterKeys, borderExit->borderPass
• Username-prefixed message formatting for multi-participant contextVerified

  Username-prefixed message formatting for multi-participant context preservation

  Claimed on Devposthigh confidence

  • backend/server.js:827 — userMessage content formatted as `${player.username}: ${message}`
• WASD movement controlsVerified

  Use W, A, S, D keys to move your character

  Claimed on readmehigh confidence

  • frontend/src/components/Game.jsx:764 — Movement loop emits playerMove based on key state; keydown/keyup handlers elsewhere in Game.jsx track WASD (consistent with rendered controls)
• Win/loss condition evaluation with immediate broadcastVerified

  Win/loss condition evaluation with immediate broadcast propagation

  Claimed on Devposthigh confidence

  • backend/server.js:608 — checkWinCondition triggers gameWon and emits gameOver; police catching player sets gameLost and emits gameOver
• 2-Player support (README) vs 4-player support (Devpost)Code-supported

  README claims '2-Player Support: Play with a friend in the same room'

  Claimed on readmemedium confidence

  • backend/server.js:680 — Code enforces a 4-player cap, contradicting the README's 2-player claim; the README appears stale relative to the actual (higher) player limit implemented
• Real-time position synchronization via Socket.IOCode-supported

  60 FPS position synchronization with optimized broadcast patterns / real-time movement

  Claimed on Devpostmedium confidence

  • backend/server.js:724 — playerMove handler updates position and broadcasts playerMoved to the room
  • frontend/src/components/Game.jsx:511 — requestAnimationFrame game loop drives movement and periodic playerMove emits (line 764), but no explicit 60Hz throttle or delta compression logic found
• Fish Audio integration for voice/audio generationClaimed only

  fishaudio listed under Built With

  Claimed on Devposthigh confidence
• Sub-100ms latency and other quantified performance characteristicsClaimed only

  Latency: Sub-100ms message propagation; Throughput: 60 FPS with delta compression; AI Response Time: 2-5 seconds

  Claimed on Devposthigh confidence

An AI agent derived these features from the project’s Devpost page and readme, then searched the code for each one. Verified features are backed by cited code; claimed-only features had no supporting code, which is not by itself proof a feature is missing.