base HP x (321 / 250)^(players - 1)
Use this formula only when base HP is known or entered by the player.
Use this hub for boss identity, progression context, source confidence, and readiness links before you commit to a weapon or party size.
Use this formula only when base HP is known or entered by the player.
The planner uses time to defeat and survivability confidence as conservative signals.
Fresh boss videos are useful leads, but official or direct source checks should decide guide facts.
These launch rows prioritize safe source boundaries over complete drop tables. Add exact drops after extraction.
Early/mid boss and Scrap Longsword drop context
Useful for planner examples because it connects directly to a weapon route.
Volcano boss route
Needs exact current HP and drop extraction before final route math.
Snow Highlands progression boss
Connects naturally to Snow Highlands ranged weapon paths.
Major route milestone
Use source-backed prerequisites before publishing a firm order.
Calm update watch boss
Recent update context means behavior and readiness notes should be rechecked.
Fresh update guide candidate
YouTube and update signals exist, but direct route details need source reconciliation.
A boss can be relevant because it teaches a biome, unlocks a weapon path, drops a material, or marks a readiness wall. The page should say which kind of relevance is confirmed. Do not merge rumored drops, video-only route tips, and official wiki rows into one confident checklist.
When a player is unsure whether a fight is next, the safest handoff is base HP, party size, estimated DPS, survivability confidence, and status plan. The planner can then show whether the build looks comfortable, risky, or too slow for the current route.
Compare source-backed weapon routes before choosing a fight.
Tier listUse role-first rankings with checked dates and confidence labels.
Update guideKeep fresh boss and keycard claims labeled until verified.