PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
PoB Conjoined Spire not looking at maximum totems from power charges for searing bond of detonation
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 open and closed issues by using the search function of the issue tracker
Check for support
- I've checked that the calculation is supposed to be supported. If it isn't please open a feature request instead (Red text is a feature request).
What platform are you running Path of Building on?
Windows
What is the value from the calculation in-game?
In game, when conjoined spire is allocated, totem life scales with maximum power charges.
(conjoined spire: scale totem life with max # of summoned totems, searing bond: max # of summoned totems increased by max power charges)
What is the value from the calculation in Path of Building?
The power charges are not in the calculation for damage, area or life (life is probably separate bug, already reported and I think fixed).
How to reproduce the issue
Use searing bond of detonation and get some maximum power charges, area and dmg are not scaling.
PoB for PoE1 build code
https://pobb.in/DEZ7ac0E7AvV
Screenshots
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
Load the linked PoB build and reproduce the Searing Bond of Detonation case with maximum power charges and Conjoined Spire allocated. Trace the calculation path for maximum totems, then verify that damage and area scale with the charge-based totem limit without regressing other totem calculations.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100