I built a complete video game in a day. Not a prototype, not a jam toy — a finished, polished, deployed action-adventure, live on the web, playable on your phone right now. Here is how, and why it matters for anyone who wants software built fast without it being built badly.
Nightwatch of the Islands
It is a Zelda-style adventure set on a mythic, historically-accurate Malta. You play as Xemx, a Marsaxlokk harbour cat with nine lives and a guardian’s lantern, crossing the real map of the island — Marsaxlokk, the Hypogeum, Valletta, Mdina, Ħaġar Qim, Mellieħa — to lift a curse of endless night and relight the three great beacons. Every chest holds genuine history: the Great Siege of 1565, the Ħal Saflieni Hypogeum, St Paul’s shipwreck, the Bride of Mosta.
Fifteen hand-authored zones. Three-mode lantern magic. A boss — the Siege Wraith of St Elmo. A standing-stone temple puzzle. An original, fully procedural WebAudio score in a Mediterranean mode (no audio files shipped). Touch controls and an installable, offline-capable app. Saves to your device. Zero dependencies — just HTML, JavaScript and a canvas.
👉 Play it now · Read the full case study, method & references · View the source on GitHub
How do you build a whole game in a day?
The honest answer: I didn’t type most of it. I directed it. I’m “The Human In The Loop” — and the loop is an AI agent fleet that I orchestrate, review, and stay accountable for. The method is the actual product here:
- The human sets direction; agents execute and verify. Every feature started as a paragraph of intent — “like A Link to the Past, but real Malta, and maybe the hero is a cat.” No 40-page spec. Just clear intent, then build and prove.
- Multi-agent adversarial review. After the build, a fleet of reviewer agents attacked the game across four dimensions — engine correctness, world data, historical accuracy, and UX. Every finding was then handed to refuter agents whose only job was to disprove it. Eleven of twelve findings died in verification; the one survivor was a real, nasty pause-state bug, fixed and regression-tested the same hour.
- Headless verification over vibes. The game exposes a test hook, so the entire quest chain — dialogue, puzzles, boss AI, saves, death — was driven and asserted programmatically in a real browser, with exact numbers, not impressions.
- Institutional memory. Decisions, gotchas and architecture live in a shared cross-agent memory, so any agent can resume any part of the work cold.
The honest part
A single unescaped apostrophe — in the word “Mnajdra’s” — silently killed an entire script file. No error, no warning, just a blank screen. It cost real time to find. That lesson (syntax-check after every edit; double-quote your prose) is now baked into the standing method. AI velocity doesn’t remove the need for an engineer who knows where the bodies are buried. It makes that engineer ten times faster.
Why this matters
This is the working proof behind the pitch: high-velocity code, human-centred logic. A one-person studio with an agent fleet ships in days what used to take a quarter — without surrendering accountability, accuracy, or taste. The first players finished the whole quest and sent feedback; a same-week mobile polish pass shipped straight off the back of it. Feedback in, fixes out. That is what keeping a human in the loop looks like.
Nightwatch is open-source (MIT) and free to play. It’s the flagship of MaltaQuest.Online, a heritage-discovery platform turning the Maltese islands into a living quest.
Want something built like this — fast, bespoke, and accountable? Book a Vibe Check. Or just read exactly how it was made and star the repo.
