Orbalisk's - Wight King (PvP/Mythic+) v. 2.2 (Updated 02/10/26)

I think they’re waiting for people to hit max level to get more accurate Sims out and the damage meter is definitely not counting numbers properly because Blizzard has no idea how to make add-ons.

What I can trust is seeing the lesser ghouls summoned and spent reliably so I know the cycle for the damage outgoing is going to be close to peak. You want to be between 2 and 5 stacks of lesser ghouls so I think I’m pretty much in that range with a little bit over sometimes but that’s not terrible.

good example is timewalking, a lvl 21 is doing more dmg then a mythic geared 80.

Raidbots will be updated for the World of Warcraft: Midnight expansion

, but support will be phased, with only partial functionality available during the pre-patch period starting January 27, 2026.

Here is what to expect based on Raidbots support information:

  • Pre-Patch (Jan 27 - March 2026):

    • Sims: Will be “hit-or-miss” as SimulationCraft developers focus on level 90 character optimization. Some specifications may not simulate properly for level 80 characters initially.

    • Top Gear: Should work for most classes, provided the underlying SimulationCraft engine is working for that specific spec.

    • Droptimizer: Will be disabled during the pre-patch due to the complexity of the item level squish. It is expected to return when the full expansion launches.

  • Expansion Launch (March 2026): Full support for Midnight is expected when the expansion officially launches.

It is highly recommended to check the SimulationCraft Midnight Implementation spreadsheet or your class Discord for updates on specific spec functionality during the “in-between” pre-patch state.

1 Like

1.7 is having many momemtns of 2-3 seconds of inactivity.

Im thinking its the new cast sequence? as maybe its waiting for 1 of the skills in there to become usable?

Yes, unlike paladin or Warrior you’re not going to always have something to press because you need to wait for certain runes to come up. In order to cast festering strike you need to wait for two runes which takes a few seconds sometimes when you’re at zero. It’s not a DPS loss because you’re setting up the next burst mini cycle with the four scourge strikes spending the lesser ghouls. At least that’s my understanding of the class at the moment.

Sadly one of the main add-ons I used to show efficacy, castlog for details, is impossible with the current restrictions in retail.

I’ll look at this more over the weekend, but it might just be that.

Ideally, we just wait for raidbots to be usable and then I can try to get as close to Sim as possible like I normally do. I’m expecting this to be at least 90 to 92% to sim based off of what I’m seeing versus the numbers with the one button.

gotcha

also when midnight class changes go into effect on the 3/10

soul reaper also passively activates purify

whats ancestral call for uhdk?

Does that mean I don’t need to cast putrify?

im not sure– this is for midnight ONLY, not pre patch.

I think you will still need to cast is becasue soul reaper isnt always up, its either there for xecute phase or if talented into the node right beneath it when dark xform is used.

I also figured out whats going on with 1.7 st, and im not sure why the 1.7 ae one runs smoothly and differently

so when im watching my runes and runic power in the ST, its ultra rune starved, and that is leading to the 2ish seconds of no activity.

it is rarely if ever casting death coil,

so when the rune starved instead of using death coil as a filler til runes are ready, it has been jsut doing nothing until runes come up, and im sitting at 100 runic power

But by that point the rune regen is way too slow, so only 1 to 2 runes regen, are used and cant catch up

I added a block right before your castsequence that copies your last block of death coil, and now its running fine and hast been pausing

also—

I dont know what ancestral call is for UHDK that moo subbed in for soul reaper, do you know whats hes referring to

Ancestral call is racial for mag orc

Yeah what punahou said is correct. Sometimes you get rune starved real bad and the castsequence bugs. during chain pulls i cant get the 2 runes required for festering and then the macro breaks unless i use runic power manually to let the runes recharge. @punahou Ancestrall call is mag orc racials as starkey said.

Furthermore i didnt replace soul reaper for it i deleted soul reaper entirely. but added my racial to the top block:
Currently it looks like this:

Might try and do as you suggested and add a death coil block before the castsequence and see if that helps. Did you also do it with Epidemic for AOE?

ah lol a racial skill i was wondering wth that was

ya never play the horde only alliance thats prob why i wasnt fam with it

so the 1.7 ae for me seems to be running fine, it was only the 1.7st that has been rune starved.

ill restest 1.7 ae when i get back im off the the gym

Can you please explain how it breaks better to me so I can fix it?

1 Like

I’ll work on this tomorrow.

heyas

ok so when there’s a pause, the character stand in attack stance just auto attacking and there’s no skill activation for roughly 2 to 3 seconds

so during this time them resource bars show no runes, and they are all regenerating.

at the same time you see the runic power creeping up because noneunic spenders are being activated.

for me

thenrunic power actually gets to 100%eanwhile when it gets to 100 2 runes will have regened then the macro will kick in for both then repeat what I just explained

so I unsure if it’s hanging at the cast sequence waiting for runes because it doesn’t seem to progress past that and get to the last block that has death coil

when I stopped and look at the damage meter it will show 0 to 1 death coil used over 1.5 minutes

Hmm. The rune issue is by design so that you get the right amount of scourge and festering. The death coil I’ll look at the morning.

to put this in perspective

your previous macros for st have death coil as top dps skill

sheesh typing on my phone is a nightmare lol

I found the issue, working on it now.

1 Like

Ok, version 1.8 is up at the top. Please let me know how it works for you.

2 Likes