Havoc Reborn

what I did for a work around for this stupid bug is I made a 2 macro’s with no Immo or eye beam so it will just do death sweep / CS and DB . and other with Immo along with DS . CS and DB . so I bounce around the 3 macros when one stops working . its a pain but it keeps my rotations going

The “spam” macro doesn’t fix it for you? It does for me. Whenever my main macro breaks I just switch to it on the fly (both are on the bar).

But, for me at least, the breaking is becoming less frequent. If it is tied to server population like I thought then we’re likely mostly past the huge influx for the expac launch. Hopefully things return to normal for everyone.

First and foremost love your macro and the work you are doing its fantastic. I’m using your macros and so far doing great. Things are progressing and as I start to look towards raiding I have been simming myself more lately. As of now I am ilvl 308 and Sim for roughly 8k dps. On target dummy though I burst high 10k plus. But settle down to roughly 6k for a full 5min test. That’s with food and pots. So i have been trying to figure out how i can get closer to the Sim numbers I should be getting. I fully realize I will likely never get Sim numbers on a target dummy. Though I fill like 2k difference is a large gap and that realistically it should be closer by half the current gap. I’ve been testing some things trying to up the dps and will let you know if I come up with anything useful once I do. Again great work.

@Ghoste, that’s still a bit large of a gap from what you should be seeing, but there could be a few factors at play.

Since you are simming your character it should also be giving you a plot of what your damage sources should look like. Annilhation, Auto-attack, Eye Beam, Blade Dance, etc in a certain order. Compare that to what the macro is doing for you. If something is in the wrong position, like Demon’s Bite is high for you, or Chaos Strike is too low, you can adjust the macro.

The macro is written in such a way that the line
/castsequence Demon's Bite, Demon's Bite
can be cut and pasted higher or lower in the macro depending on your haste. In general, the lower haste you have the higher up you should have that line. Where it is in the macro originally should be balanced for those who are using gear optimizer sites.

If you don’t want to fiddle with that, the other thing you can do is switch from Priority (which is why the Demon’s Bite line should be moved) to Sequential which will make the macro more random but also smooth out any over-active/under-active spells that might be happening for you.

BATHYM US KIL’JEADEN that’s my too. If you want to see what I’m running. And yes I did look at the damage order the percentages of the sum vs my test. I’m at work now and don’t recall the exact result. But annihilation was low as was death sweep. Both of which were high damage contributes. Auto attack or melee was high on my test. Demons bite was low as well.

You helped me alot there with your suggestions. I mess around with the macros alot changing things but knowing more about how they actually work and how to better prioritize things is great. Gives me a starting point to improve my dps.

Which macro should we be using now? The original that has been modified a few times, as recent as the 19th, or the one with the Imolation Aura fix?

The top of the OP if it works. It’s the most up-to-date. If you hang on IA, modify it as I list toward the bottom. If castsequences break for you, use the “spam macro” at the bottom.

EnixLHQ Not sure if this link will work but here is my Sim Report maybe you can look at it and see what changes I should make?
Baythm Sim

As you can see according to this I actually should be hitting 9k DPS. Test Dummy though has me between 6k - 6.5k

good evening, so I did some testing and I think BFA has changed how /castsequence works. I imported old macros, and they work with no hang up or issues. what is the difference? /cast instead of /castsequence. I notice this more on my main mage, that all the spells are /cast in a order and then have a loop number. Therefore, I think this maybe a WOW issue?

[quote quote=63993]EnixLHQ Not sure if this link will work but here is my Sim Report maybe you can look at it and see what changes I should make? Baythm Sim
As you can see according to this I actually should be hitting 9k DPS. Test Dummy though has me between 6k – 6.5k[/quote]

Well, for one, your sim includes all buffs (potion, food, rune), bloodlust, as well as all party buffs from other classes. So, unless you are in a party with a warrior and have applied all your top raid buffs to get your 6k against a target dummy, I’d say you are fine. Re-run the sim and make sure you uncheck every buff and circumstance you are not actually in when you are fighting the test dummy.

It is a WoW issue, but it’s not intended. None of the API documents say that castsequences have changed and should work in any way different than before BfA. So it’s safe to say their current behavior is a bug. Especially since not everyone has the issue, the issue appears and disappears for those who have it, and things like server population all make the issue behave differently. So, it’s pretty clear it’s broken internally somewhere.

