Storm the House 3

Storm the House 3 is the third and, as far as any source checked here shows, final entry in a series one developer built and kept building across three releases: a stick-figure base-defense shooter where you stand at a fixed spot, aim with the mouse, and shoot down whatever's walking, driving or flying toward your house before the day ends. The developer is credited everywhere — Kongregate, DeviantArt, Armor Games — only as "Ivory" or "IvoryDrive." No source checked for this review could confirm a real name behind that handle, and this review does not repeat any of the several different names that turned up in search results for that query, none of which could be corroborated by a primary source.

What it actually is

The loop is straightforward and the game leans on it rather than reinventing it. Each day is a timed wave of enemies advancing from the left side of the screen toward your house on the right; you aim and fire with the mouse, spacebar reloads, Z or the mouse wheel swaps weapons. Survive to sundown and you spend that day's earnings on repairs, wall upgrades, additional tower slots, better guns and — the mechanic that gives this entry its shape over the previous two — hired gunmen, who fight alongside you and, according to a completionist's walkthrough posted to the Armor Games community forum, start meaningfully carrying fights once you've got 60 or more of them on the field by around day 26. That walkthrough also lays out the weapon progression in concrete terms: a starting pistol, a shotgun bought around day 3, and an endgame rifle nicknamed "Old Glory" bought around day 13 that reportedly carries the rest of the campaign, including roughly a hundred rounds to bring down the campaign's toughest single enemy, a "megazord" boss. New enemy types are introduced every few days rather than all at once — jeeps, jetpack soldiers, fuel trucks, tanks and choppers show up on a steady drip according to that same account — which is a real piece of pacing craft, not just a bigger number on the enemy-count counter.

Structurally, this puts Storm the House 3 in an odd spot relative to the tower-defense wave that was breaking out the same year it shipped. Paul Preece's Desktop Tower Defense, released a year and a half earlier in March 2007, had already popularised a purely placement-driven school of the genre where the player's only input is where towers go. Storm the House 3 keeps the player's own aim as the primary weapon and treats towers and gunmen as support for that aim rather than a replacement for it — closer in spirit to the earlier Storm the House games than to the maze-TD lineage Desktop Tower Defense was founding in parallel. That's a real point of difference worth crediting, even if it isn't presented as one; it's just what the series had always done, refined rather than reconceived a third time.

The campaign, and what it doesn't do for you

A completionist's walkthrough posted to the Armor Games community forum puts the full campaign at 40 days plus a 41st day gated behind badge verification, and estimates roughly three hours to finish it. That's a substantial amount of content for a free browser game from 2008, and the difficulty curve inside it reads as genuinely considered — the same walkthrough singles out day 39 as the point where the challenge spikes sharply enough that, in the author's words, "n00bs lose."

What the campaign doesn't give you is any way to stop and come back later. There is no save function and no continue option once you close the browser tab, and this is not a minor complaint dug up from one forum post — it recurs across Kongregate's own comment thread for the game, with players describing losing an entire run to a single mistake and having no recourse but to restart from day one. For a roughly three-hour campaign with a real difficulty spike near the end, that's a structural gap, not a stylistic choice, and it sits squarely inside a genre where mid-run saves were already standard practice by 2008.

Player comments on Kongregate also describe specific bugs rather than vague dissatisfaction: one account reports an enemy unit that neither the player's guns, hired gunmen, nor towers can kill — a stuck state in a wave-survival game, not a cosmetic flaw. Earlier reports describe a bomber plane that turned invisible after day 20. The developer's own v1.5 changelog, dated 9 November 2008, states only "removed plane altogether." This review does not claim the patch note and the bug report are provably connected — no changelog or developer statement checked spells out the reason for the cut — but the timing and the fix both point the same direction, and it's worth flagging as the kind of thing that happens when a bug proves easier to remove than to fix.

Difficulty tuning outside the main campaign is uneven in the other direction. A separate forum strategy post about the "300" challenge mode — a Spartans-themed scenario, one of several bonus modes alongside a "Zombocalypse" mode referenced in player comments — describes it as "really not hard to beat" once a specific formation of two upgraded fan towers and a flamethrower is in place, with the rest of the fight essentially playing itself. A campaign that spikes sharply at day 39 sitting next to a bonus mode a forum poster calls trivial once solved is not necessarily bad design — the two modes are meant for different audiences — but it does mean the game's overall difficulty curve is less consistent than the campaign's internal pacing alone would suggest.

The toybox underneath the siege

Storm the House 3 also ships a ten-code cheat menu, each code a James Bond film title mapped to an effect — "die another day" is godmode, "from russia with love" is unlimited ammo, "diamonds are forever" is unlimited money, and so on, per a cheat list posted to the Armor Games community forum. None of that is hidden or exploit-based; it reads as the developer building in a deliberate, slightly goofy release valve for players who want to see the later content without grinding sixty gunmen to get there. It's a small thing, but it's evidence of a developer thinking about the game as something people would want to mess around in, not just clear once.

Playability today

This is where the honest answer is "unclear, and worth saying so plainly." Armor Games' own listing for Storm the House 3, checked 5 September 2026, states that the game "is currently not available on Armor Games" because the site's Ruffle-based Flash emulation "doesn't currently work for all games" — and names this as one of the titles it doesn't yet cover. Kongregate's listing page for the game, checked the same day, still shows a "Play Now" button and no Flash-required warning in the page's static content, but this review could not execute the page's embedded player to confirm it actually loads and runs; that would need a live browser check, not a page fetch. A number of third-party mirror and archive sites (among them Bubblebox, evilgames.eu, Flash Museum and Silvergames) also list the game as playable, but none of those were independently verified to run it either. Whether the swf survives in Flashpoint's catalogue specifically could not be confirmed from any source checked for this review. In short: the game is not confirmed dead, but it is not confirmed reliably playable either, and anyone chasing it down today should expect to try more than one host before finding one that actually loads.

Final verdict

Storm the House 3 is a competent, unglamorous refinement of a formula its own developer had already built twice before — a longer campaign, a real enemy escalation, a gunman-hiring economy that gives the mid-and-late game some actual weight, wrapped around the same click-and-aim core the series always had. It earns real credit for pacing a 40-day campaign that a completionist walkthrough describes as building steadily toward a genuine late spike, and for shipping a cheat menu that suggests a developer who wanted the game to be a plaything, not just a grind. It loses that credit back on execution: no save function for a three-hour run, specific unresolved bugs on the record in the game's own comment threads, and a difficulty curve that swings between "loses to n00bs" and "really not hard to beat" depending which mode you're in. That combination is a fair description of a 6.5 — a solid third entry in a series that never asked itself to be anything more than a bigger version of what it already was, held back by exactly the kind of finishing-work gaps that a longer campaign makes more costly, not less.