I am working on leveling my DK, and have been developing this sequence as I went along. I just hit 80 and I’m wearing full equip from siren isles. Currently 592 ilvl. I’ll update this post with any changes that I make.
This probably needs some fine tuning, so give me your opinions and I’ll take them into account as I work on this.
Modifiers: (I will probably change these as I streamline the sequence)
CTRL: BREZ while Mousing Over a friendly DEAD Target
ALT: Death Strike (This is for extra healing above the normal rotational Death Strikes)
Good work on the macro, do you know how to fix the problem that occurs with Heart Strike? Sometimes the sequence get stuck there because it change spell name to Vampiric Strike…
It works fine for me. The original sequence I wrote even included vampiric strike as a seperate spell but I noticed that it was just converted to Heart strike automatically when i viewed it as a compiled sequence.
I have noticed this issue with one spell turning into another on use or on a proc, but it always seems to be a wow issue and not a sequence issue.
As long as you end combat without heart strike being swapped to vampiric strike, there’s no issues. The shitty part is, that it’s not that easy to control that.
Haven’t seen any other way to solve the issue, and I wouldn’t call what I said a solution either lol.
I started the raid with an ilvl of 606 or 607, so you can guess my dps was not very good at all, but that didnt matter since i was tanking.
Here’s the character’s log page, i’ve only done 1 heroic on him I think. https://www.warcraftlogs.com/character/id/91673389
it’s trying to use your trinkets. if the trinket is on cd then it will show you the error message, but it should still work regardless.
If you want to remove that, find the block that contains the /use 13 and /use 14 parts and just delete it. That way you can use your trinkets manually. I also use Blood fury for orc in the same spot.
I tanked an entire heroic Nerub’ar Palace run without any issues, and nothing has changed since then. As far as I know, nothing has been changed lately with the hotfixes that have gone in either.
Not sure why you’re having problems.
I probably wont be doing much updating of this sequence in the future either, since I like tanking on my Paladin and Warrior a lot more than on the DK.
Nope, tried that, tried having a section dedicated to vampiric strike and one for hearts strike.
The issue seems to be either internal from GSE, or something that doesn’t really work as it should in blizzard’s code.
The issue is that whenever you end combat with VS active, GSE overwrites heart strike, something that should not be doing, with VS.
There’s no workaround atm. @Venjense That’s because you don’t get to end combat as much as you do on M+ with VS active, but if you do, it will happen.
EDIT: After some more exhaustive testing, it happens with a few other “transformable” skills, for example, storm strike from shaman.
Something’s broken.
I’m having this same issue with Vampiric Strike / Heart Strike / Rune Strike on blood and the blood thirst on fury when reckless’ed has this been acknowledged yet or is there a work around?
Yes, a very reliable fix is to create a wow macro with the skill that transforms and put the name of the macro on the GSE box.
Example, name the macro HEART make it a /cast heart strike type HEART in the GSE box.
From that point onwards it doesn’t matter that you end combat on vampiric strike, gse will cast the HEART macro, that will cast heart strike, which is gonna cast vampiric because wow macros work like that.
Do this with every transformable skill so you don’t lose hair like I did looking for a solution that doesn’t exist lol
Yeah the macros that include skills that transform will break when meeting certain conditions (ending combat with a transformable skill transformed) So you need to make them on the wow macro system and then use that in the sequence. It’s been an issue for a while, but since it has a solution, it must not be a priority.
I didn’t realize how old this thread is. I went ahead and opened a bug report using it as Blood DK let me know if I got it all gathered up hopefully it’ll get fixed soon!