Goal and progress clarity
Players need to understand the current goal, whether an action registered, and how close they are to a state change. Make targets, hits, and progress legible without explaining away the challenge.
A check from Boss Up
This lens connects to one of the talk’s practical rules.
Make state legible
Show the goal, valid hits, progress, signals, and enough reaction time; mystery can be intentional, helplessness should not be.
Mechanics that use this lens
Weak point
Damage is concentrated on a specific body part.
Structure and readabilityTelegraph
A telegraph communicates an upcoming attack’s timing.
Structure and readabilityFight phase
A health.
Structure and readabilityEnrage
The boss enters a more demanding state after a threshold or time limit.
Additional targetsDecoy
The boss presents a convincing false target, so the player must identify which body can advance the fight before committing an attack.
DefenseDamage-type resistance
The same boss body takes less damage from a slash than a thrust; both attacks still connect.
DefenseSituational immunity
A linked ward prevents damage to the boss until the player disables it.
DefensePart break
A targeted boss component is destroyed, visibly disabling its associated attack.
DefenseAttack reflection
A guarded boss reverses an incoming attack, making its return path dangerous to the player.
DefenseCounter stance
A visible guard converts a qualifying player strike into the boss's own counterattack.
DefenseAbsorption power-up
A marked input is absorbed instead of damaging the boss and fills a resource for a stronger next move.
DefenseLoadout adaptation
The boss snapshots a defined part of the player's loadout and selects a visible, bounded response package.
Structure and readabilitySurvival phase
A survival phase advances when players endure a bounded sequence, timer, or objective rather than reducing boss health.
Space, movement, and perceptionForced scrolling
Forced scrolling moves the camera or playable route independently of the player, so maintaining progress becomes a required part of the encounter.
Space, movement, and perceptionChase herding
Chase herding makes the moving boss a spatial objective: the player closes distance, preserves contact, and approaches from useful angles until the boss reaches a designed destination.
Space, movement, and perceptionEscape phase
An escape phase gives the boss a destination and consequence outside ordinary combat. The player must interrupt, pursue, or accept the clearly stated result.
Space, movement, and perceptionNested / relocated arena
A relocated arena transfers the active boss fight into another playable space without ending or silently rebuilding the encounter.
Space, movement, and perceptionControl mode shift
A control mode shift replaces the player's current movement or response grammar with another one during the same encounter.
Encounter goals and vulnerabilityObjective-linked invulnerability
The boss ignores normal damage until a finite set of visible protection objectives is complete, then opens for a timed damage window.
Encounter goals and vulnerabilityWave-clear objective
The encounter advances when the player clears a fixed sequence of finite enemy waves rather than depleting conventional boss health.
Encounter goals and vulnerabilityEnvironmental weapon
A fixed arena device must be reached and prepared; its resolved shot, not ordinary weapon damage, advances the encounter.
Encounter goals and vulnerabilityEncounter-specific tool
The encounter grants or activates a portable tool whose rule-specific action is unusually effective against this boss.
Encounter goals and vulnerabilityPlayer-controlled boss
The system assigns a real player as the boss opponent and substitutes AI when no candidate is available.
Encounter goals and vulnerabilityProjectile rally
Boss and player repeatedly return the same projectile until a missed response resolves the rally.
Encounter goals and vulnerabilityBaited self-hit
The player places or exposes a valid hazard, baits a committed boss action through it, and turns the boss's own resolution into damage or stagger.
Encounter goals and vulnerabilityPosture stagger gauge
Authored attacks and counters pressure a separate posture gauge; a break opens a bounded critical state that only an explicit finisher can consume.
Encounter goals and vulnerabilityPacifist resolution
The encounter can end without emptying boss health when the player satisfies a visible nonviolent condition and commits to a separate spare action.
Encounter goals and vulnerabilityPersistent encounter progress
Completed encounter objectives survive player defeat, so a new attempt resumes from an explicit authored milestone instead of rebuilding the whole fight.
States, resources, and scalingStatus buildup
Boss attacks fill a separate status gauge; the actual effect begins only when accumulated exposure reaches its threshold.
States, resources, and scalingInstant-kill condition
A clearly signaled condition bypasses ordinary damage and ends the current attempt through one authoritative result.
States, resources, and scalingMaximum-health reduction
A marked hit lowers the health ceiling separately from current health, limiting later recovery until an explicit restoration rule succeeds.
States, resources, and scalingAbility or healing lock
A marked contact temporarily rejects one named action while movement and the rest of the player kit remain available.
States, resources, and scalingResource steal or drop
A qualified boss hit removes a bounded resource and may spill it into pickups that the player can reclaim or the boss can capture.
States, resources, and scalingOn-hit healing or lifesteal
A qualified boss contact restores a bounded amount of health, even when the hit deals no damage if the encounter declares blocking eligible.
States, resources, and scalingInterruptible self-heal
The boss starts a visible recovery action without player contact; a qualified interruption cancels it, while a completed cast applies one capped heal.
States, resources, and scalingInterceptable healing sources
A separate entity or resource sends healing toward the boss, and destroying the source or its packet prevents that bounded delivery.
States, resources, and scalingAdaptive damage-rate cap
Recent or estimated burst damage lowers the fraction of each new hit that reaches the boss, then the attenuation relaxes when the damage window clears.
States, resources, and scalingLoadout mirror
At a declared moment, the boss snapshots selected parts of the player’s build and converts them into a stable encounter package.
States, resources, and scalingMoveset shapeshifting
The boss changes between complete borrowed movesets, each with its own signals, attacks, movement rules, and recovery.
States, resources, and scalingFalse death and return
The boss appears defeated, but encounter completion stays pending until a readable revival begins a new phase.
States, resources, and scalingRun-history manifestation
The encounter turns selected decisions accumulated before the boss into a stable set of enemies, allies, attacks, or rules.
States, resources, and scalingReal-time progression
The encounter changes while the game is closed because a saved deadline, calendar window, or server schedule continues in real time.
States, resources, and scalingInterface interaction
The boss can only be opened, weakened, or answered by using an input channel or system interface outside the player character's ordinary verbs.
States, resources, and scalingWorld-state encounter variant
A normalized world state selects a complete encounter variant: rules, geometry, roster, and rewards change together rather than only scaling numbers.
States, resources, and scalingParty-size scaling
The encounter converts active party size into bounded health, target, hazard, and reward budgets while preserving progress across joins, leaves, and retries.
Multi-boss relationshipsPartner revival
A surviving boss can restore a downed partner unless the cast is stopped or the pair is finished within the authored window.
Multi-boss relationshipsKill-order inheritance
The first boss to fall selects a distinct survivor phase; the transfer is visible, resolved once, and reset on a new attempt.
Multi-boss relationshipsShared group health
Hits on either active boss drain the same encounter bar, while each body can leave or return without replenishing that bar.
Multi-boss relationshipsCoordinated duo attack
Two bosses commit to a shared target and timed attack legs; interrupting the leader cancels the dependent follow-up.
Cooperative coordinationShared-damage stack
A marked impact has one damage budget split among players inside its area at resolution, making participation a survival rule.
Cooperative coordinationPersonal spread
Several players receive independent impact zones; each must clear the other players' bodies before the simultaneous hit.
Cooperative coordinationTower soak
A fixed point checks how many living players occupy it when the timer ends; a missed count changes the whole group's outcome.
Cooperative coordinationEntity tether
A visible bond makes two entities' movement interdependent; crossing its stated limit changes the outcome for both.
Cooperative coordinationGaze check
A marked source checks which way the player character faces when its gaze resolves.
Cooperative coordinationTankbuster and target handoff
A strong hit leaves its recipient vulnerable, so another defender must claim the boss before the repeat.
Cooperative coordinationDebuff handoff
A marked player transfers a harmful timed state through deliberate contact before it expires.
Cooperative coordinationOrdered targets
The boss marks several targets and strikes them in a visible, committed order.
Cooperative coordinationPairing polarity
The boss marks four players; each receiving zone needs exactly one player of each polarity.
Cooperative coordinationParty split
The boss divides the group; both teams must finish their own task before everyone can reunite.
Learn more
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub