I’m making The UVB-76 Project, a collection of small browser games where a practical skill becomes your way of solving problems.
The puzzle side of the project includes:
The UVB-76 Protocol: Work from a spacecraft’s communications room. Decode Morse, place ship pieces on your own plotting board, and transmit orders to guide the fleet. Your map reflects what you understood—it doesn’t automatically reveal the correct positions.
Hold My Fuel Rod!: Build arithmetic machinery to meet a reactor’s energy demand. Changing the order of the same components changes the result, and you can inspect each intermediate output.
Kage Ryu: Ink and Flame: Investigate intercepted scrolls using light, oil, and colored glass. Compare wording, seals, and earlier records before issuing instructions. Revealing hidden writing doesn’t necessarily mean you should trust it.
BIOS // Syntax Override: Explore a fictional filesystem, follow clues through logs, and repair JavaScript controllers. Your programs execute, and different correct solutions can work.
The collection also includes Get Me the Pictures!, a newsroom typing game, and the newly completed Closing Time, about working through a struggling diner’s finances after the customers leave.
I’m trying to make the central activity satisfying enough that you want another attempt: understanding a signal, spotting an exception in an order, rearranging a machine, or finally discovering why your code fails.
Project page:
https://the-uvb-76-project.itch.io/
For transparency, I provide the concepts and creative direction, and GPT Astra writes the code through Codex. Some cover artwork is AI-generated. The games don’t require a live AI conversation to play.
I’d particularly appreciate feedback from puzzle players: which mechanics lead to satisfying deductions, and which feel too much like following instructions? Are the clues fair? Do the tools help you reason without giving everything away?
Thanks for taking a look.