Bombuzal: The Puzzle Game That Blew Up Its Own Floor

Bombuzal, designed by Antony Crowther, credited in the game as “Ratt”, and David Bishop for Image Works, arrived in 1988 for the Commodore 64, Amiga and Atari ST, with an MS-DOS port following the next year and, further down the line, a Super Famicom release renamed Ka-Blooey for its 1992 North American appearance. Underneath all of that, the design is stark and uncomplicated to describe: a player moves a small character across a grid of tiles littered with bombs, and the objective of every one of its 130 levels is the same, detonate every bomb on the level, without falling off the platform or getting caught in a blast.

The mechanism for detonation is where the actual game lives. Standing on a bomb’s tile and holding the action button starts a three-second countdown. The player then has exactly one step to get clear before the bomb explodes, and any other bombs sitting on tiles adjacent to that blast detonate too, in a chain reaction that can clear half a level in one move or, mistimed, take the player out along with it.

The fuse is the whole design document

Almost every interesting decision in Bombuzal traces back to that three-second window and the one-step rule that follows it. Lighting a bomb is a commitment: the player has three seconds to be somewhere specific, and exactly one further step of positioning to reach cover once the countdown ends, which means a level’s layout has to be read in advance for viable escape routes before a single bomb gets lit. Light the wrong bomb first, in the wrong position, and there may be no tile available within reach to survive the blast, let alone the chain reaction it triggers among neighbours.

That constraint turns Bombuzal into a sequencing puzzle disguised as an action game. The bombs on any given level are rarely meant to be detonated in an arbitrary order; the intended solution usually specifies, implicitly, which bomb has to go first to create both the chain reaction that clears the most tiles and the escape route the player needs to survive triggering it. Levels that look, on first inspection, like an unsolvable cluster of adjacent bombs are frequently solvable in exactly one sequence, and working that sequence out from the static layout, before committing to the first detonation, is the actual test the game is running.

Rails, and the bombs that refuse to stay still

Not every bomb in Bombuzal is fixed in place. Some sit on rail tiles, which allow the player to push and reposition them before lighting anything, turning a subset of each level’s puzzle into a sliding-block problem layered on top of the chain-reaction problem the rest of the level presents. That combination matters because it means a level that looks unsolvable with bombs left in their starting positions may become solvable the moment a rail-bound bomb is nudged one tile closer to a neighbour it previously could not reach in a chain. The rails are the closest thing Bombuzal has to a tool the player actively wields, as opposed to a hazard purely to be read and navigated around, and the best levels use them sparingly enough that a player has to notice a rail tile is even present before the intended solution becomes visible.

The early levels withhold rail tiles almost entirely, which is a deliberate teaching choice rather than a missed opportunity: a player who has only ever solved fixed-bomb layouts arrives at the first rail-equipped level with a settled mental model of how the puzzle works, and the rail’s arrival forces a small, pointed revision to that model rather than dumping the full rule set on a player who has not yet earned the fixed-bomb fundamentals. That staged introduction of a second mechanic on top of a well-understood first one is a harder trick to pull off convincingly than adding both at once, because a player has to actually feel the gap the new tool closes rather than simply being told a new tool exists.

Two views of the same grid

Bombuzal offers both an overhead and an isometric viewing option, a choice unusual for a puzzle game of this era to bother building in at all, since most titles committed to a single fixed perspective and left it there. The overhead view reads more like a traditional grid puzzle, clean and diagrammatic; the isometric view sells the sense of a real, precarious platform suspended over open space, at some cost to the instant legibility of exactly which tiles are adjacent to which. That the game bothered to support both suggests Crowther and Bishop understood their puzzle worked on paper, as pure grid logic, and were using the isometric presentation to add atmosphere on top of a design that did not actually depend on it to function.

130 levels of an idea that never needs a twist

What is notable about Bombuzal’s sheer level count is how little the underlying rule set changes across all 130 of them. There is no new mechanic introduced at level fifty that reframes what came before, no late-game power-up that changes the fundamental question a player is answering. Every level is still, at bottom, the same three-second fuse and the same one-step escape rule, applied to a new arrangement of tiles, rails and bomb positions. That restraint is a deliberate design bet: rather than widening the rule set to manufacture novelty, Bombuzal trusts that a single, well-understood mechanic can generate 130 genuinely distinct problems purely through layout, and for the most part that trust is rewarded. The puzzles get harder by getting denser and more interdependent, not by asking the player to learn something new.

