Mario jump grew extra results

Mario jump is the standard example of a versatile verb, and it did not start that way. In Donkey Kong, Nintendo, 1981, the leap is plain. You hop from a standstill or a run, and the arc is not yours once you leave the ground. One input, one result. Later games let you steer, cut the jump short, bounce on a foe, and reach a ledge you had no right to trust. Same button. More outcomes.

A verb with one result is a button. A verb with several, depending on timing and place, is a vocabulary. The levels can then be written in that vocabulary instead of inventing a new button for every idea. The failure mode is a jump so buried in special cases that the player cannot predict it. Versatility still has to be learnable. Donkey Kong was learnable and thin. The later jump is learnable and thick. Thickness without predictability is just noise.

A single verb becomes interesting the moment it stops producing a single result. Mario's jump is the standard example, but it did not start that way. In Donkey Kong the leap is plain: Mario can hop from a standstill or while running, the arc cannot be steered once he leaves the ground, and the animation looks the same every time.

Call an action the player can perform a verb, and that early jump is about as thin as a verb gets. Press the button, get the action. Nothing the player does before or during the press changes the answer.

Now put a modern Mario next to it. Height, length, angle, landing point, and the relationship to every other move are all in play. He kicks off walls, bounces off shells, converts a crouch into a backflip, turns a run-up into a long jump, and strings ground pounds into rebounds.

None of that comes from adding buttons. It comes from letting one action resolve differently depending on timing, movement, how hard the button is pressed, and the situation it is pressed in. That is what a versatile verb is.

Verbs live on buttons, so the useful question is what a press, a hold, a release, and a second press each mean. Weak designs answer that question once and repeat the same action. Strong ones use the hold to force a choice.

Mega Man X shows it cleanly. Tap fire and a small pellet leaves the gun straight away. Keep the button down and a heavier blast charges instead, and with the right upgrades a longer hold builds something stronger still. The shot goes off on release.

One input now carries a trade. Take small damage now, or gamble on bigger damage in a second. Charging exposes the player to a hit before the shot is ready, which is exactly what makes committing to it feel like a decision.

Cooked grenades run on the same structure. Throw immediately and the grenade bounces and detonates on its own schedule. Hold it first and it goes off in the air or on contact instead. Hold it a beat too long and the threat comes back to the thrower. The button never changes, only the window.

Variable jump height is the quiet version of this in Mario. A tap gives a small hop, a hold gives more air. It looks like nothing written down, but it is why the jump feels alive: the player is still shaping the action after it has already started.

Some of the best verbs put the interesting decision in letting go rather than pressing. Luftrausers builds its whole loop out of that. Hold the button and the plane fires; stop firing and the plane starts repairing itself.

Offense and defense end up sharing one verb. Firing makes you dangerous and fragile at once, and releasing buys back health while handing enemies room to move. The game turns into a rhythm of pushing and easing off.

The throttle works the same way. Sharp turns require letting go, so the moment-to-moment feel becomes press, release, whip around, fire again. A lot of the thrill is in having the nerve to stop doing the obvious thing.

Dark Souls plays a slower version. Stamina crawls back while the shield is up, so recovering quickly means dropping the guard and eating the risk. The real question is not whether to block. It is when to stop.

MotorStorm makes release timing the racing line itself. Boost drives the vehicle forward and holding it too long destroys the engine, so the whole race is spent nursing the button up to the edge and letting go just before it goes.

Pressing a button again can extend a verb, provided the second press does something other than repeat the first. Mashing for its own sake is not the idea. The idea is that press one begins an action and press two, landed inside a window, produces a different one.

Double jumps are the obvious case: the player has to decide where to spend the second leap. Stack more air jumps on top and the decision speeds up, as it does in Ms. Splosion Man, where every extra activation reshapes the arc and the options that follow.

The active reload in Gears of War does this to a chore. The first press starts reloading; a second press with the marker in the right zone rewards the next shots, and missing the zone punishes them. Reloading suddenly has stakes.

What makes it work is the shift in attention. A background maintenance action becomes a small test of skill without becoming a different verb. It is still reload; the timing is what changed its meaning.

Combos scale the same logic up. A punch can flow into heavier attacks when the follow-up inputs land on the right beat, so the button stops being one hit and becomes the opening of a phrase the player may or may not finish.

