Tactical Escape 101 · Web Developer
The web layer for the escape rooms: a public front end where customers sign the intro waiver and check the schedule, plus a live game-master console that pushes a countdown timer and typed clues onto the screens players see inside each room.
Two connected experiences: the public-facing site for customers, and a private console the game master uses to run a session in real time.
The front page is where customers go to sign the introduction waiver, and from there they can reach a schedule of available rooms (driven from a separate, scroll-controlled admin view).
The clue system is the live half. When a game master logs in with the room password and selects a room, they get a console — on their own phone or computer — for typing clues. Inside the room, a Raspberry Pi connected to a TV and set to full screen shows the matching customer view: the game master can start, stop and reset the countdown, and any clue they submit appears instantly on the in-room screen, regardless of which machine is driving it.
The two views below are embedded from the original production system. The clue console (top) is what
a game master types into; the in-room screen (bottom) is what players see — text submitted on one
appears on the other. The demo backend is unparsed, so symbols like " ( ) ' [ ] will
report an error rather than send.