Castlevania and the Art of Friction:
When Slow Controls Are a Choice, Not a Flaw

The first time Simon Belmont dies, it's your fault. Not the game's, not a bug, not an unfair enemy. Yours. You jumped without thinking. You whipped a split second too late. You underestimated the Medusa Head coming from the right because you were already eyeing the next platform. And when the knockback sent you into the void, you understood that in Castlevania every action has a cost. At PixelPrompt we reinterpret classic games with AI, rewriting them from scratch for the browser. And Castlevania is one of the titles that taught us the most about design.

Modern game design has a term for all of this: friction. Friction is the number one enemy of contemporary UX. Every extra click, every field to fill, every unnecessary step: remove it. Reduce friction. Make everything smooth. But Castlevania says the opposite. And it's right.

Friction as language: Simon Belmont's vocabulary

Simon Belmont has a minimal movement vocabulary. Walk. Jump. Whip. Use a sub-weapon. That's it. But it's not the scarcity of actions that defines Castlevania's game feel: it's the weight of each one. Every movement communicates consequence.

The jump is the perfect example. In Super Mario Bros, released a year earlier, jumping is fluid: you can correct your trajectory mid-air, modulate height by holding the button, change direction. Mario's jump is an expressive tool: it forgives, adapts, accommodates. Simon's jump is a commitment. Once you press the button, the arc is locked. You can't turn back. You can't adjust. If you jump in the wrong spot, the only thing you can do is whip and hope.

Konami didn't make this choice because of hardware limitations. The NES was perfectly capable of handling air control; Mario already proved that. Simon's rigidity is a pure design decision. Every jump becomes a micro-commitment: you assess the distance, calculate incoming enemies, decide the timing, and only then press. This turns a trivial action into a tactical decision.

“We deliberately made the controls heavier than other games of the time. We wanted every action to be a choice.”

Hitoshi Akamatsu, Castlevania director

Knockback: punishment or feedback?

Castlevania's knockback is the game's most hated and most brilliant mechanic. When Simon gets hit, he's pushed back several pixels. If there's a platform below, you lose some health. If there isn't, you fall into the void and die. Knockback isn't just damage: it's forced displacement. It strips you of positional control, which in a platformer is the most precious resource.

In modern UX, this would be called excessive punishment. A disproportionate negative feedback that discourages the user. But Castlevania doesn't want to encourage you: it wants to teach you. Every knockback is a message: "you shouldn't have been standing there." Next time you position yourself better. You calculate whip distance more carefully. You wait half a second longer before advancing.

Knockback makes space meaningful. In a platformer where you can absorb hits without positional consequences, the level becomes a hallway. In Castlevania, every tile of the floor matters. Standing three pixels from the platform edge is not the same as standing twenty pixels from it. Risk is spatial, not just numerical.

Product lesson: not all friction should be removed

I work in tech and I hear "reduce friction" repeated like a mantra. And it's true: useless friction should go. Nobody wants to fill out twenty fields to sign up for a service. But there's a huge difference between useless friction and intentional friction.

• Useless friction: a registration form with fifteen required fields. The user learns nothing, just wastes time. Remove it.
• Intentional friction: the "Are you sure you want to delete?" confirmation before erasing a project. The user pauses, thinks, decides. The slowdown is the value.
• Formative friction: the interactive tutorial that forces you to complete an action before moving on. It slows you down but builds competence. Just like Castlevania's first level.

Castlevania is built entirely on formative friction. Every screen, every enemy placement, every platform above the void is a puzzle that teaches you to respect the rules. And the rules are few but absolute: don't jump without thinking, don't whip without calculating distance, don't advance without checking what's coming from above.

The most direct parallel in product design? Systems that slow the user down at the right moment to prevent costly mistakes. Git's autosave asking confirmation before a force push. The double verification step before a payment. The email preview before sending. All of these are intentional frictions: they slow the flow to protect the user from themselves. Exactly like Simon Belmont's no-correction jump.

Developer insight: rebuilding Simon's weight with AI

When I started working on the Castlevania interpretation for PixelPrompt, the first thing I asked Claude was: "Implement a platform character that walks, jumps, and attacks." The result? A fluid, responsive character with full air correction. Practically the opposite of Simon Belmont.

The problem is that AI generates code based on the most common patterns. And the most common pattern in 2026 is the modern platform controller: fluid, responsive, with air control. Achieving Simon's rigidity required subtractive work. Not adding features, but removing them with surgical precision.

The first thing I removed was air control. Sounds simple: strip horizontal input during jumps. But the game feel changed dramatically depending on when you locked horizontal velocity. If you locked it at the exact frame of the key press, the jump felt too dry, almost robotic. If you locked it at the takeoff frame (when the character leaves the ground), the player had a tiny correction window that made everything feel more natural, closer to the original.

Then came knockback. The basic physics is a vector: when Simon gets hit, you apply horizontal velocity away from the enemy and vertical velocity upward (a small forced jump). But the values are everything. Too much knockback and the game is unplayable: you fall into the void on every hit. Too little and knockback loses its role as spatial punishment. I spent an entire afternoon tuning two numbers: knockbackVelX and knockbackVelY. Two variables. Four hours.

The most subtle detail? The whip. In the original, Simon's whip has a noticeable delay between button press and when the hitbox becomes active. There are wind-up animation frames (Simon pulls his arm back) before the whip connects. This delay is pure friction: you can't whip reactively, you have to anticipate. When I tried removing those wind-up frames to "improve responsiveness," the game became easier but less satisfying. A weightless whip is a meaningless whip.

“Making a game deliberately slower is harder than making it fluid. AI generates fluidity by default; intentional heaviness you have to design yourself, frame by frame.”

From the PixelPrompt development diary

The legacy of a bold choice

Castlevania isn't the only game with rigid controls. Ghosts'n Goblins, Mega Man (partly), Ninja Gaiden: the NES is full of games where the protagonist isn't weightless. But Castlevania is the one that turned rigidity into identity. Dark Souls owes more to Simon Belmont than most players realize. The weight of attacks, the inability to cancel an animation once started, the spatial punishment after a hit: it's Castlevania with a triple-A budget.

The lesson I carry with me, as a developer and as a product manager, is this: friction is a tool, not a flaw. Like a rallentando in music, like a pause in a speech. The silence between notes is part of the melody. Simon Belmont's weight is part of Castlevania's game feel as much as the candelabras, the hearts, and the Vampire Killer theme.

Next time someone in a meeting says "let's remove this step, it's friction," pause for a second. Ask yourself: is it useless friction or friction that teaches? Is it bureaucracy to eliminate or a guardrail that protects? Simon Belmont can't change direction mid-air. And nearly forty years later, we're still talking about that jump.

If this piece made you want to take apart more classics, at PixelPrompt we do it every week. We reinterpret retro games for the browser, analyze them piece by piece, and share what we've learned. Join the crew: zero spam, just pixels and code.