You get one rain-soaked street, sodium light against neon, a full cinematic post stack, and a firefight. There’s no engine, no install, and no download. Click and you’re in.
Type
First-person shooterEngine
Three.js / WebGL (no game engine)Install
None. It’s a URLStatus
Live and playableA tech demo with a gun wasn’t the goal.
This is a graded, art-directed night that happens to be playable.
Browser games have a reputation problem: they read as toys. The point of Operation Blackout was to see how high that ceiling really is. Could a game served as static files from a CDN, with no engine, no bundler, and no install, hold the look of a AAA night mission? The setting is one street, with rain on the asphalt, sodium streetlights fighting neon signage, and enemies pushing a checkpoint in waves. You sprint, slide, aim down the optic, and hold the line.
The constraint was the appeal. Everything a game engine normally supplies had to be written directly against WebGL through Three.js: the renderer’s post stack, the state machine, the HUD, and the enemy behaviour. That keeps the entire build inspectable. It’s fifteen small modules, each owning one system, loaded straight off an import map. There’s no black box anywhere in it.
Art direction was treated as a discipline, not a vibe. The build went through six rounds of blind critique against real stills from a AAA night map. Screenshots of both were put side by side and graded, and the notes fed back into the lighting, the fog, the grade, and the HUD. The honest outcome is part of the story: the AAA reference still wins on micro-detail and characters, but the browser build holds its own on lighting design and interface. For something that weighs a few megabytes and starts in seconds, that’s the argument.
The game is live, free, and linked from this page. It’s also a template. The production brief behind it, with the art direction, structure, and engineering notes, is in the prompt shop, and the build itself is in the template gallery.
Every system is hand-rolled,
because there’s no engine underneath.
The street
The game takes place on a single rain-soaked city street designed as a film frame, with wet asphalt reflections, sodium light against neon signage, and volumetric haze. The sky is procedural, and image-based lighting fills the surfaces without ever leaking into the visible backdrop.
The gunfeel
There’s first-person movement with sprint and slide, aim-down-sights with a real optic, muzzle flash that lights the scene, and enemies that push the checkpoint in waves. The feel was tuned round after round, because feel is the first thing players judge.
The grade
Bloom, film grade, vignette, and fog are part of the game state instead of decoration. The night look is authored in the same place the gameplay lives, and that’s what keeps screenshots looking like film stills.
Architecture
A written architecture contract defines a shared context, one event bus, and strict per-module file ownership. Menus live in the HUD module, and lighting lives in the lighting module. That discipline is what let the build grow through six critique rounds without tangling.
Game states
A proper state machine handles the main menu, playing, paused, and down states. Losing pointer lock pauses the game instead of leaving you firing at a menu. Fullscreen is one key, and death releases the mouse so you can click the redeploy button.
Test rig
A query flag parks the camera on fixed poses with all randomness seeded, so a headless browser can capture pixel-stable frames. Every screenshot on the template page is reproducible from the build itself, which makes QA a feature of the game.
There’s no store, no launcher, and no 40 GB download. A link in a chat message is the whole distribution, and that’s what makes a playable build usable as marketing.
The code is fifteen readable modules instead of an engine’s black box. For a studio selling engineering, the game is the portfolio piece and the code review at the same time.
Grading against real AAA stills, blind and in rounds, replaced taste arguments with evidence. The gap that remained is documented, and so is the ground that closed.
It’s static files on a CDN. Updates deploy in seconds, there’s nothing to patch, and the same pipeline that ships this studio’s websites ships the game.
Captured by the test rig,
so every run gets the same frames.
Questions worth asking
Yes. It’s live at ogtraplord.com/templates/operation-blackout, free, in any modern desktop browser. You need a keyboard and mouse. It’s a shooter.
Because people engage more with a playable moment than with a banner, and a browser game removes the only real barrier: installation. A branded arcade piece that opens from a link works in a campaign, at an event booth, or as the reason people share your URL. This build shows it can also look serious.
Engines win on tooling and raw fidelity. The browser wins on distribution and weight. An engine export to the web ships tens of megabytes of runtime before your first texture. Writing directly against Three.js keeps this build at a fraction of that, so it starts in seconds, and every system in it is code you can read.
A way to make the game hold still. A flag in the URL parks the camera on fixed poses and seeds every random number, so an automated browser can open the game and capture the exact same frame every time. That’s how the lighting was compared across critique rounds, and it’s how you know the screenshots aren’t cherry-picked.
Yes. The exact production prompt behind the build, with the art direction, structure, and engineering notes, is a one-time purchase in the prompt shop. The template page has the full breakdown of what’s inside.
If it can run from a link, it can run in your campaign. That goes for games, interactive pieces, and product demos. Tell me what you’re imagining.
