Context and sequence
A challenge gains meaning from where it appears, how it fits its environment, and what earlier or later challenges prepare. Review timing, local systems, escalation, and aftermath together.
A check from Boss Up
This lens connects to one of the talk’s practical rules.
Fit context and sequence
Connect place, supporting actors, timing, neighboring challenges, and consequences into one setup.
Mechanics that use this lens
Telegraph
A telegraph communicates an upcoming attack’s timing.
Structure and readabilityFight phase
A health.
ProjectilesCrossfire
Two independent sources fire through the arena so their projectile paths intersect.
ProjectilesSplitting projectile
One projectile reaches a readable trigger, disappears, and releases several committed fragments.
ProjectilesReturning projectile
A projectile travels away from its owner, turns at a readable point, and creates a second dangerous pass on the way back.
ProjectilesOrbiting projectiles
Projectiles remain attached to one center and rotate as a spaced moving perimeter.
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 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.
Learn more
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub