A behind-the-scenes look at the design decisions, dead ends, and bug hunts that shaped the game.
Most arcade games start with a single verb. Jump. Shoot. Match. Veatris started with a stranger idea: what if the thing you do with your fingers on the keyboard and the thing you do in your head at the same time were pulling in two completely different directions? This page is the story of how that idea became a playable game, and of the small design battles we fought along the way. It is written for anyone curious about how a browser game actually gets built, one decision at a time.
The block puzzle is one of the most refined game forms ever made. It is calm, spatial, and forgiving of thought. Speed typing is almost its opposite: it is urgent, linear, and punishing of hesitation. We kept coming back to a simple question. What happens if you force a player to hold both of those mindsets in one head at once?
The honest answer, in the earliest prototype, was chaos. But it was interesting chaos. Stacking blocks uses the slow, planning part of your attention. Typing falling letters hijacks the fast, reactive part. When both demand you at the same second, you feel a very specific kind of pressure that neither game creates alone. That pressure became the whole point. Veatris is not a typing game with blocks bolted on, and it is not a block game with a typing minigame. It is the friction between the two that makes it worth playing.
Early on, letters that reached the bottom simply cost you points. It worked mechanically, but it felt hollow. A number going down is not a threat you can feel. So we gave the falling letters something to destroy: a City Wall of five segments standing behind your field. Every capsule that slips through breaks one segment, and when the wall is gone, the run is over.
That single change reframed the entire game. Suddenly the player was not chasing a score, they were defending something. It gave the typing layer real stakes and it gave the whole game a quiet allegory we grew fond of: the blocks are the physical weight the world drops on you, the letters are the tangled problems and unanswered questions that slip in between, and the wall is what you are trying to protect while you deal with both. We did not set out to build a metaphor. It emerged from a design fix, which is often how the best parts of a game arrive.
By the time the game had stages, items, combos, and even a rare hidden block for veterans, it played well. But when we sat down and pushed deep into a run, something felt off in a very specific place: roughly stages thirteen through fifteen. The early game teaches you. The very late game overwhelms you. The middle, though, was just quietly getting faster, and nothing else about it changed.
This is one of the most common traps in difficulty design. Raising the speed is the easy lever, so it is tempting to lean on it alone. But speed only scales tension in one dimension. Past a certain point the player has already adapted to fast, and further acceleration stops feeling like a new challenge and starts feeling like the same challenge with less air. The mid-game was not too hard or too easy. It was flat. It needed a new idea, not a bigger number.
We wanted the new idea to grow out of what already made Veatris special, not to feel bolted on. The typing layer had always destroyed falling letters. What if, in the mid-game, typing could reach down and reshape the blocks you had already stacked?
That thought became the Bomb Capsule. It looks like an emoji instead of a plain letter, it falls like any other capsule, and when you type its word it detonates inside your tower of blocks. We deliberately gave it four different blast shapes rather than one. A single explosion type would have become routine within minutes. Four shapes, each signaled by its emoji, turned every bomb into a small reading test: what mess do I have right now, and which blast actually solves it? That question is exactly the kind of moment the flat mid-game was missing. It rewards the player for looking at the board and thinking, instead of just typing faster.
Crucially, we made the bomb forgiving. If you miss it and it lands, nothing bad happens to your wall. A powerful new tool that also punished you for failing to use it would have made the mid-game more stressful, not more interesting. The bomb is an opportunity, never a trap.
Adding a mechanic that carves holes in an existing block field is exactly the kind of change that looks simple and then quietly breaks three other systems. It did. Each bug was worth the trouble because each one exposed an assumption we had not noticed we were making.
The very first version blew a hole in the middle of the tower and left everything above it floating in mid-air, suspended over the gap like a bad magic trick. The blast was deleting cells but nothing was told to fall into the empty space. The fix was to add a gravity pass after every explosion that compacts each column downward, so the surviving blocks settle naturally into the crater. It is obvious in hindsight, but it is a reminder that in a grid-based game, destruction and gravity are two separate responsibilities, and forgetting the second one leaves the world hanging.
The next problem was more subtle and, honestly, funny to watch. The bomb was detonating the instant you pressed the first letter of its word, long before you finished typing it. It made the mechanic feel twitchy and unearned. The cause was that the input handler was treating any matching first key as a trigger. The fix was to require the full word, typed in order, before the bomb fires, matching how the rest of the game already handles multi-letter capsules. Consistency, it turned out, was the real fix. A special mechanic that breaks the game's own input rules feels wrong even when the player cannot say why.
The strangest bug came last. After a bomb went off, dropping a new block sometimes triggered a phantom line clear seconds later, as if an old explosion were echoing. The gravity pass was correctly settling the blocks, but it was not checking whether that settling had completed any full rows. Those completed rows sat invisible until the next hard drop finally ran the line-clearing routine and swept them away, producing a clear that felt like it came out of nowhere. The fix was to run the line check immediately after the post-explosion gravity, so a bomb that completes a row rewards you right then, in the same satisfying beat as the blast. There was also a smaller cousin of this bug hiding in our debug tools, where a subtle operator ordering mistake made a test spawner repeat the same bomb instead of cycling through all four. Both bugs shared a lesson: when you add a new way to change the board, every system that reacts to the board has to be invited to the party at the right moment.
The Bomb Capsule did more than patch a flat stretch of stages. It reminded us that good difficulty comes from new decisions, not bigger numbers, and that the most satisfying mechanics are the ones that let one part of your game reach across and touch another. It also reminded us that shipping a feature is only half the work. The other half is the unglamorous hunt for the ways it quietly breaks everything it touches.
Veatris is still growing. There are ideas we are circling, from fever states to word chains, and there is a rare block out there that most players will only ever hear rumors about. If you want to see how the mid-game feels now, the best way to understand a design decision is always to play it.
▶ Play Veatris Now