PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
[dev] Winds of fate should change DPS, not average hit
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
Check version
- I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
How is Path of Building expected to behave?
When you deal 0% damage with non-crits, your average hit damage should not go down. It causes issues with ailment estimations. Instead, we should affect DPS.
Technically speaking, on average, it is true that the average damage goes down. However, in practice, we use average damage for both average damage per hit AND for average damage per hit that does damage, which is relevant for things like ignite, bleed, shock, etc.
How does Path of Building behave?
0% damage from non-crits when you're at less than 100% critical strike chance lowers the damage of average hit, which breaks ailments and leads to misleading breakdowns for things like burst damage, even though the final value is correct there.
How to reproduce the issue
No response
Character build code
https://pobb.in/MCD6Rlt0HAig
Screenshots
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified in the issue. Load the linked build code, trace the DPS and average-hit calculations for non-critical damage under Winds of Fate, and compare the ailment estimates and damage breakdowns before and after the change. Done means non-critical damage no longer lowers average hit damage while the final DPS remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100