GCD issues affecting thousands of players

There’s several mega threads on Reddit & other forums about this issue, and some people have suggested creating a topic here in hopes a real Blizzard employee might come across it in addition to the tickets already created through the support system.

To summarize, a huge amount of players have experienced delayed global cooldown responses in combat for at least half a year. This negatively impacts high haste classes/specs (like fire mage or outlaw rogue) moreso than other specs. When a spell keybind is triggered during high-haste moments like bloodlust, players are suffering from performance drops due to the GCD not registering or resetting correctly.

There’s a post about this topic in the WoW subreddit. Plenty of people there are all experiencing this issue, and for many of us the game has become unplayable. This isn’t a result of server lag or home latency issues, it’s primarily happening to people with high haste levels not being able to register spells even if the GCD has finished queueing.

It’s been at least half a year of this, with some people mentioning first experiencing it in Dragonflight. A few are theorizing that Blizzard’s outdated servers can’t handle the “tick” speed of modern WoW’s fast-paced combat, but I can’t really comment on how realistic that is.

All we know is that it’s a very real issue and it’s affecting a huge amount of people very negatively. Hopefully this can be looked at, because it’s a pretty glaring issue and it’s happened to me at least a few times during every single M+ dungeon I’ve entered.

19 Likes

Thank you Khenja for posting this. I’m affected by this problem as well.

I’m sure there are more out there lost in the nether, but there’s plenty of evidence to go around, so here are some of the receipts:

https://www.reddit.com/r/wow/comments/1jw4dv2/gcd_delay_still_present_blizz_is_silent_has/

https://www.reddit.com/r/wow/comments/1gto77z/something_is_seriously_wrong_with_the_serverinputs/

https://www.reddit.com/r/wow/comments/1gcqylr/weird_combat_delay_as_of_1105/

https://www.reddit.com/r/wow/comments/1jasixu/what_is_this_gcd_press_delaylag_desperate_for_help/

2 Likes

It’s hugely appreciated that you posted the topics on this. So many people are being adversely affected by this issue and the lack of a response makes me think it’s either a deep-rooted issue that’s too costly to fix, or it’s a problem that Blizzard still doesn’t know the cause of.

Either way, unless I’m mistaken, the lack of a response from Blizzard is disheartening to say the least. This is a server-side issue that’s been lowering player enjoyment (and probably engagement) on an hourly basis for at least half of the past year.

I really, really hope this is fixed.

1 Like

Unfortunately this issue has been around pre DF.

They changed how spells are batched back in WoD.

:+1:

:surfing_man: :surfing_woman:

1 Like

Just posting to say I also experience this issue and have for a long time (it’s not something recent at all). I try and avoid classes that prefer haste for this very reason.

Since not everyone experiences it, I’ve often wondered if there’s some hidden account variables on the server side which are the cause. My account was created back in WotLK, and my wife and I had two separate wow accounts under the same bnet account … so maybe there’s something related to multiple accounts and Blizzard having to look something up repeatedly on the server - I dunno. But yeah, have my upvote.

1 Like

Yes! Please fix this Blizzard! It happens constantly on my totemic enhancement shaman with Lava Lash during hot hands procs especially but almost always during high haste moments/quick GCDs.

I have noticed this over the last 4 months that I have been back. Additionally, I would like to add that I felt it most on unholy DK, Enhance shaman, and to some extent on Marksman hunter and dev evoker. I am not serious player at all so this doesn’t make an issue for me a side from the sluggish unresponsiveness causing frustration and confusion.

All things considered and the relevant information of titles and services been sold off by the company, we should and can expect the terrible degradation in quality from now on. More over the US is making increasingly likely that bad American companies will be able to blow off customer complaints and refunds. We should expect this to be the norm and not the exception.

Yeah seems like things like this are starting to stay round alot longer then they were before, also lots of bugs being introduced when they do new patches.

2 Likes

BFA was the first time I noticed the lag spikes for high haste classes and specs especially with Lust. As other have said BFA with all those new spells really put a crunch on the servers.

