Mythic warrior struggling

[chilly stream]

Hello, feels like I'm doing something fundamentally wrong or some big mistake but I have tried to figure it out and I really don't get it. Maybe I'm just washed and don't cast enough but that would be nice to know too ig.

Realized I trolled a bit with talents and played "Vicious Contempt" instead of "cold steel, hot blood" on STbut I doubt that will make an insane difference?
Besides that the only mistake I know I make sometimes is that I don't press RB after BS but i read that it was not a huge difference so I've been slacking a bit but besides that I truly have no idea.

Here is from todays heroic run on fract where I got pretty destroyed by the other warriors which made me make this post. I know heroic is not super relevant and I was not 100% locked in right but I also have no mechanics to blame for my low damage. https://www.warcraftlogs.com/reports/L4QkJMZjnYDaAWyF?fight=last&type=summary (arbosmash)
and this is from one of our better progress pulls on nexus king mythic which we are currently progging
https://www.warcraftlogs.com/reports/ZqtQNg9MHKbfY6yx?fight=38&type=summary

Idm if you only analyze one of these, I'm very thankful for any help and advice I can get.

[open anchor]

you'll probably want to sim and adjust your stats here and there (likely trade some for vers), and like you said fix that cold steel talent (about 55k dps lost there) .

biggest thing that stands out to me is your opener is soft, in large part because you didn't use a potion. unbuffed 30 seconds of a sub 3 minute fight is big.

your rotation isn't bad, but you do need to try and follow every single bladestorm with at least 2 RBs, 3 or 4 if you gets resets, i wouldn't go to 5 but that's me. your rampages hit for 3 mil on average, xlights hit for 3.5, and he's getting more reap the storm procs because he's RBing more so like 150k dps gained on his part from that passive during the fight. ultimately your damage chart should have RB at the top and a big gap down to rampage. if you get lots of execute procs that can be #2 on the list, you both got a pretty normal amount of execute procs but his hit harder because of potion and 2 item levels

xlight also got 2 power infusions so there was nothing you were going to do to match his damage

[peak kestrel]

your rotation isn't bad, but you do need to try and follow every single bladestorm with at least 2 RBs, 3 or 4 if you gets resets, i wouldn't go to 5 but that's me
no, you're supposed to raging blow while enraged. You do not need to and you do not want to force multiple raging blows when your enrage runs out. That nuance is very relevant.

ultimately your damage chart should have RB at the top and a big gap down to rampage
This is a 50% p2 wipe, meaning that he mainly fought single target or 2 target cleave. RB climbs the damage meters (along with reap the storm) when fully playing the p2 platforms. If anything its his execute damage that's kinda on the low end, but we naturally get more exe damage later on in the fight due to us wanting to click exe at 1 stack of MFE in exe phase over raging blow. His RB damage is fine.

If I was @chilly stream and i was trying to improve, then your advice would not be very helpful, mr boomerwow

his main rotational issue is that he's using rampage at 80-115 rage too much, when he should be rampaging more at 115+ (assuming that you can get there while enraged)

Also nexus king logs are weird as fuck because if the person that logs the fight is on the opposite platform, then damage gets whooshed, thins dont get tracked properly. It's a known bug with the fight and you need to always be aware of this

[open anchor]

You are generally enraged after bladestorm because you've just hit 2-4 bloodthirsts and bloodthirst has a chance to enrage, but even if tou weren't enraged tou still follow bladestorm with RB to buff your already buffed next rampage

[peak kestrel]

yes generally, but not always. especially since improved whirlwind doesnt always run 2x deft experience. Mr Arbosmash did, but that's not a rule to go by.

[open anchor]

I'm referring to the fractilus fight linked first, so I've got no opinions on whirlwind except it sucks if you're so unlucky that you have to use it lol

[peak kestrel]

also yea you got affected by the nexus king log bug, Arbo. What happens is that the opposite platforms of the person logging freeze within the log, you just end up stuck there, causing ur logged damage to sink, despite you actively doing damage

[peak kestrel]

there his main issue is rampaging below 115 rage despite being enraged and having RB up

Like that's genuinely it

he even got more opportunist procs than xlight lol

[open anchor]

Said differently, he should RB more, especially after bladestorm

[chilly stream]

hi, thank you so much for the input! I will make sure to think about that. I feel like I would overcap a lot of rage if I don't press rampage earlier but ig that's not an issue I need to worry about?

[peak kestrel]

"just RB more" isn't very good advice and you should realize that

[open anchor]

What other button would you prefer he use to get to 115 rage

[peak kestrel]

Mate you didn't specify the 115 rage rule that we all adhere by. You likely didn't even check whether that's relevant in his case or not because all you looked at is other people clicking more Raging blow and dealing more damage with that ability.

If you want to give proper, sound and helpful advice, then tell him to not rampage too early while enraged, to focus more on saving excess rage by clicking the two relevant generators (RB and Exe (given the conditions of course)) instead of Rampaging early instead of just saying hurr durr RB more becuase other people did more RB damage than you

[peak kestrel]

The entire reason we specify 115 rage is to avoid overcapping while avoiding rampaging too early. It's what we found to numerically work best

But as soon as enrage drops, you click rampage. Never forget.

[chilly stream]

Okay thank you again!

[peak kestrel]

also thank boomerwow pls, his input is solid

[chilly stream]

yeah sure ofc! @open anchor thank you!

[open anchor]

Imo brutal finish hero talent is worth buffing even with an unenraged RB, but otherwise i think we're all on the same page and yw 😄

[peak kestrel]

I mean that's not something you can just have an opinion about, it's numerically not worth to do yk. Slaughtering strike increases rampage by 20% per stack and your additional raging blow(s) dont benefit from the enrage buff if it falls off. Enrage is a flat 50% or higher (depending on your mastery) buff to all your damage + you get haste from frenzied enrage

If it was numerically better to spam RBs regardless of enrage, then we would

If you'd like, i can go and run a custom APL that spams RB regardless of enrage so you have numerical proof of it being worse

https://www.raidbots.com/simbot/report/3bxVfNECn9nhYm6psxThC6/simc
https://www.raidbots.com/simbot/report/4yU96tzQ4FF6iYwYiSwSkY/simc
@open anchor

[open anchor]

Question: is the sim choosing to wait until 5 slaughtering strikes are present or is it going to 3-5 depending on procs?

Or i should say 2-5

[peak kestrel]

actions.slayer=recklessness
actions.slayer+=/avatar
actions.slayer+=/execute,if=buff.ashen_juggernaut.up&buff.ashen_juggernaut.remains<=gcd
actions.slayer+=/execute,if=buff.sudden_death.remains<2&!variable.execute_phase
actions.slayer+=/thunderous_roar,if=active_enemies>1&buff.enrage.up
actions.slayer+=/champions_spear,if=!cooldown.bladestorm.remains&(!cooldown.avatar.remains|!cooldown.recklessness.remains|buff.avatar.up|buff.recklessness.up)&buff.enrage.up
actions.slayer+=/odyns_fury,if=active_enemies>1&talent.titanic_rage&buff.meat_cleaver.stack=0
actions.slayer+=/bladestorm,if=buff.enrage.up&(talent.reckless_abandon&cooldown.avatar.remains>=24|talent.anger_management&cooldown.recklessness.remains>=15&(buff.avatar.up|cooldown.avatar.remains>=8))
actions.slayer+=/whirlwind,if=active_enemies>=2&talent.meat_cleaver&buff.meat_cleaver.stack=0
actions.slayer+=/onslaught,if=talent.tenderize&buff.brutal_finish.up
actions.slayer+=/raging_blow,if=buff.brutal_finish.up&buff.slaughtering_strikes.stack<5&(!debuff.champions_might.up|debuff.champions_might.up&debuff.champions_might.remains>gcd)
actions.slayer+=/rampage,if=buff.enrage.remains<gcd
actions.slayer+=/execute,if=buff.sudden_death.stack=2&buff.enrage.up
actions.slayer+=/execute,if=debuff.marked_for_execution.stack>1&buff.enrage.up
actions.slayer+=/odyns_fury,if=active_enemies>1&!talent.titanic_rage
actions.slayer+=/bloodbath,if=buff.bloodcraze.stack>=1|(talent.uproar&dot.bloodbath_dot.remains<40&talent.bloodborne)|buff.enrage.up&buff.enrage.remains<gcd
actions.slayer+=/raging_blow,if=buff.brutal_finish.up&buff.slaughtering_strikes.stack<5&(!debuff.champions_might.up|debuff.champions_might.up&debuff.champions_might.remains>gcd)
actions.slayer+=/rampage,if=rage>115
etc other shit that is less relevant for this chat

it follows the normal APL except it spams as many RBs as possible after bladestorm

when you run out of raging blows, you rampage

but it ignores enrage completely

If your suggestion is to click bloodthirst, execute, t-roar and whirlwind until you get to 5 stacks of slaughtering strikes then idk man

[open anchor]

No i wanted to make sure it was not doing that

My suggestion was 2-4 after bladestorm assuming rb reset itself. I wish that sim would rule out 5 rbs, but it's close enough. It is a 22k dps loss to use my suggestion if you can think as fast as a computer.

[peak kestrel]

You can easily edit the slaughtering strike buff max from 5 to 4

but it will barely do any difference

as a 5 stack of SS doesnt happen much

[open anchor]

It's all immaterial really. 2 after every bladestorm is fine

3 or 4 is an unnoticeable dps los

[peak kestrel]

it's unnoticeable with this build yea but the moment you drop deft experience in favor of something like Focus in Chaos + CSHB and 2x critical thinking (which might sim better than 2x deft depending on mastery in gear), you have to adjust because the damage loss increases

Cause then you leave bladestorm with less enrage uptime on avg

it's generally not a good habit to drop enrage, that's all that's very relevant. If you end up clicking one RB outside of Enrage on accident thats fine after bladestorm but it's something that we should generally avoid, making this a force of habit is not advisable to any degree

🤷‍♂️

[open anchor]

@peak kestrel i thought i was done but i have to address the sims you linked - sorry.

i'm not sure how to alter sims but looking at the damage breakdowns and buff uptimes of the two sims you linked earlier shows that the sims are running basically identical rotations (for instance 151 raging blows compared to 149) and enrage procs 1 MORE time on the "ignore enrage" example. both characters rampage 89 times and both get 29 procs of reap the storm as other examples. so it seems however it was altered, they simply removed some enrage bonus damage that DID exist instead of having enrage fall off here or there but adding in more reaps and opportunist procs, or modifying the rampage damage that would result from several more slaughtering strikes. it's just not a realistic sim

[peak kestrel]

sample size diff

the avg damage is accurate

the example of one run that achieves this damage is a sample size of 1

millions of samples to find the avg

[open anchor]

the alteration is the problem. how does it "ignore enrage" if enrage has the same uptime

[peak kestrel]

All the altered APL does is prefer to click raging blow when brutal finish is up over rampage no matter what

we usually stay enraged for all raging blow stacks anyway

not all of em

but most

the sim simulates millions of attempts at this

and averages a lower damage than the current apl we abide by

but in one singular shown attempt, it shows the same overall uptime

[open anchor]

clearly that was the intention but both action lists have the same conditions for when to use rampage and raging blow