This post is a high-level tour of what went into it. The full dev log goes deep on every system — with annotated code, architecture diagrams, and the hard-won lessons from each step.

The Zero-Dependency Bet

The entire project — ~3,200 lines of JavaScript across 9 modules — runs with zero external libraries. No React, no Phaser, no Howler.js. Every system was built from first principles: a 20×14 tile grid, a waypoint-based pathfinding system, a 60fps game loop with a wave state machine, and a full UI layer including a tower upgrade panel and enemy bestiary.

The reason wasn't stubbornness — it was education and performance. Building directly on the Canvas API forces you to understand what's actually happening at every layer of abstraction. And at 45KB unminified, the game loads instantly.

Five Towers, Ten Enemies, Fifteen Waves

The gameplay is built around five elemental tower types — Ember, Frost, Storm, Vine, and Arcane — each with three upgrade tiers and distinct targeting behavior. Towers use a "closest to nexus" priority system, automatically focusing fire on the most dangerous threats.

On the enemy side, ten unique shadow creature types march across the map across 15 increasingly difficult waves, from fragile Shadow Wisps in Wave 1 all the way to the Shadow Dragon boss encounter. Status effects — Frost's 40% slow, Vine's poison-over-time — stack together to create real strategic depth. A Frost + Vine combination is particularly brutal.

Every Visual Asset Was AI-Generated

This is where things get unusual. All 18 visual assets — five tower sprites, ten enemy sprites, and three dynamic map backgrounds — were generated using AI image tools. No hand-drawn pixel art. No asset store purchases.

The process wasn't just "prompt and paste." Maintaining visual consistency across 18 separate generations required a locked style anchor in every prompt: "dark fantasy, pixel art aesthetic, top-down perspective, glowing magical effects." Background removal and per-sprite brightness calibration still required manual passes. The full pipeline — prompt engineering, generation, post-processing, and integration testing — took roughly 40 total generation attempts to get right.

The map backgrounds themselves are a standout feature: the environment transitions through three distinct themes (Enchanted Forest → Crystal Caverns → Volcanic Wasteland) as players advance through wave ranges, giving a real sense of escalating stakes.

Every Sound Is Synthesized in Real Time

There are zero audio files in this project. Every sound — tower attack effects, enemy death pops, UI clicks, the upgrade fanfare, the wave horn, background ambient music, and the victory and defeat jingles — is synthesized procedurally using the Web Audio API's oscillators and gain nodes.

This was the system I'm most proud of, and also the one with the most unexpected engineering rabbit holes. Chrome's autoplay policy means you cannot create or resume an AudioContext before user interaction, full stop. The fix required lazy-initializing the audio context on the first user gesture, with careful ordering to ensure ensureContext() was always called before any early-return checks. It's a subtle bug that's easy to introduce and frustrating to debug.

Dynamic Tower Rotation and the Polish That Makes It Feel Real

Three late-stage additions transformed Arcane Bastion from a working prototype into something that actually feels like a game: AI-generated map backgrounds (replacing flat procedural tiles), glow auras on tower sprites, and smooth dynamic tower rotation.

Every tower continuously rotates its sprite to track its current target using angle interpolation with a lerp factor of 0.15 per frame. A +π/2 offset corrects for the fact that sprites default to "facing up" while Math.atan2 returns 0 for "facing right." A subtle recoil displacement on each shot ties the visual and audio feedback together. None of this affects gameplay mechanics — but it's the difference between a tech demo and a game.

Want the Full Breakdown?​

The complete dev log on InstantGames covers all ten systems in full detail — including the in-browser video recording pipeline (MediaRecorder + Web Audio capture + Playwright + ffmpeg), the module architecture, the wave design philosophy, and the complete lessons-learned section. It's a ~15-minute read aimed at developers who want to understand not just what was built, but why each decision was made.

You can also play Arcane Bastion directly and browse the rest of the projects on InstantGames.top — an indie game dev site where I build and ship browser games, write dev logs, and experiment at the intersection of game development and AI tooling.

Here's a breakdown of what I did and why for the key writing choices:

Hook and framing.​ The opening leads with a concrete, curiosity-driving question rather than a feature list. "Zero dependencies" is a counterintuitive claim that earns a click.

Section structure.​ Each section distills one major system into its most interesting insight — the kind of thing a developer would want to share with a colleague. This respects the reader's time while making the full dev log feel like a worthwhile destination for the deep dive.

Link placement.​ The full dev log link appears in the intro, in the body, and in the closing CTA — three natural placements without feeling spammy. The site homepage link appears twice, anchored to specific actions (play the game, browse projects) rather than generic "visit my site" language.

Tone.​ Written in first-person developer voice to match the Hashnode audience — technically literate, curious, and allergic to marketing fluff.