Kern announces a straight lane and a speed-change rune. Once committed, he crosses 120 units at 100 units per second, then 180 at about 277. He never turns or expands his hitbox. Tavi walks clear before Kern reaches her former position. He stops, the trail clears, and the next loop restores the slow pace.
Kern shows one fixed horizontal lane and its speed-change rune while Tavi stands ahead of him.
Autoplay is disabled by the reduced-motion setting. Use the timeline slider to inspect the loop.
Tune initial speed, the cue and position of acceleration, final speed, route length, player clearance, and recovery independently.
Mark the whole straight lane and the acceleration rune before Kern moves. The second segment must use the same path; a late turn would create a separate aiming rule.
Let Kern travel the first segment long enough to establish its slow pace, then change his velocity at the glowing rune. Shorter, brighter motion trails make the fast segment legible without enlarging his collision body.
Check the time Kern reaches the player's former position against ordinary walking time beyond his 57-unit body radius plus the player's 24-unit radius. Stop the hazard before recovery, then restore the same slow starting speed.
An unannounced acceleration turns a learned timing into a trap. Preview the switch location and accompany the speed shift with an immediate change in trail and rune brightness.
If Kern changes direction at the rune, the player cannot rely on the promised escape. Test the velocity change separately from tracking or a wider hitbox.
The first 120 units take 1.2 seconds (100 units/s). The next 180 take 0.65 seconds (about 277 units/s). Preserve those distances when tuning the cadence so the contrast is visible.
The boss's 57-unit collision radius plus Tavi's 24-unit radius calls for more than 81 units of center separation. Tavi moves 170 units downward in 0.7 seconds and remains outside the horizontal crossing.
At x=260 the rune brightens when Kern crosses it at 2.8 seconds. Both visual events coincide with the slope change of his position over time, not with an arbitrary effect timer.
Kern's movement ends at 3.45 seconds; the danger trail vanishes. Recovery returns him to the start, so the next loop again opens slowly rather than inheriting the fast speed.
Kern's stone feet grind across the floor until he passes a charged threshold glyph. The glyph flares and his wake sharpens: the setting explains why this particular crossing suddenly gets faster.
The intended answer is to leave the announced lane early by ordinary movement. A dodge can rescue a late response, but the baseline timing must not assume a dash or invulnerability.
Charge commits a path; this rule keeps that path and changes the movement rate along it. Enrage may raise many stats at once; a fight phase may replace an entire move set. Here a single velocity switch is the teaching variable.
The top-down Moldorm moves faster after hits and can slow again. Unlike Kern's fixed straight crossing, its path wanders; the reusable ingredient is a conspicuous change of travel speed on the same visible boss.
This separate nightmare encounter reuses Grimm's recognisable attacks at a faster pace; even the Pufferfish fireballs move faster than in the earlier fight. It is a comparison across two encounters, not a mid-attack acceleration.
After the phase change, Placidusax's tempo increases and new rapid dives and teleports alter the response window. This is a whole-phase speed variant, not Kern's single predetermined threshold, and must be telegraphed accordingly.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub