A moving hazard is one active danger footprint whose position changes over time. It works when the path, direction, speed, size, and end condition are legible before the moving edge arrives, collision follows the current visible footprint, and an ordinary response can reach a safe corridor in time.
Kern reveals a fixed horizontal route and one circular field at its starting point. The whole radius and direction are readable before it can hurt.
Autoplay is disabled by reduced-motion settings. Use the timeline to inspect the moving edge and safe corridor.
Tune the path, speed, full-body clearance, readable moving edge, and cleanup as one continuous rule.
Preview the entry, complete route, direction, radius, travel speed, and exit. A moving edge or repeated cues should make future danger easier to read than a static marker at the starting point.
Sample one center and radius for rendering and hit testing at every time. Check the player's full body against the current footprint, not the entire future path or a delayed invisible copy.
Measure the time until the moving front reaches each possible route. Leave a corridor reachable with ordinary acceleration, and retest it with the camera, walls, and concurrent attacks.
A sudden drifting field asks for luck rather than route prediction. Show its origin, direction, and footprint before activating collision; signal a reversal as a new commitment.
A visually clear patch must not leave hidden collision behind or hurt along its preview track. Reserve a persistent residue for an explicitly separate hazard-trail rule.
A valid-looking gap can close faster than normal movement can reach it. Tune width, speed, warning time, and arena boundaries against the player's actual acceleration and body size.
Store path control points, start time, duration, radius, and active interval. Derive the current center, warning, visual edge, collision, and disappearance from that clock.
At high speed, a large field can leap across the player between samples. Sweep its footprint along the segment between consecutive centers instead of checking only endpoints in the game simulation.
A broad field denies an arena corridor over a sustained passage. A projectile is a discrete launched object with its own origin and impact; do not silently change its hit rule into a continuous lane.
Change speed, width, curvature, direction, or concurrent pressure separately. If the field reverses or follows the player, introduce a new tell and re-evaluate the safe route.
Kern sends a runic current across a known strip of stone. The moving glow claims space only where it is now, so Tavi can read the next boundary and use the lane again after it passes.
Basic movement needs a reachable side corridor and enough advance warning. A jump can clear a low field only if its vertical collision is modeled; dash invulnerability, block, or teleport must have explicit interactions with the moving footprint.
A moving hazard carries one persistent active footprint along a path. A mine waits at a trigger point, a lingering hazard stays in one place, and a hazard trail leaves dangerous residue behind motion. Here the old position becomes safe when the field passes.
During Grim Matchstick's second phase, marching flame creatures traverse his tongue. The ground-level danger occupies a moving position while their crouch warns of a different jumping path, showing why motion and a changed path need separate cues.
Bubbling honey rises under Rumor Honeybottoms as the platforming space scrolls upward. Unlike a compact circle, its moving edge is a broad arena boundary; the reachable platforms and its climb rate determine the response window.
Wind announces the direction before Caustic Grebuloff's Miasmata orbs drift across the arena with circular attack markers. The moving footprints make the future corridor, rather than each orb's original position, the useful planning target.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub