How hasan-wolf/geekednet works
GeekedNet is a browser networking game: learners build or inspect a network, configure it, send packets, and diagnose failures; lab objectives determine mission completion. The graph separates the React experience, shared app state, simulation/mission engine, and phone/topology experiences. The README documents the shared engine and read-only phone flow; edges from sampled source are limited to references listed in the SOURCE INDEX, so unsampled wiring is not inferred.
Main entry points: store.ts Game state · engine/index.ts Engine API · topologies/index.ts Topology registry · Canvas.tsx Network canvas
Components 29
Learning experience
- Application shell
src/App.tsx - Network canvas
src/components/Canvas.tsx - Device palette
src/components/Palette.tsx - Device catalogue
src/devices.ts - Config panel
src/components/ConfigPanel.tsx - Terminal UI
src/components/Terminal.tsx - Command parser
src/terminalEngine.ts - Objectives view
src/components/Objectives.tsx - Companion hints
src/components/CompanionBot.tsx - Mission results
src/components/WinBar.tsx - Progress tracking
src/progress.ts
App state
- Game state
src/store.ts
Network engine
- Engine API
engine/index.ts - IP addressing
engine/ip.ts - Packet simulation
engine/simulate.ts - Link state
engine/linkState.ts - Mission evaluation
engine/missionRunner.ts - Lab validation
engine/validate.ts
Labs and topology data
- Lab registry
engine/labs/index.ts - Lab definitions
engine/labs - Topology demos
src/components/Topology.tsx - Topology registry
src/topologies/index.ts - Topology definitions
src/topologies/topologies.json
Phone experience
- Phone layout switch
src/phone/usePhoneLayout.ts - Read-only phone view
src/phone/PhoneApp.tsx - Phone network view
src/phone/PhoneCanvas.tsx - Phone packet demo
src/phone/phonePing.ts - Solved lab state
src/phone/solveLab.ts
Other components
- Learner
Connections 48
- Learner → Application shell: uses
README.md - Application shell → Game state: reads and updates
src/App.tsx - Application shell → Progress tracking: derives progress
src/App.tsx - Application shell → Phone layout switch: selects layout
src/App.tsx - Network canvas → Game state: reads and updates
src/components/Canvas.tsx - Network canvas → Engine API: uses simulation API
src/components/Canvas.tsx - Network canvas → Device catalogue: renders devices
src/components/Canvas.tsx - Network canvas → Topology registry: reads topology
src/components/Canvas.tsx - Network canvas → Topology demos: supports topology mode
- Device palette → Device catalogue: lists devices
src/components/Palette.tsx - Config panel → Game state: reads and updates
src/components/ConfigPanel.tsx - Terminal UI → Game state: reads and updates
src/components/Terminal.tsx - Command parser → Engine API: runs commands
src/terminalEngine.ts - Objectives view → Game state: reads objectives
src/components/Objectives.tsx - Companion hints → Game state: reads state
src/components/CompanionBot.tsx - Companion hints → Engine API: uses engine results
src/components/CompanionBot.tsx - Mission results → Game state: reads results
src/components/WinBar.tsx - Mission results → Progress tracking: shows progress
src/components/WinBar.tsx - Progress tracking → Game state: selects progress state
src/progress.ts - Game state → Engine API: evaluates objectives
src/store.ts - Game state → Device catalogue: creates devices
src/store.ts - Game state → Command parser: runs terminal
src/store.ts - Game state → Topology registry: loads topology
src/store.ts - Game state → Solved lab state: derives phone lab state
src/store.ts - Engine API → IP addressing: exports addressing
engine/index.ts - Engine API → Packet simulation: exports simulation
engine/index.ts - Engine API → Link state: exports link state
engine/index.ts - Engine API → Mission evaluation: exports mission runner
engine/index.ts - Engine API → Lab validation: exports validation
engine/index.ts - Engine API → Lab registry: exports labs
engine/index.ts - Packet simulation → IP addressing: uses address math
engine/simulate.ts - Mission evaluation → Packet simulation: checks packet reachability
engine/missionRunner.ts - Mission evaluation → Lab validation: uses lab validation
engine/missionRunner.ts - Lab registry → Lab validation: validates lab data
engine/labs/index.ts - Lab registry → Lab definitions: loads definitions
engine/labs/index.ts - Topology demos → Game state: selects topology
src/components/Topology.tsx - Topology demos → Topology registry: reads topology data
src/components/Topology.tsx - Topology registry → Topology definitions: loads definitions
src/topologies/index.ts - Topology registry → Engine API: uses engine types
src/topologies/index.ts - Topology registry → Topology demos: provides demos
src/components/Topology.tsx - Read-only phone view → Engine API: uses shared engine
src/phone/PhoneApp.tsx - Read-only phone view → Game state: reads app state
src/phone/PhoneApp.tsx - Read-only phone view → Phone packet demo: offers packet demo
src/phone/PhoneApp.tsx - Read-only phone view → Phone network view: renders network
- Read-only phone view → Solved lab state: derives solved state
- Phone network view → Engine API: uses shared engine
src/phone/PhoneCanvas.tsx - Phone network view → Game state: reads app state
src/phone/PhoneCanvas.tsx - Phone packet demo → Engine API: simulates packet
src/phone/phonePing.ts