PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
divergent elemental proliferation not counting number of ailments
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
What is the expected behaviour/value?
Divergent elemental proliferation appears to be using if frozen/shocked/ignited rather than a count of the number like the taming does not sure if this is accurate to the in game interaction or not
What is the actual behaviour/value?
I expected Divergent elemental proliferation to be a comparable damage up to a the taming ring especially with a build that should be achieving large numbers of inflicted ailments on targets in a pack
How to reproduce the issue
set an elemental damage skill with divergent elemental proliferation
try to set number of elemental ailments on the target
equip a the taming ring
set number of elemental ailments on the target to a large number (100+)
equipping/removing the taming with be a major change to damage
enabling/disabling the divergent elemental proliferation will be a minor damage change
also notice that is the enemy shocked/frozen/ignited to effect divergent elemental proliferation while without them ticked it is counted as not effecting damage
Build code
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
Start by reproducing the build from the linked Pastebin and compare Divergent Elemental Proliferation with The Taming while varying the target's elemental ailment count and frozen, shocked, and ignited states. Trace the ailment-count and damage calculations used by these two effects; done means the behavior matches the intended in-game interaction and is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100