these meters 
2 Likes
yep both ST and AE working fine now ty
2 Likes
Awesome. Please let me know if anything else needs tweaking.
1 Like
Thank you.
need 20 characters 
is the pvp one tweaked as well with these changes cause im seeing a LOT of soulreaper?
Yes. Soul reaper should cast when it procs right? Or is that not accurate?
Should it be removed for AoE?
If you’re testing on training dummies that may not be the best. Use the PvE mob Kelpfist for a more accurate ST rotation assessment since he isn’t always in execute range.
from what im reading
In World of Warcraft PvP, Soul Reaper should be used on targets below 35% health, acting as a dedicated execute ability. It is not designed to be used on a random proc, but rather as a planned burst window to finish off opponents.
i could be wrong, since u CAN use it on all %, but i do not know if thats the purpose of it, love some opinions on it.
and i tested bg’s 
not dummy , maybe i should put it on a mod.
I thought it wasn’t usable unless they were at the threshold like execute or on proc.
When Soul Reaper procs—typically via the Reaping or Putrefy talents—the primary benefit is that it becomes usable on any target regardless of health percentage.
In PvP, here is how you should handle those procs:
Treat Procs as Free Damage: A procced Soul Reaper doesn’t just bypass the 35% health requirement; it often triggers automatically or resets its own cooldown, saving you a Global Cooldown (GCD) and a Rune. Use these procs immediately to maximize your sustained pressure and keep your Virulent Plague damage buff active.
The “Execution” Trap: Even when it procs, the massive explosion damage still only occurs if the target is at or below 35% health after 5 seconds Wowhead. Do not expect a “one-shot” on a high-health target; the proc is mainly useful for the 20% increased disease and minion damage it provides for 8 seconds.
so if iread this right, its usefull on procs but it doesnt only use on 35% or less ( u can use it above ) , and not only when it procs. but maybe as written above, thats not a bad thing ?
Yes so it should run like it is for ST. Fire off on proc or 35%.
I’ll check when I get home from church if it’s in the AoE sequence. If it is I’ll remove it as that’s an oversight.
1 Like
It is in the aoe, but in arena, i very rarely use aoe.
i used the wrong sequence. it was on tab 2 inst or 3 although i saved it, guess i didnt wait for confirmation, and was still pending when i closed it. /faceplant
works as intended apologize for the confusing posts.
even with basic honor gear, i do top dmg every time in arena 
so thank you !
I removed Soul Reaper from the AoE sequences and updated it as 2.0 at the top!
2 Likes
sick i love it, in aspirant pvp gear vs full conquest. ( mage , hunt , pally )
edit : 2nd one while spamming death strike vs 2 mages
changed a few talents tho, most used according to Unholy Death Knight 3v3 PvP Guide - Midnight Pre-Patch which made total sense. dmg is even higher now.
And again, now i have 2 pieces of conQ, and they are all max /even bis geared and gem’d
1 Like
Correct me if im wrong, but its not even talented ( as shown on your talents snapshot ) from OP
What id do, is just disable the block and carry on.
So been testing 1.9 for a while and got the same thing happening. what i would love to know if i am the only one encountering this or if its something else. If its just me than i will reinstall gse so that my options are back to default.
What did you use in your dungeon yesterday sir orb?
I use synapse and a razer mouse for pressing the macro and i’ve tested 50ms, 100ms and 150ms.
Maybe some GSE setting i’ve turned on/off that makes it do this
Hmm, I’m not sure what problem you’re having then, I haven’t had any hang ups whatsoever in 1.9 or 2.0. There is some awkward downtime every once in a while where you’ll have two to three seconds where nothing can fire off because there’s no runes available and no runic power available, but outside of that it should be cycling totally fine. My DPS is significantly higher and out beat my warrior for the first time. My paladin has the same downtime, but after the recent patch update it’s been really high up there on DPS as well with version 2.3 of my ret sequence.
I won’t be able to give you a hyper accurate to sequence until I get raidbots up and running after we hit 90.
Also, be careful putting any of your macros under 100 milliseconds because if you leave it at 50 or 75 or something, usually the game client will stop accepting your inputs and do nothing.
2 Likes
Not everything is about pve. Its in the PVP block. And its fixed now
Thanks for the heads up! Ill set my ms back to 125ms.
I just ran a HOA after reinstalling GSE (patreon build) and clearing my SavedVariables.
No hickups, nothing 
So i probably fudged something up on my end.
Thanks for all the support and the quick changes yesterday.
Moving the first block up mightve been not necessary since it seemed to be a user error. So sorry about that so thats up for testing
Overall dmg of the +10
(hunter was 169ilvl vs me 150)
1 Like
I mainly just PvP so panel 3 is my go to on this sequence. The change is just modifiers.
ya id rec to keep it and disable the block because in midnight we will use soul reaper on cd because it will passively also proc putrify