
Frostscythe multi-target priority not respecting Remorseless Winter
Closed this issue ยท 1 comments
Before You Begin
- I confirm I am using the latest version of the addon (outdated versions may have problems that were fixed on the newest release).
- I confirm I am playing on official Blizzard servers (not private servers).
- I checked for an existing, open ticket for this issue and was not able to find one.
- I have updated the issue title to clearly describe the problem.
- I am reporting an issue with the default specialization priority (not a custom or imported priority).
Specialization
DK - Frost
Describe the Issue
Frostscythe should trigger with 4 set and riders talent, only on 3 targets if Remorseless Winter is active, but currently Frostscythe never shows up on 3 targets
How to Reproduce
1.Enter the game and fight vs 3 dummys till remoreless winter buff is up
What is your information source?
Based on my own Raidbots Quick Sim results
Snapshot (Link)
Raidbots Sim Report (Link)
https://www.raidbots.com/simbot/report/s6MUArG5uLibAG74ZhZkEs
Additional Information
https://pastebin.com/k4f469JM Before pressing pillar of frost
https://pastebin.com/wKwX03NC after pressing pillar of frost
Contact Information
No response
Copying my reply from the other thread, didn't see that it was closed.
The APL defines frostscythe target counts very clearly in the frostscythe_prio
variable:
actions.variables+=/variable,name=frostscythe_prio,value=3+(1*(set_bonus.tww3_rider_of_the_apocalypse_4pc&!(talent.cleaving_strikes&buff.remorseless_winter.up)))
- 3 default
- 4 ONLY if 4-set rider AND you don't take cleaving strikes AND remorseless winter is NOT UP
Note this part: !(talent.cleaving_strikes&buff.remorseless_winter.up)
BOTH of those conditions MUST be false. This is like writing NOT cleaving strikes AND NOT remorseless winter active.
Every talent build on wowhead and icy-veins and in the Acherus FAQ takes cleaving strikes. That means frostscythe will only be recommended at 3 targets, never 4, regardless of remorseless winter. This is the behavior I see in-game.