The density increase is the actual difficulty curve, and it is worth being specific about what that means in practice: early levels typically ask the player to work out one, maybe two viable detonation orders among a handful of bombs with generous surrounding clear space, while the later levels pack bombs and rails close enough together that a single misplaced first detonation can strand the player with no legal sequence left to complete the level at all. That is a much less forgiving kind of difficulty than adding a faster enemy or a tighter timer, because it punishes the planning stage rather than the execution stage, and a player who has not internalised the habit of reading a level fully before touching anything will simply fail later levels repeatedly without understanding why.

Where it sits among the era’s puzzle games

Bombuzal’s insistence that every failure is legible in advance, that a level’s solution can in principle be worked out entirely by looking at it before acting, puts it in useful company with Boulder Dash: The Grid That Taught Physics, another mid-1980s puzzle game built around a simple physical rule, falling rock rather than a spreading blast, that a careful player can reason through completely before committing to a move. It is also worth reading against Lode Runner: The Puzzle Game Disguised as a Chase, which shares Bombuzal’s interest in a grid that punishes a wrong sequence of actions severely, though Lode Runner adds pursuing enemies that Bombuzal’s calmer, purely environmental hazard set deliberately does without. Comparing the three is a useful way of seeing how much variety 1980s puzzle design achieved from a genuinely small set of underlying physical metaphors: falling, chasing, exploding.

The case against it

Bombuzal’s central bargain, that every failure is legible in advance if the player looks hard enough, only holds if the player is willing to do that looking, and a three-second fuse that cannot be paused or reconsidered mid-count is an unforgiving way to test a hypothesis about a level’s solution. Get the read wrong and the usual result is a full restart from the level’s starting layout, since there is no partial credit for detonating six of a level’s eight bombs correctly before an error strands the player on a tile with nowhere left to go. That restart cost is defensible as a puzzle-game convention of its era, but it means a level that takes thirty seconds to solve once a player has worked out the sequence can easily cost fifteen or twenty minutes of repeated attempts to reach that solution in the first place, and the game offers no in-level hint, undo, or partial-state save to soften that arithmetic.

The isometric view, for all the atmosphere it adds, is the other place the design’s own ambition works against it: a game whose entire appeal rests on a player correctly reading tile adjacency before committing to a detonation is not well served by a perspective that makes adjacency genuinely harder to judge at a glance, and a player who defaults to the isometric view for its mood is quietly making the puzzle harder for themselves without necessarily realising that is the trade they have made. Neither of these is a design failure exactly, both flow directly from choices that also make the game distinctive, but a modern player used to generous retry loops and clearer failure states should go in expecting a puzzle game that asks for patience the genre has since largely stopped demanding.

Where to play it now

Bombuzal’s Amiga and Atari ST versions are the most visually generous of the original releases and the easiest to find running well in modern emulation, though the Commodore 64 original holds its own for anyone who prefers that machine’s sound and colour handling. The MS-DOS port from 1989 is a reasonable alternative for anyone working from a DOS emulator rather than a dedicated 8-bit or 16-bit setup, and plays identically to the earlier home-computer versions in every respect that matters to the puzzle design itself.

Spoilers below

The later stretches of the 130-level campaign lean increasingly on rail-bound bombs whose correct final position is not obvious from a level’s starting layout, which means levels that look solvable through chain reactions alone, ignoring the rails entirely, frequently are not. Players who have spent the earlier levels treating rail tiles as optional flourishes rather than load-bearing parts of a solution will hit a wall in the game’s second half, where several levels are constructed specifically so that no arrangement of the fixed bombs alone produces a viable chain, and the rail-bound bomb has to be repositioned first before any detonation sequence becomes survivable. The fix, learned the hard way by most players who reach this point, is to treat every rail tile as a question the level is asking before treating any fixed bomb as an answer.