Teleport is a discontinuous position change, not a fast dash. Kern dissolves at 0.55 seconds while a destination rune appears at 0.72. With body collision off, the boss reforms there by 1.70 and commits to a fixed vertical strike from 2.36–2.72 seconds. Tavi reads the destination, clears the lane, and uses the opening.
At 0.55 s Kern begins dissolving at the origin. At 0.72 s a shrinking destination rune appears at the exact reappearance point; the boss body and contact collision are absent from 1.05–1.52 s.
Autoplay is disabled by reduced motion. Scrub across 0.55, 0.72, 1.05, 1.52, 1.70, 2.36, and 2.72 seconds to inspect the teleport contract.
Implement departure, absence, destination reveal, reappearance, follow-up commitment, collision authority, and reset as explicit timed states driven by one destination record.
Capture one legal destination before disappearance and keep it immutable through reappearance and the follow-up. Validate arena bounds, navigation, camera framing, overlap with players, and reserved hazard space before committing. In the example the destination record is exposed at 0.72 s and never retargets.
Disable body, contact damage, targeting sockets, and hittable hurtboxes with one authoritative absent state. Decide separately whether status timers, projectiles, summons, and arena ownership continue. Visual disappearance must not leave an invisible collider or a damage trail between the two points.
Treat arrival and the next attack as one authored package. Kern reforms by 1.70 s, then previews a stored vertical lane for 0.66 s before its 0.36 s active window. Reappearance cannot overlap Tavi, the lane never tracks after reveal, and recovery starts only after collision is off.
A random destination that becomes known only on arrival converts spatial reasoning into guessing and can create unavoidable contact damage. Reserve space around players, expose the destination early, or provide a guaranteed escape interval after arrival.
Sweeping collision along the line between endpoints contradicts the visible disappearance. If transit should damage, show a beam, trail, portal connection, or moving body and classify that geometry explicitly instead of borrowing the teleport label.
Measure departure recognition, destination search, camera travel, response choice, and movement clearance separately. A long delay can still feel unfair when the new point is off-screen or indistinguishable from ambient effects.
Random does not mean unconstrained. Tag destinations by range, angle, line of sight, elevation, recent use, and compatibility with the next attack. Weighted selection should avoid repeats and impossible combinations while retaining variation.
Store health, phase, cooldowns, captured target, facing policy, and queued follow-up before hiding the actor. Networked and rollback builds must replicate the destination and state transition, not infer them independently from effects.
Exercise destinations near walls, platforms, split-screen edges, target-lock limits, summons, and multiple players. Verify the frame before absence, every absent frame, arrival, the first active frame, interruption, death, and loop reset.
Kern collapses into fragments at the origin as a paired rune ignites elsewhere. The same rune channels the next strike, so the magical fiction communicates both where the elemental returns and what space it will threaten.
Tavi does not need a special teleport counter. The destination rune creates an early spatial read, the fixed lane makes a sideways step sufficient, and the recovery preserves the familiar sword response once the danger has ended.
A dash occupies and crosses intermediate space. Burrow-and-emerge usually hides a moving source whose emergence point is part of a subterranean route. Teleport has no collidable transit between endpoints; portals may add a persistent connection, while a swap exchanges two actors or positions.
Nightmare King Grimm repeatedly disappears and returns at a new arena position to begin a recognisable attack. The destination and pose identify the follow-up quickly, letting relocation function as spacing and attack selection rather than contact travel.
The Time Keeper uses short teleports to create spacing before shurikens, hook, or dash attacks. The relocation supports the range requirements of the queued move; it is not itself a damaging sweep across the arena.
Astel vanishes and may reappear overhead for a grab. The example shows why a 3D teleport needs strong arrival audio, camera-aware search time, and a distinct follow-up tell: the dangerous decision begins after relocation, potentially outside the current view.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub