Slayblade spends its whole design budget in the parts shop
4 min read
A battle-top has no moveset. Two objects meet and their properties settle it, which means every decision worth making happened earlier, in a shop, with money you won off somebody else.
The fight is decided before it starts
Slayblade is a run-based battle-tops game. You build a top, launch it at somebody else’s top on a street corner in a miniature Y2K city, and win cash. The cash buys new parts, the new parts change what your top does on contact, and the loop runs again. There are over sixty parts to collect, and the pitch is not that one of them is the good one — it is that their powers merge, and the combinations are yours to find.
The verbs are few and small: pick, merge, launch, spend, bet. The whole game is playable with a mouse and left click, and that is a much louder design statement than it looks. Every input a game declines to give you is a decision that has to live somewhere else. Here it lives in the build, which is why the build is the part you are actually playing.
That inversion is the unusual thing. An action roguelite normally puts its interesting choices inside the fight — which move, which angle, when to commit, when to back off. A top cannot do any of that. It cannot block, feint, or change its mind halfway through a collision. So the properties become the play, and the battle turns into the readout of an argument you finished in the menu.
The city around the fights is doing quieter work. You skate between opponents, bet your lunch money, and take on a rich loser at the top of the ladder, all in lo-fi PS1 geometry with hand-drawn character art. It is billed as chill, and chill is a real target rather than a shrug: if the tension is concentrated in the build screen, the space between builds is free to be pleasant.
Where the decisions actually live
The Two Types of Randomness in Game Design is the essay that explains why a game like this can feel fair at all. Its argument is that luck reads as drama when the dice fall before you decide, and as a swindle when they fall after. A battle-top is naturally the second kind — you commit the build, then the collision happens without you. The fix is to move everything knowable to the near side of that line: you chose the parts, you know what they merge into, and the only thing you are really gambling on is the opponent.
Roguelikes, Persistency, and Progression handles the other half. It argues that what separates a roguelike from a roguelite is whether anything survives your death, and that the answer decides whether a lost run is information or wasted time. Slayblade leads with its collection — sixty-plus parts and a pile of unlockables — which is the tell. The run is disposable, the parts are not, and that is what lets a duel end in seconds without the loss feeling like a scolding.
Secrets of Game Feel and Juice is the one it will be judged on. The developer’s own promise is supremely satisfying controls, and with a single button there is nowhere to hide: the launch has to carry weight, the impact has to land in the ears as well as the eyes, and a part’s power has to be legible in the half-second it fires. Get that wrong and sixty parts is a spreadsheet with a paint job. Get it right and it is sixty different ways to feel clever about a decision you made two minutes ago.
What you actually get
Slayblade is made by [Henry’s House](https://www.henryshouse.com.au) with Oscar Brittain, published by Henry’s House, and out now on Windows, filed under Action, Casual, Indie, RPG and Simulation. It is single-player, with Steam achievements, cloud saves, partial controller support, and a mouse-only option that is closer to the intended way to play than an accessibility footnote.
The store page is unusually straight about scope. No big story mode, just a short intro and outro. Not multiplayer. The replay value is the parts and the unlockables, stated plainly instead of dressed up, which from the developer behind Kardboard Kings and Desert Child reads less like a disclaimer and more like someone who knows exactly which part of his game is the game. The joke about dying in real life is best not taken as a feature list.
If what appeals is a fighting game where the fighter is the variable and your execution is not, Shot One Fighters is the closest relative here — it throws out your entire moveset between runs and makes you win with whatever came back. Slayblade asks the same question from the opposite end: it lets you shop for the build, and then holds you to it.
Keep reading
- The Two Types of Randomness in Game Design
- Roguelikes, Persistency, and Progression
- Secrets of Game Feel and Juice
- Shot One Fighters
One game at a time, with the mechanic that makes it interesting.
More indie game posts