Damage assumptions
Use player-entered DPS in the planner until weapon attack speed, scaling, status ticks, and resistance details are fully extracted.
Use this page to separate source-backed formulas from player-entered estimates before turning a build idea into a boss-readiness plan.
Stats pages should help players understand uncertainty. They should not turn incomplete wiki extraction into exact-looking numbers.
Use player-entered DPS in the planner until weapon attack speed, scaling, status ticks, and resistance details are fully extracted.
The source-backed planner formula uses base HP multiplied by (321 / 250) to the power of players minus one.
Duration and level claims should link back to status-effect sources before they become calculator constants.
The planner is designed to work even before every Pilgrammed stat is extracted. Players can enter a conservative DPS estimate, the known or estimated boss base HP, and a survivability confidence level. That keeps the output useful without pretending the site has complete combat tables.
A later data pass can turn verified weapon stats, equipment bonuses, status durations, and boss HP values into presets. Until then, the stats wiki should explain what is known, what is estimated, and which source would be needed to make a stronger claim.
Use weapon pages to decide what DPS estimate belongs in the planner.
BossesUse boss pages for scaling, route notes, and missing exact-data labels.
Tier listRankings stay role-first until exact stat extraction supports stronger claims.
Short answers for exact formulas, safe launch data, and planner use.
No. This page keeps formula boundaries visible and sends exact readiness math to the planner only when source-backed or player-entered.
The boss player-count HP scaling formula is source-backed. Exact weapon DPS and status duration still need deeper extraction.
Use it as a source boundary before entering DPS, base HP, status plan, and survivability confidence in the Build & Boss Planner.