How dwatkin-dev/set08801 works
CodeQuest is a browser-based interactive debugging game. The player explores room pages, manages health and inventory, obtains a patch, defeats Wumpus.exe, and reaches the Web Core ending. The sampled JavaScript supports the game-state and encounter relationships shown; HTML page wiring and room-by-room mechanics were not sampled, so those links are left unspecified.
Main entry points: core.js Game state logic · patch.js Patch pickup · zap.js Damage event · loop.js Health loss event
Components 12
Game pages
- Game entry
index.htm - Labyrinth rooms
rooms - Room interface
rooms/room_template.htm
Gameplay events
- Patch pickup
JS/patch.js - Damage event
JS/zap.js - Health loss event
JS/loop.js - Health restore event
JS/cache.js - Wumpus encounter
JS/wumpus.js
Game state
- Game state logic
JS/core.js - Session state
Game ending
- Web Core ending
JS/webCore.js
Other components
- Player
Connections 10
- Player → Game entry: starts game
- Player → Labyrinth rooms: explores
- Patch pickup → Game state logic: reads and updates inventory
- Damage event → Game state logic: reads and updates health
- Health loss event → Game state logic: sets health
- Health restore event → Game state logic: sets health
- Wumpus encounter → Game state logic: reads inventory; updates health and defeat state
- Web Core ending → Game state logic: reads defeat state
- Game state logic → Session state: reads and writes
- Game state logic → Room interface: updates status and game-over display