Invisibility removes the easiest position cue, not all usable information. Footprints, sound, particles, displaced foliage, lock-on behavior, and attack previews become a lossy sensor for one continuous hidden body. Their cadence and error must still leave time and space for a full response.

Open boss builder
Fade the body and begin a traceAt 0.62 s Kern begins to fade and is fully hidden at 0.88 s. Five short-lived footprints, dust puffs, and stone ripples appear along one continuous route through 2.12 s, while Tavi moves toward the marked safe side without receiving an exact silhouette.
Remove the body, preserve the evidence Kern fades while rune-lit footprints and expanding stone ripples mark a continuous curved route. The final clue locks a diagonal attack corridor. Tavi stands fully beside that corridor, waits through the hidden strike, then closes with the sword as Kern becomes visible. Boss Player

At 0.62 s Kern begins to fade and is fully hidden at 0.88 s. Five short-lived footprints, dust puffs, and stone ripples appear along one continuous route through 2.12 s, while Tavi moves toward the marked safe side without receiving an exact silhouette.

Implementation checklist

Build invisibility as an explicit state contract: one authoritative hidden transform and hitbox, bounded secondary cues, cue cadence and lifetime, uncertainty limits, a committed attack source, consistent collision, multisensory equivalents, readable entry and exit transitions, and a useful post-reveal response window.

Core checks

Three questions for the mechanic

  • Which state remains authoritative while the body is hidden?

    Keep one real transform, facing, velocity, and collision volume throughout invisibility. Presentation may suppress the model, but AI, attacks, physics, network replication, and secondary effects must read that same hidden state. Decide explicitly whether contact damage, lock-on, shadows, health bars, and aim assistance remain available. Debug the true body and every exposed proxy together so a cue never describes a different position from the collidable boss.

  • How accurately do clues predict the next source?

    Treat each footprint, sound, dust puff, water wake, or foliage reaction as a timestamped sample with known delay, lifetime, radius, and error. The sequence should communicate direction and plausible speed without revealing a perfect outline. Before an attack, lock the source or show a new preview long enough for the player to move a full body out of danger. Never let the hidden boss silently teleport beyond the history implied by those samples.

  • Can every player perceive entry, tracking, and exit?

    Pair environmental traces with high-contrast particles, spatial or stereo sound, controller vibration, and an optional accessibility outline. Give fade-in and fade-out their own state cues, and ensure busy effects cannot erase the evidence. Assists may increase cue lifetime, reduce positional error, or add a directional indicator without changing the hidden route or attack rule. Test on small displays, mono audio, color-vision filters, and reduced motion.

Design mistakes

  • Opacity changes, but the information contract does not

    A transparent model is cosmetic when the lock-on reticle, shadow, health bar, or perfect homing aim still reveals the exact center. The opposite failure removes every signal and turns contact into guessing. Inventory every channel that exposes position, choose which ones remain intentionally lossy, and make their accuracy agree with the encounter's intended uncertainty.

  • The hidden boss breaks continuity before attacking

    If traces imply movement to one side but the hitbox or attack begins elsewhere, the player cannot reason from evidence. Keep motion continuous, cap hidden speed, and log the distance between the last cue and the committed source. If a teleport or decoy is part of the pattern, signal it as a separate rule rather than hiding the discontinuity inside invisibility.

Tuning

Tune the attack

  • Model secondary cues as a lossy sensor

    Expose samples of the hidden state instead of a second exact model. A cue can be delayed, short-lived, quantized to terrain cells, or offset within a bounded radius. Record those parameters in data so difficulty changes remain deliberate and automated tests can verify that the attack source stays inside the inferred envelope.

  • Let the arena material carry information

    Snow holds prints, shallow water forms wakes, dust rises from heavy steps, foliage bends, and loose stones react to weight. These effects make invisibility feel grounded in the setting while clarifying which surfaces support the mechanic. Preserve an equivalent abstract cue on surfaces that would otherwise become unreadable.

  • Tune cadence, lifetime, and error together

    Faster bosses need more frequent or longer-lived samples. A larger error radius needs either more reaction time or a wider safe route. Measure the worst gap between useful cues, the maximum inferred-source error, and the movement budget from source lock to impact; tuning only opacity or damage cannot repair a broken sensing loop.

  • Make reveal states mechanically meaningful

    Use a clear impact, stagger, material collapse, or exhausted shimmer to announce when exact position returns. If reveal creates a damage opportunity, keep its duration stable enough to plan around and show when it closes. Later phases may shorten the window or mix cue types, but should not retroactively invalidate the learned trace grammar.

Arena

  • Kern hides its core, not its weight

    Kern dims the runes holding its stone plates together until the body disappears. The quarry still answers each heavy step: pebbles jump, dust folds around an unseen leg, and old floor runes flare under pressure. The setting itself becomes the witness to the hidden elemental.

Player upgrades

  • Let Tavi infer a route, then earn the approach

    Tavi uses ordinary movement and the existing sword. The clue cadence always leaves a neighboring body-sized safe side, the final source is fixed before the strike, and the visible return separates evasion from the counter. Accessibility settings can extend traces or add direction without replacing the authored route.

Do not confuse this with

  • Continuous hidden state, not teleportation or a decoy

    Invisibility suppresses direct perception while the same body continues through space and collision. Teleportation changes position discontinuously, and a decoy changes which perceived entity is real. Those mechanics can be combined, but each transition needs its own signal; otherwise players cannot know whether to integrate a trace, expect a jump, or test identities.

Bosses that use this mechanic

Learn more

Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub