You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PoB currently only calculates Molten Strike dps for a single ball hitting. This overlap calculator has existed for a number of years and it would be nice to have this integrated into pob instead of having to copy over values to estimate your dps. This is especially tedious for Molten Strike of the Zenith, for which you'd need to use the calculator twice (normal balls and 5th attack balls) and then take a weighted sum of the two values.
Describe the solution you'd like
Add skill parts for Molten Strike and its transfigured version for average dps considering overlaps on a single target. Also add a total average for Molten Strike of the Zenith considering both normal and 5th attack ball hits.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Check for duplicates
What platform are you running Path of Building on?
Windows
Is your feature request related to a problem?
https://moldydwarf.gitlab.io/MoltenStrikeDPS/moltenstrike-simple.html
PoB currently only calculates Molten Strike dps for a single ball hitting. This overlap calculator has existed for a number of years and it would be nice to have this integrated into pob instead of having to copy over values to estimate your dps. This is especially tedious for Molten Strike of the Zenith, for which you'd need to use the calculator twice (normal balls and 5th attack balls) and then take a weighted sum of the two values.
Describe the solution you'd like
Add skill parts for Molten Strike and its transfigured version for average dps considering overlaps on a single target. Also add a total average for Molten Strike of the Zenith considering both normal and 5th attack ball hits.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: