Forced inertia changes what movement input means. Starting is a commitment: heading, entry speed, friction, collision, and the eventual stopping point matter more than frame-by-frame steering. The rule is fair when the altered surface is unmistakable, the endpoint can be estimated, and control returns on a visible beat.

Open boss builder
Freeze the floor and preview the vectorAt 0.44 s Kern's rune freezes the quarry. At 0.82 s a straight vector and rough stopping patch reveal where Tavi will finish; Tavi reaches the entry point before direction locks at 1.34 s.
Show the endpoint before the slide begins Kern freezes the quarry floor from top to bottom, leaving a lethal cliff at the right edge. An icy groove points to the rough rune patch where Tavi will stop; Tavi commits, slides along the fixed route with a visible ice trail, brakes, regains control, and runs to Kern for one sword strike. Boss Player

At 0.44 s Kern's rune freezes the quarry. At 0.82 s a straight vector and rough stopping patch reveal where Tavi will finish; Tavi reaches the entry point before direction locks at 1.34 s.

Implementation checklist

Implement surface entry, velocity capture, reduced acceleration, limited steering, deterministic deceleration, collision behavior, endpoint preview, a safe braking margin, control restoration, and the next action as one movement contract.

Core checks

Three questions for the mechanic

  • What is captured when movement commits?

    Define the exact entry event and snapshot the quantities that survive it: direction, speed, acceleration contribution, facing, and any dash or knockback velocity. Decide whether later input offers no steering, weak steering, or only braking. Keep the rule identical for keyboard, stick, touch, AI, replay, and network prediction instead of letting each controller produce a different trajectory.

  • Can the player predict the stopping point?

    Expose the changed surface before the first required move and provide stable visual motion cues: frost grain, skid streaks, a trajectory ghost, or a destination marker. Calculate the preview from the same integration and collision rules as the live body. Include the player's radius and a visible margin so a mathematically safe center does not leave the silhouette touching a lethal edge.

  • When and how does ordinary control return?

    Use a readable speed loss, sound, pose, floor change, or pulse to mark the transition back to normal movement. Define how rough patches, walls, jumps, attacks, status cleanses, and invulnerability affect momentum. Give the player a meaningful follow-up after stopping so the mechanic produces a planned arrival rather than only delaying access to the boss.

Design mistakes

  • The slide feels like input lag

    If the surface cue is weak or steering authority changes gradually without feedback, the player reads preserved velocity as an unresponsive controller. Switch the movement state on a named beat, exaggerate the first skid, show the remaining speed, and keep animation, particles, audio, camera, and collision synchronized with the actual velocity.

  • A correct plan still dies at the edge

    Tiny friction differences, uneven frame steps, hidden slopes, enemy pushes, or collision depenetration can shift the endpoint after commitment. Use fixed-step or analytic deceleration, clamp negligible velocity, author generous stopping zones, and test external impulses explicitly. Precision may be part of mastery; nondeterministic drift should not be.

Tuning

Tune the attack

  • Choose a velocity model designers can solve

    Prefer a small explicit state machine: normal movement, entry capture, committed slide, braking, and restored control. Constant or piecewise deceleration makes stopping distance predictable and tunable. If steering remains, express it as a capped lateral acceleration rather than silently replacing the captured heading with the latest input.

  • Make collision outcomes intentional

    Decide whether a wall stops, reflects, redirects, damages, or preserves tangential velocity. Test corners, seams, moving platforms, slopes, narrow passages, and several contacts in one frame. A visible boundary must agree with the collision surface, and a camera cut must not hide the remaining travel distance.

  • Tune from reachable endpoints backward

    Place useful stopping regions first, then derive entry distances and speeds that reach them with margin. Test minimum and maximum input magnitudes, accessibility assists, movement upgrades, debuffs, latency, and every supported frame rate. If one build changes speed, update either the preview or the stopping region so the rule stays legible.

  • Combine only with threats that respect commitment

    During an unsteerable interval, hazards must be readable before the slide begins or arranged as a stable lane problem. Avoid spawning a reactive marked area under the already committed endpoint unless another guaranteed answer exists. Good combinations test planning; bad combinations ask for steering the mechanic has explicitly removed.

Arena

  • Kern turns quarry dust into rune ice

    The elemental drives a cold glyph through old polishing channels in the floor. Smooth stone flashes blue while one unfinished patch keeps its rough chisel marks, explaining both the long glide and the deliberate place where Tavi can regain footing.

Player upgrades

  • Use Tavi's ordinary movement and sword

    Tavi needs no special dodge or air control. The preview uses the current run speed, the braking patch accepts the complete body with margin, and normal control returns early enough to take a short sword route to Kern before the arena freezes again.

Do not confuse this with

  • Preserved velocity, not an instant displacement

    Knockback applies an external impulse, forced scrolling moves the reference frame, and a control-mode shift remaps available actions. Forced inertia specifically carries the player's own committed motion after input release, making the eventual stopping point the decision.

Bosses that use this mechanic

Learn more

Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub