#Fury log help (rage overcap)

1 messages · Page 1 of 1 (latest)

mental apex
#

Hey, follow up log posting related to this question #fury message

Last week's fractilus (NM) at 695 ilvl with 4p https://www.warcraftlogs.com/reports/gVtaK3ZLW9AznTmb?fight=88&type=damage-done&source=987
I was focusing on following the wowhead prio closely in this run. Can't remember exactly if it felt like a decent pull since it was a week ago
Comparing myself to other logs, it looked like I wasnt casting rampage enough / wasting too much rage so today, I did a follow up run trying to overcap less and not doing the rb spam after bladestorm nor exec conditions if it would overcap
Here's a log from loomi'thar doing this with 707 ilvl https://www.warcraftlogs.com/reports/RGWXv7Z2cQr9VhJ3?fight=11&type=damage-done or nexus king https://www.warcraftlogs.com/reports/RGWXv7Z2cQr9VhJ3?fight=39&type=damage-done&source=165
I wish I could send frac but I forgot to respec after soul hunters lmao

Any pointers towards mistakes I'm making in this would be appreciated 😊 (since I know i'm still doing a bunch looking at the other fury from today who was not overcapping rage a lot)

mental apex
misty isle
#

You don't need to worry too much about overcapping rage really, due to how our rotation works you will always see a large amount wasted on RB / Exe / BS as they have a higher priority than spending with Ramage under certain conditions.

#

Assuming you are using the Execute conditionals WA, you will always press it if you are enraged even if you are at 130 rage which will case you to lose some due to the rage refund.

#

After Bladestorming you will want to spam RB as much as possible before using rampage (unless you are going to drop enrage), this is to take advantage of Brutal Finish + Slaughtering Strikes