Party-size scaling keeps one boss meaningful for solo players and groups without multiplying every value equally. Roster changes queue during committed actions, resolve at safe boundaries, preserve the visible health fraction, and settle reward eligibility independently.
At 0.62 seconds, a second participant joins the roster queue. At 1.18, a safe boundary selects the two-player curve: maximum health becomes 1.6× while the displayed 68% progress remains unchanged.
Autoplay is disabled by reduced motion. Scrub across 0.40, 0.62, 0.90, 1.18, 1.50, 1.80, 2.22, 2.52, 2.82, 3.28, 3.50, 3.72, 4.00, 4.55, and 5.35 seconds.
Define roster authority, active-member rules, join and leave grace, safe resolve points, health and target curves, progress preservation, phase thresholds, reward eligibility, reconnect behavior, caps, accessibility, and telemetry.
Choose one authoritative roster and define joined, loading, alive, downed, disconnected, reconnecting, spectator, and departed states. Add grace for short drops, deduplicate identities, cap the party size, and never derive encounter strength from every client independently.
Tune health, stagger, target slots, simultaneous hazards, add count, revive pressure, and resource drops independently. Use diminishing returns instead of multiplying everything by party size; extra bodies already add damage, coverage, revives, roles, and attention.
Queue changes during telegraphs and active attacks, then apply them in recovery, phase handoff, or another authored safe point. Preserve the health fraction and completed objectives, keep phase thresholds monotonic, and snapshot qualified reward shares separately from the current combat roster.
Doubling health, damage, hazards, and adds can compound into far more than double difficulty. Treat durability, attention load, target coverage, recovery, and rewards as different budgets with explicit caps.
A target disappearing mid-cast or a health bar jumping backward breaks causality. Lock committed targets, queue the roster event, preserve the visible progress fraction, and apply one idempotent resolution at the next safe boundary.
Map party sizes to health, stagger, target, hazard, and reward values in one data table. Clamp unsupported sizes, record the curve version, and test every transition in both directions so a leave never produces an easier exploit or an impossible remainder.
Combat can scale down after a genuine departure while contribution credit remains. Define participation thresholds, reconnect windows, anti-idle rules, and disconnect handling so neither late joins nor network loss silently duplicate or erase a share.
Record anonymized party size, curve version, queued event, resolve boundary, health fraction before and after, target count, disconnect class, retries, completion, and reward grants. Audit oscillation and repeated join-leave patterns separately.
A second rune joins Tavi's trial, so the scale adds another target without moving the progress mark. When the rune fades, Kern finishes the promised attack before the covenant returns to one participant; the departed ally's contribution seal remains.
Keep solo, duo, and larger groups viable; avoid mechanics that require an absent role; provide generous reconnect and downed-state grace; mark personal targets with redundant shape, color, text, and sound; and do not accelerate cues merely because more players are present.
A difficulty setting selects an authored challenge level, and a world-state variant selects a contextual rule package. Party-size scaling converts the current authoritative roster into bounded encounter budgets and defines how those budgets change safely during the fight.
In Expert and Master multiplayer, boss maximum health uses a player-count factor rather than remaining at the solo value, while each participant can receive an individual Treasure Bag. Skeletron illustrates how durability scaling and reward sharing solve different group problems.
Iceborne added solo, two-player, and three-to-four-player quest settings and made difficulty update in real time with the quest roster. Alatreon's shared elemental checks show why health, team output, failure budget, and group coordination cannot be treated as one linear multiplier.
The Glyphid Dreadnought uses effective-health tables that combine Hazard level and player count, including its protective shell. The explicit matrix demonstrates why party size and global difficulty are separate axes that should be tested together.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub