Task list

Lock down the rooms, equipment zones, and teaching-relevant environmental details so the space feels believable without distracting from the networking work. This milestone is about deciding what the student can move through, inspect, and use before more device logic gets layered in.

• Confirm the main room layout, server room location, hallway access, and workstation placement.
• Walk the player path from workstation to wall jack to rack and remove tight turns or confusing dead ends.
• Tune indoor point lights so equipment labels, port panels, and workstation screens remain readable in WebGL.
• Add consistent labels for rooms, racks, wall jacks, patch panels, switch ports, and student workstations.
• Verify scale for doors, desks, racks, cable trays, and player camera height.
• Review collisions on racks, chairs, desks, walls, and equipment so navigation feels smooth.
• Keep only props that support networking context, classroom realism, or player orientation.

Create one reliable switch-router-patch-panel path that can become the interaction test bed for the rest of the simulator. This path should prove that a student can inspect physical equipment, select ports, understand labels, and see visible feedback when links change.

• Create a 24-port switch prefab with individual clickable or targetable port regions.
• Add one router or upstream device with a small set of meaningful interfaces.
• Connect switch ports to patch panel endpoints with clear labels that match the room wall jacks.
• Create cable visuals that show connected, disconnected, and wrong-port states without cluttering the rack.
• Add LED states for link, activity, disabled ports, and no cable present.
• Add close inspection framing so the player can read labels and select ports comfortably.
• Finish rack door open, close, and inspection behavior.
• Show immediate visual feedback when the student changes a connection.

Make visuals, workstation screens, and CLI output read from the same project data so the world behaves consistently. The goal is a simple source of truth: every cable, port, device state, workstation symptom, and success condition should come from the simulator model instead of separate one-off scripts.

• Define core device records for workstations, switches, routers, patch panels, wall jacks, and servers.
• Track interface names, port numbers, labels, power state, admin state, link state, and connected cable ID.
• Give racks, wall jacks, patch panel ports, and workstations matching endpoint IDs.
• Represent cable objects in data so cable visuals and network state stay synchronized.
• Add a first-pass VLAN or network segment field for later lessons.
• Generate simple CLI responses from simulator state, including link status and basic ping results.
• Add fault presets for disconnected cabling, wrong-port cabling, powered-off equipment, and disabled interfaces.
• Define success checks that compare the current simulator state against the lesson goal.

Complete the first playable troubleshooting exercise: Lab workstation 2 cannot reach the server. This milestone ties the environment, interactions, and state model together into a short lesson that can be tested by someone who has never seen the project before.

• Show the failed workstation connectivity symptom on the screen with a clear but realistic message.
• Add a short scenario brief that tells the student what is wrong without revealing the fix.
• Guide inspection from workstation 2 to its wall jack, patch panel label, switch port, and server path.
• Provide readable clues through labels, LEDs, cable placement, and workstation feedback.
• Let the student correct the cable, port, or device state through the normal interaction system.
• Require verification with a workstation check, ping, or CLI command before marking the scenario complete.
• Show a simple completion state that confirms the network path is working again.
• Run a playtest pass and note where the student gets lost, misreads labels, or misses feedback.