I believe we are starting to see the same thing now in TWW with hero talents.

No easy fix as this has been around for a while now.

:+1:

:surfing_woman: :surfing_man:

Until blizzard actually admits there’s a problem here–

  1. After any load screen, do a /reload
  2. After dying and resurrecting, relog and /reload. Pvp deaths are especially prone to causing this GCD problem.
  3. Do not touch a crafting table for any reason. If you do, just relog then /reload. They create an invisible persistent mouseover overlay on your screen.
  4. Plumber addon can fix the auto-loot bug

It’s not fun having to press an ability 4-5 times to get it to go off. This issue should be absolute #1 priority for a fix.

5 Likes

Hopefully they’re looking into it!

2 Likes

Yep, it sucks badddddd

2 Likes

So you have to logout of your character, log back in and then immediately do a /reload in order to fix 2 and 3’s issues?

While nice to have a potential workaround, #2 is not feasible when running dungeons if logging out is part of the solution. I’ll definitely be more mindful of doing reloads after loading screens however to see if that helps.

And dang-it-all, I touch crafting tables all the time. Maybe that’s compounding my issue? I’m gonna be more careful with that one from now on.

2 Likes

Please Blizzard look into this. This is single handedly ruining the game for me. Combat is not fluid at all with this and extremely frustrating. :frowning:

1 Like

I can confirm this is happening for me. I play with 2~4ms on the EU servers where I have this issue so it’s 100% not my internet. It’s causing me to miss stuns for no good reason and it’s extremely frustrating.

2 Likes

I submitted my own bug report on this issue ( Severe Delay in Ability Feedback - #6 by Weran-tichondrius )

I have done additional troubleshooting since then and would like to add it to this thread for anyone at Blizzard working on this bug. It seems that despite a visual delay that can last upwards of 600+ ms, my combat log still reflects procs and spell casts instantly:

4/22/2025 06:01:18.209-5  SPELL_CAST_SUCCESS,Player-11-0E528872,"Awayukia-Tichondrius-US",0x511,0x0,Creature-0-3131-2552-31371-225984-000086A81A,"Training Dummy",0x10a28,0x0,8676,"Ambush",0x1,0000000000000000,0000000000000000,0,0,0,0,0,0,0,0,-1,0,0,0,0.00,0.00,2339,0.0000,0
4/22/2025 06:01:18.210-5  SPELL_DAMAGE,Player-11-0E528872,"Awayukia-Tichondrius-US",0x511,0x0,Creature-0-3131-2552-31371-225984-000086A81A,"Training Dummy",0x10a28,0x0,8676,"Ambush",0x1,0000000000000000,0000000000000000,0,0,0,0,0,0,0,0,-1,0,0,0,0.00,0.00,2339,0.0000,0,311922,212191,-1,1,0,0,0,1,nil,nil,ST
4/22/2025 06:01:18.210-5  SPELL_DAMAGE,Player-11-0E528872,"Awayukia-Tichondrius-US",0x511,0x0,Creature-0-3131-2552-31371-225984-000086A81A,"Training Dummy",0x10a28,0x0,315585,"Instant Poison",0x8,0000000000000000,0000000000000000,0,0,0,0,0,0,0,0,-1,0,0,0,0.00,0.00,2339,0.0000,0,13947,6973,-1,8,0,0,0,1,nil,nil,ST
4/22/2025 06:01:18.210-5  SPELL_AURA_APPLIED,Player-11-0E528872,"Awayukia-Tichondrius-US",0x511,0x0,Player-11-0E528872,"Awayukia-Tichondrius-US",0x511,0x0,195627,"Opportunity",0x1,BUFF

I don’t know enough about the inner workings of the game to comment definitively on the significance of this. However, I believe it proves the engine is handling casts correctly and without delay, and the issue is purely on the render/client feedback loop.

2 Likes

Yet, no word from blizz. Go figure

1 Like