As for what’s different between /cast vs /castsequence as far as WoW is concerned, that is a topic I got into many pages back (and in other places on this forum and our Discord) but the TL;DR answer: A /cast is just that, cast this spell. It requires no logic, no computations, nothing. I just casts or it doesn’t. A /castsequence, however, requires WoW remembers your progress through it, if a previous attempt was successful, and the cooldown of all abilities listed in it in order to not progress further than the spell on CD. In short, it has to store information for your character. Multiply that for every player using a castsequence on your server. That data is breaking. Likely because there’s too much of it right now.

So I’m currently 304 ilvl (not that high). When I sim my character it says with 0 buffs I should be doing around 6,020 DPS…On a training dummy I’m doing about 6.5-6.9k DPS after about 5-8 minutes of holding the macro. I can honestly say this is the best macro I’ve used. Thanks again Enix :D!

::thumbsup::

Great macro!!! But i have a problem: Sometimes I get hungry for fury. How to solve this? The spam macro fix this? Apparently I put the main macro and the macro spam to run together, it’s going well at 30ms, but I’d like your opinion.

Sorry, my english is rusty haha :slight_smile:

[quote quote=64032]Great macro!!! But i have a problem: Sometimes I get hungry for fury. How to solve this? The spam macro fix this? Apparently I put the main macro and the macro spam to run together, it’s going well at 30ms, but I’d like your opinion.
Sorry, my english is rusty haha ???[/quote]

You should never starve. It’s impossible. Like I’ve said numerous times, it’s okay to spend all your Fury as long as you build it back up again, which the macro will do.

If you feel it’s taking too long to build back up, take the line /castsequence Demon’s Bite, Demon’s Bite and move it up the main body sequence.

Please refer to earlier posts in this thread about that.

How would I take eye beam out of the macro? Love your macro but not really sure on editing without breaking the macro.

Thnx again for an awesome macro Enix! This macro made me play DH for BfA. Its cool to top dps meters most of the time and actually keeping up with others like 30 ilvls higher =)

As of today Eye Beam is not being allowed to channel its full duration. Is this s glitch in the game, or something the macro can be adjusted for? It was working fine till today. Also, when I hold ALT the Retreat/Charge works, if I hold SHIFT all it does is stop my macro and I sit there like a dumbass till I let go. :wink:

  • Yes, I’m using the un-edited OP Macro.
  • Yes, I’ve tried removing GSE and reinstall. I even used an older version to check and see if an update killed it.

Any ideas?

About one minute of Details: 4.0K

  1. Trial of Ruin 42.5k
  2. Annihilation 40.5k
  3. Death Sweep 32.0k
  4. Melee 30.8k
  5. Blade Dance 27.6k
  6. Chaos Strike 22.3k
  7. Immolation Aura 15.5k
  8. Demon’s Bite 10.1k
  9. Chaos Nova 4.7k
  10. Filthy Transfusion 3.5k

Eye Beam is canceled so fast, it doesn’t even do any damage at all.

[quote quote=63711]Hi boys and gals!
I figure I would try to help out as I’ve been using this for a while. I spent some time today simming and modifying things just a tad.
Here is what I have now. I am 333 Ilvl. Sim= 8,389 DPS Target Dummy = 8.5k ish I have 2 Proc Trinks so may be getting lucky. ** This is with NO buffs – If you sim your character make sure you set no buffs to avoid confusion on why you are low.
**The prior Post about Eye beam getting Canceled is because of Immolation Aura. Fixed in the following. I personaly do not have problems with lock ups from Immo Aura like Enix mentioned.
30ms / Talents= 1.3.1.1.2.1.1 / 3x Revolving Blades Traits (simming the highest)
/cast [nochanneling] Immolation Aura /castsequence [nochanneling,combat] Blade Dance, Chaos Strike /castsequence [nochanneling] Eye Beam, Chaos Strike /cast [nochanneling] Chaos Strike /cast [nochanneling] Demon’s Bite
Let me know what you guys think.[/quote]

Hey TheLaziest, been using the above for quite a few dungeons now (around 100). My only change is that I like to cast eye beam manually for maximum aoe. So far I’ve got top damage/dps in every random heroic (now 325ilvl), naga set to 30ms. Only issue I have is when the macro randomly hangs in dungeons, then I use Enix’s spam macro to a button and /reload. Trying to figure out what conditions cause it, I’ve been /reload 'ing as soon as I enter the dungeon to be safe, no issues so far but I’m sure it will happen again.

@Hazmat-13 You might have a trinket with an active on-use ability that’s on the GCD. If so, when it’s ready it’ll pop and interrupt everything. You can uncheck the “trinket” slots in GSE when viewing my macro and see if that helps, but you’ll lose the use of the trinket without some other activator.

@Luigieee Yep. Welcome to the club. Would be sure nice if Blizz got around to fixing whatever this is.