A gaze check tests character facing relative to a named source, not camera direction or position alone. Here, turning away before the eye pulse prevents the effect; turning back too soon causes a hit. Other encounters check throughout a channel or switch the active threat with facing, so teach their timing separately.
At 0.70 seconds Kern reveals the eye. Tavi starts facing it, then turns away between 1.04 and 1.60 seconds. The arrow beside Tavi and the shared character rig show the same orientation used by the rule.
Reduced motion disables autoplay. Scrub through 0.70, 1.30, 2.30, 3.10, 3.70, 4.40, and 5.50 seconds.
Specify source position, target orientation, angular boundary and equality rule, snapshot or channel duration, warning cue, status and damage, one-hit identity, and a clean retry.
Name the source and measure the angle between the player's facing vector and the direction from player to source. This demo treats an angular difference of 90 degrees or less as looking; a larger difference is safe. Use the character's rendered facing, not an unrelated camera angle or a stale aim vector.
Reveal the eye at 0.70 seconds and sample once at 2.20 seconds. Repeat the same rule at 4.30 seconds with a new hit ID. A successful turn avoids the first pulse; facing the source at the second pulse applies 90 damage once. A continuous channel would need repeated or continuous checks and must be labeled as such.
Budget the turn around movement, casting, controller input, and other threats. Test exactly on the 90-degree boundary, just beyond it, coincident source and target, invalid facing, repeated callbacks, and reset. Keep the eye and facing arrow legible without color or camera motion.
In third-person games, a player can look at the screen while the avatar faces away. Couple the collision rule to the avatar's facing and show that orientation in the rig.
An eye icon alone does not say whether the game samples once, for an animation window, or throughout a channel. Show the pulse or channel interval and delay the outcome until that rule is active.
Tavi stays at one point in both checks, making the result attributable to orientation. If distance or line of sight also matters, expose those additional tests rather than implying that the gaze is purely directional.
Attacking, casting, or target lock may automatically rotate the character. Test whether these controls can accidentally turn the avatar toward the source during the check; offer a readable way to maintain the intended facing.
Log source and target IDs, source bearing, facing angle, angular difference, hit ID, status application, health delta, and reset. Scrub across the boundary and replay the same input to confirm determinism.
Kern's rune eye opens. Tavi turns their back and its first flash passes. When the eye reopens, Tavi faces it: the flash finally finds a target.
Show the boss eye, an arrow fixed to Tavi's body facing, a visible pulse, a check or cross, and a health number. Keep the timeline and scene seekable with autoplay disabled.
A line-of-sight hazard asks whether cover blocks a ray; a gaze check asks whether the target faces the source. Cuphead's Angel and Demon instead uses facing to change which side is harmful, while a sustained gaze can punish throughout a channel rather than at one pulse.
Mortal Gaze marks the boss as a gaze source; characters facing it risk Doom, while turning away avoids that status. Unlike this simplified demo, the game's resolution timing and its lit cleanse circles are encounter-specific.
In phase three, Lunatic Gaze punishes players facing Yogg-Saron during its channel with damage and lost Sanity. This is a sustained facing test, unlike the two discrete samples in the demo.
The Angel and Demon swap sides when the player turns; the Demon stays in front and its attacks are dangerous, while the Angel's are harmless. This is an orientation-controlled threat swap, not a timed look-away pulse.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub