'Level two' game to set up tools.

OCS Gamified Toolchain Trail

The7Blueprints
Hope Fune, Anishka Sangvi, Kailyn Sanford, Meryl Chen, Anika Marathe, Avantika Chittari, Laya Balaji

Level 2 / Environment Quest

Students are extending the OCS onboarding system to guide students through development-environment setup and verify that their machines are ready for classroom development. The project includes a cross-platform Python verification agent, tool and project checks, GitHub identity, remediation feedback, and integration with the OCS Analytics System. Verification and gameplay results will flow into the existing Java/Spring/SQL backend, where student activity can contribute to status, grading, progress, and regression tracking. The goal is to provide students and teachers with a working-status view of development environments while connecting machine-level activity to the broader OCS learning system.

Team: Hope Fune, Anishka Sangvi, Kailyn Sanford, Meryl Chen, Anika Marathe, Avantika Chittari, Laya Balaji

Planning Board GitHub Repository
6core stations
Toolchain Trail Kanban Board Open on GitHub

Project Stages

Stage 01

Development Environment Verification

View stage details

Improve the existing verifyTools.sh Bash script so it can determine whether a student's development environment is properly configured.

  • Find the repository automatically and verify required tools, files, and project configuration.
  • Give clear remediation steps and a passed, warning, or failed summary with the correct exit code.
  • Keep checks secure, platform-aware, and documented in the README.
Stage 02

Python Onboarding Agent

View stage details

Replace the Bash verification script with a cross-platform Python onboarding agent that produces structured JSON for every verification.

  • Verify development tools, GitHub access, repository setup, and project runtime across supported platforms.
  • Record structured results and connect them to each student's GitHub identity.
  • Track progress, retries, and regressions to gate levels and surface students who need help.

Recent Changes

Choose your system

  • Players pick Windows, macOS, or Linux at the start and can change it any time.
  • Every station then shows the right steps for that system: WSL Ubuntu on Windows, Terminal and Homebrew on macOS, apt on Linux.
  • Each system also has a one-command setup check that only reads versions and settings; it never installs or changes anything.

Toolchain agent

  • The agent is a small Python program on the student's own computer, because a web page cannot run programs there.
  • Students pair it once: the game shows a one-time code that works for 5 minutes, the student pastes it into the agent, and it then runs in the background for the whole trail, even while they install tools in the same terminal.
  • At each station the game asks the agent for that station's checks, such as the pages clone, Python, and Git. The agent reports what it finds, and the server decides pass or fail.
  • A failed check shows the exact fix for the student's system. If pairing is not possible, a Practice Check lets students paste terminal output for feedback.

Spline barriers and road

  • Added invisible barriers along paths and below the score bar.
  • Moved the road beside the buildings; players start at its entrance.
  • The road now loops around the map, with stations in clockwise order.

Sound settings

  • Added voice, volume, speed, and pitch controls.
  • Settings persist across levels and reloads without changing each level's voice style.
  • Choose English, Chinese, or Spanish, plus fun voice effects.
  • Removed the extra effects menu from dialogue.

Saving setup check results

  • One command checks tools, saves results locally, and sends them to the server.
  • Results appear in-game with status, fixes, date, time, and duration.
  • Latest results are stored; manual paste is still available.
  • An AI summary highlights missing setup items.

What We’re Working On

Progress alerts

  • Show student progress and flag failed checks or stalled activity.

Bring the setup flow to other levels

  • Add guided steps, automatic results, and a teacher view to other levels.

Block progression after setup failure

  • On failure, block progress and flash a large red “0.55” until fixed.

Toolchain Trail Stations

1 Terminal Town Gate Station 1
2 Compiler Canyon Forge Station 2
3 Editor Isle Tower Station 3
4 Git Village Hall Station 4
5 GitHub Gateway Arch Station 5
6 Build Bridge Station 6
★ Integration Summit Final gate
View station purposes

Terminal Town Gate

Shell basics and cloning the class repo

Compiler Canyon Forge

Python and Ruby runtimes with pip and Bundler

Editor Isle Tower

VS Code/Cursor and WSL configuration

Git Village Hall

Git installation and configuration

GitHub Gateway Arch

GitHub authentication and repository connectivity

Build Bridge

Project build and runtime verification

Integration Summit (Gated)

Final end-to-end verification

Map Structure

Explore the map plan
  • The player starts at the entrance of a road that loops around the map.
  • Six buildings sit along the road in clockwise order, each representing one development-environment station.
  • Integration Summit is the locked final stop; it opens only after all six stations are complete.
  • Each station has a unique building, floating nameplate, purpose icons, wooden sign, and completion feedback.
  • Integration Summit initially appears desaturated and locked.

Building States

Each station makes its progress visible as students move from setup to verified completion.

1
State 01

Locked

Desaturated with unlit torches and no glow.

2
State 02

Active

Full color with lighting and a glowing entrance.

3
State 03

Stuck

Active appearance with a subtle warning glow.

4
State 04

Complete

Full color with a steady glow and completion indicator.

NPC Feedback & Completion