Planning walkthrough

How to read solo and party estimates

Use measured damage, encounter work and explicit party assumptions without treating a HEXA score as damage per second.

Start with measured damage

A HEXA score summarizes a character under a reference setup. It does not identify a class rotation, a burst schedule or the share of a fight spent dealing damage. A clear-time estimate needs a matching damage measurement, its duration and the encounter work that damage must cover.

Keep the class, GMS version, test target, buffs and party environment attached to the measurement. A recording measured on a different target is not automatically a boss-DPS input. If the model cannot reconcile those conditions, a missing result is more useful than a precise-looking guess.

Solo and party use the same work

For a shared target, each party member contributes their own measured rate under the assumptions that apply to them. Adding headline scores, multiplying one character by the party size, or adding a support multiplier already included in the measurement would count damage incorrectly. The same engine evaluates solo and actual party inputs separately.

For simultaneous rooms, assign members to the rooms they can damage. A faster room does not lend its unused damage to a slower room automatically. Sequential phases instead consume time one after another. Shields, healing, invulnerability and forced waits add work or time that a starting HP total alone does not describe.

Read the range and the timer separately

A conditional time range describes the supplied damage, uptime and encounter assumptions. A comparison with the fight timer needs an admitted timer too. Neither is a win probability: deaths, execution and mechanics can still prevent a clear. An independently observed solo run and party run are needed to test gameplay accuracy.

When a prediction is unavailable

Look at the missing input or unsupported encounter condition, then use the boss reference to decide what to measure next. A nominal HP reference is useful for understanding scale, but it is not a current calibrated score-to-time curve. We keep historical references and publisher-confirmed mechanics identified separately.