Disc Priest Wand GCD/Smite Bug

I know there have been posts about this before but there has been ZERO Blizzard acknowledgement. I also submitted a bug report and a ticket - the GM said he couldn’t do anything and directed me here.

This is a game-breaking bug for disc priests. Equipping a wand creates a split second GCD after cast smite. This breaks chain casting and throws off our entire rotation. Because wands are a ranged weapon, they can auto-attack even when we are at a distance from our target. This auto-attack leads to a GCD.

Please look into this bug so it can hopefully be fixed. There is no valid reason for this to be considered “working as intended” - daggers and maces do not cause this to happen. Yes, I understand that we can just get a dagger or mace (which I did - I dropped 110k gold on a boe dagger to replace the FOUR wands I’ve gotten from emissary and other quest rewards in the past two weeks) but we shouldn’t have to. All the weapons we are able to use should be equally beneficial. We should t be penalized for using wands.
2 Likes
Welp. Got a 370 wand which would be a HUGE upgrade. But I cannot use it due to the bug. Super annoying. A swift fix is necessary.
Hey Blizzard, can we please get some attention here? I got ANOTHER 370 wand today, this one from the Warfront that I've been waiting for for weeks now. Can you imagine the let-down when I saw that my big upgrade was...... another wand that I can't use because this is still bugged?

Please fix this!
Decided to test this out on my priest - the wand doesn't even have to be auto attacking. In fact, my auto attack will not STAY on with the wand between spell casts, but will still get the weird split-second GCD.

That is, I can start just auto attack with the wand, cast a spell, and the auto attack will stop.

Casting smite, and only smite, will cause the mini-GCD (which tells me it's definitely a bug).

Really pretty annoying.
1 Like
Update:
I saw some folks on reddit or MMO Champ (can't remember which) claim it's working as intended (yeahno), and to do a /stopattack macro to fix it.

Used a macro, still does it, though now it's not EVERY cast of smite, just some of them.

A workaround meanwhile is the trick of starting your next cast when the first is still casting (IE, hit smite, hit your next spell before smite is done casting). It usually works. It seems like between doing this and using the /stopattack macro, it's...workable. Not ideal (IE no mini-GCD), but workable.
Wanted to come back and say still waiting for a fix so I can use a higher ilvl weapon. I shouldn't have to jump through hoops and macros just to use a mainhand as disc. I am fine using the wand as shadow and holy (though if I dps a lot as holy I will notice the bug as well but it is not as gamebreaking as for a disc priest)

While we're at the topic of smite, is there a reason smite auto targets an enemy on cast? None of our other spells do that. Is that related to the wand bug?
this is really annoying, my druid keeps getting maces and priest keeps getting wands, 375 wand and its just frustrating having this happen all the time. My druid is now my mythic+ healer - I was loving the disc priest so much.
Noise.

How are discipline priests supposed to heal via atonement with the extra delay from casting smite?

How are priests supposed to do emissary quests in the world when shadow sucks and healing specs have a bugged damage ability?

Bump.
This needs to be fixed ASAP.