Chance-weighted average attack/cast time of Retaliation Skills
Maintainers usually reply within 8 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
The issue provides a Ruby sample for calculating chance-weighted retaliation timing but names no project files or tests. Start by locating the retaliation-skill reuse and attack-time calculations, then determine where the requested average belongs; done means retaliation skill reuse is represented in the planner's timing results.
Written by the indexing model from the issue text.
Description
Check for duplicates
- I've checked for duplicate open and closed issues by using the search function of the issue tracker
What platform are you running Path of Building on?
Windows
Is your feature request related to a problem?
PoB cannot consider retaliation skills reusage.
I have developed a formula and calculation algorithm for the average attack time, taking into account the cooldown probability of retaliation skills, so please consider implementing this.
Describe the solution you'd like
Here is some sample code written in Ruby
puts "attack time ?"
a = gets.to_f
puts "usable time ?"
u = gets.to_f
puts "usable time mod% ?"
u = u * (1 + gets.to_i / 100)
puts "cooldown?"
d = gets.to_f
puts "chance to multiple retaliation?"
r = gets.to_f
x = (u/a).ceil
puts "max number of attacks " + x.to_s
avg = 0.0
for t in 1..x do
avg += (1 - r**(t)) * (a + ((d - a) / t)) # [The probability that reuse will end after the t-th use ]*[Average attack time after t uses]
end
avg /= x
puts "avg,attack time : " + avg.to_s
Describe alternatives you've considered
No response
Additional context
No response
- Dominant language
- Lua
- Stars
- 5.5k
- Forks
- 2.4k
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from PathOfBuildingCommunity/PathOfBuilding
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
PathOfBuildingCommunity/PathOfBuilding#10420 ·
Maintainers usually reply within 8 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
PathOfBuildingCommunity/PathOfBuilding#10395 ·
Maintainers usually reply within 8 days
-
bug: accuracy
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PathOfBuildingCommunity/PathOfBuilding#9911 ·
Maintainers usually reply within 8 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PathOfBuildingCommunity/PathOfBuilding#7548 · 4 comments · 1 reaction ·
Maintainers usually reply within 8 days
-
bug: behaviour
Difficulty 3/5 1-2 days Newbie friendliness 54/100
PathOfBuildingCommunity/PathOfBuilding#10411 ·
Maintainers usually reply within 8 days
All issues in PathOfBuildingCommunity/PathOfBuilding
Similar issues
-
bug reviewed-by-AI
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
olimorris/codecompanion.nvim#3508 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fitzforge/polestar#1825 · 1 comment ·
Maintainers usually reply within 1 day
-
Data Correction Forever
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
obsidian-nvim/obsidian.nvim#1027 ·
Maintainers usually reply within 1 day