Depth also comes from what happens when two verbs meet. Psychonauts has a jump and a basic attack, and attacking shortly after jumping produces a palm bomb. One verb straight after another, inside a timing window, is a third move.

Transitions like that ask the player to understand connections, not just individual actions. A single readable transition is easy to pick up. A large set of them becomes a language that committed players learn and eventually memorize.

Aiming down sights is the same trick in a shooter. Firing from the hip sprays; holding the aim button tightens the shot and usually costs mobility. The player has not switched to a second attack, only changed the terms of the one they had.

Not every game wants this, but it shows how a modifier can create a real choice without inventing an unrelated command. Combinations land when the result feels like it follows from the two verbs that made it.

Pair a button with an analog stick, or any other fine-grained input, and the design space opens up again. Every game about moving through space already ties action to position; a punch only counts if the character is standing close enough to land it.

Mario takes that much further. Where the jump goes and how far depends on the direction and speed he had before the button went down, so clearing a wide gap means earning a run-up first. The arc can still be nudged in the air, and beginning from a spin, a turn, or a crouch produces different moves entirely.

This is why the jump could never be split into a left-jump and a right-jump button, however well that might have served the earliest version. Direction modifies the leap with too much nuance for movement and jumping to be separate verbs.

Crouching layers on more. Crouch then jump for a high backflip, crouch out of a run before jumping for a long jump, crouch in the air for a ground pound that can feed into another leap. They stay intuitive because each one follows from what the verbs mean rather than from arbitrary button arithmetic.

An expressive verb should reward mastery without demanding it. Mario's advanced repertoire sounds intimidating written out, and most of it is never required to reach the end. It exists for players chasing style, secrets, speed, or a lower finishing time.

That separation is what keeps the design honest. Someone new can run, jump, and survive on the basics, while an expert turns the same handful of inputs into a much wider movement vocabulary. Neither player is playing the wrong game.

For action games this is where versatile verbs earn their keep. The interesting play comes from how the player touches the world at all, rather than from piling on systems, buttons, and one-off commands.

Once the core verb is expressive enough, levels can ask for precision, risk, speed, improvisation, or flourish while the input language stays exactly as small as it was.

The payoff for a versatile verb is that a small set of actions does several jobs at once. Quick tactical decisions. Room for player expression. And an action that feels good before a single level exists to frame it.

They also cut clutter. Luftrausers could have shipped a heal button or scattered health pickups. Tying repair to releasing fire deletes a control and folds survival into the shooting rhythm instead.

Plenty of the satisfaction is physical. Holding a jump for extra height, releasing the fire button in Devil Daggers to pull resources in, chaining a brawler's attacks with fast thumb work — the hands learn these verbs as much as the head does.

The target is never complexity. It is a short list of actions that stay interesting because the player is still making real choices about how and when to use them.

The caveat is real and worth stating plainly. Versatile verbs lean on held buttons, repeat presses, chained inputs, and multi-button sequences, and every one of those can be uncomfortable or outright inaccessible for some players.

The answer is not to give up on expressive verbs. It is to look squarely at what the inputs demand. Remapping, toggles in place of holds, more generous timing windows, alternate control schemes, and honest difficulty expectations all do work here.

Depth and hostility are not the same thing. What matters is whether different players can reach the core experience, and whether the hardest techniques are required, optional, or adjustable.

Read Mario's jump this way and it stops looking like a button at all. It responds to whether the press was a tap or a hold, whether he was running, which verb led into it, how the stick moved before and during the leap, and whether a second press arrived on time.

Power-ups rewrite it again. The same button might float, or drop like a stone on release. Elsewhere, repeated presses timed correctly turn ordinary jumps into a triple jump.

That is the secret. Before anyone designs a level, the jump is already fun to perform. It handles navigation, generates risk, pays off skill, hides secrets, and gives players a way to show off, out of almost no buttons.

A great action verb is rarely just press A to do B. It is a compact system, and you find out whether yours is one by getting the build running and playing it — the answer is in your hands, not in the design document. The more carefully that system reads timing, pressure, movement, and context, the more play falls out of the simplest interaction.

In the Flockbay app, start with a jump that does one thing, play it, then add exactly one extra result, a stomp or a steer. Play again. If you cannot predict the new result, you added noise. If you can, and the level gets more interesting without a new button, you are on the Mario road.

An AI platformer maker and a 2D platformer template should not receive a second jump button until the first one is thick.