Cover and line of sight makes an obstacle part of the attack rule. The player identifies the source, reads the protected side, enters the occluded region fully, and knows when to leave. It works only when rendering, collision, damage, camera, and multiplayer authority agree about the same blocker.
At 0.42 s Kern's head rune locks a fixed line through Tavi. At 0.78 s the pillar projects a clear safe shadow away from the source, so the required side is visible before movement begins.
Autoplay is disabled by reduced motion. Scrub across 0.42, 0.78, 1.62, 2.12, 3.18, 3.92, and 5.08 seconds to inspect targeting, occlusion, and exit.
Implement source locking, blocker eligibility, line-segment occlusion, readable shadow geometry, full-body clearance, attack termination, edge tolerance, cover persistence, and a reliable post-attack exit as one contract.
Tag eligible cover explicitly and define whether the query uses a point, capsule, several body samples, or a swept volume. Decide how height, thickness, destruction state, moving platforms, gaps, slopes, and one-way geometry affect the result. Use the same authoritative blocker data for warning, damage, AI, replay, and networking instead of trusting whatever happens to be visible on screen.
Reveal the source, the attack direction, and the blocker early enough to form one spatial problem. A shadow wedge, rim light, projected ray, or floor mask can show the protected region, but it must match the actual damage test. Include the player's full body and movement stopping distance; touching the pillar is not enough if the head or trailing collision still crosses the attack line.
Separate beam shutdown from the moment the player may safely leave. Signal both, preserve a short tolerance at the edge, and define whether the obstacle survives, moves, breaks, or becomes invalid for the next attack. Provide a useful post-cover choice—reposition, attack, restore resources, or protect another target—so waiting behind geometry leads back into play.
A camera angle can hide the source even when a center-point ray slips past the blocker, or a visible beam can continue through cover while damage is suppressed. These contradictions teach distrust. Draw the actual query in debug builds, sample the player's relevant volume, stop effects at the hit surface, and test every camera and latency condition.
A long attack with one permanent safe spot asks the player to arrive once and then wait. Add a preparation decision, a moving source, vulnerable cover, competing positions, or a meaningful exit timing—but keep the core occlusion rule stable. Pressure should come from reaching or preserving cover, not from secretly invalidating it.
Capture the source position used by the attack and test segments from that point to defined player samples. If the source moves during the cast, either update the shadow continuously and visibly or lock it at a named beat. Distinguish visual camera occlusion from gameplay line of sight: the camera may see around a pillar while the attack remains physically blocked.
Exact tangency is noisy across animation, frame rates, and network correction. Expand the blocker or contract the safe region by a small visible margin, then validate with the player's widest supported collision pose. Avoid a hidden rule where feet are safe but weapons, companions, or an upper-body sample remain exposed.
If attacks can damage the blocker, show durability and ensure at least one reachable alternative before it fails. Decide whether the lethal hit is absorbed, penetrates, or destroys the obstacle first. In multiplayer, prevent one player's unrelated splash damage from removing the only answer after teammates have committed to it without a replacement signal.
Sweep the source around every blocker and sample player positions just inside and outside both shadow edges. Test tall and short avatars, knockback, dashes, crouches, camera cuts, moving cover, simultaneous hazards, late joins, rollback, and low frame rates. Log false-safe and false-hit cases separately; both damage trust even when aggregate difficulty looks acceptable.
The old stone was cut from the same warded seam as Kern's shell. When the elemental focuses its head rune, the pillar absorbs the beam and leaves a cool turquoise shadow, making the safety rule feel like a property of the setting rather than a floating interface exception.
The pillar is close enough for Tavi's normal acceleration and wide enough for the complete body silhouette. No dodge invulnerability is required. The beam ends before Tavi leaves cover, and the short response route fits one normal sword strike before Kern resets.
A straight beam may be escaped by moving outside its lane, and a shield may block through an owned defensive state. Cover and line of sight specifically makes another world object interrupt the segment from source to player; safety depends on their relative geometry.
The side-view arena includes background door recesses that remove the hunter from direct gunfire while Yuudai's automatic shotgun controls the open lanes. Cover does not solve his close attacks or spawned dragons, so entering and leaving it remains a timing and target-priority decision rather than permanent immunity.
The Meteor Swarm approaches from a consistent side of the arena, and the giant central lumenflower blocks it. The fixed source direction turns one landmark into readable cover, while the remaining Failures can still occupy the protected side and prevent the safe position from becoming empty downtime.
Marked players place comets outside the boss's targeting ring, the alliance preserves them from Iron Giants, and everyone must put a surviving comet between themselves and King Behemoth for Ecliptic Meteor. Cover placement, durability, source direction, and full-raid access are therefore one connected rule.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub