[Video] GCD's completely broken on PTR

by Serennia | 01/11/2007 21:46:34

Serennia

http://files.filefront.com/PTRgcdwmv/;8942230;/fileinfo.html

I recommend downloading this and not streaming it to see it better. Basically it shows me dueling a rogue and how they changed the way global cooldowns function.

Basically, Blizzard intentionally changed server-side checks in conjunction with global cooldowns in the last PTR update. The game now checks server-side if all the requirements are met to perform an ability. So, for example, to use Overpower, the server checks:

-You are in melee range
-You are facing the opponent
-You have enough rage
-They dodged

After the server verifies all of this, then it sends the message back to your client to perform the action. If however, you fail a check, you have to wait for the server to acknowledge that. But the crippling part here is that the server automatically starts your global cooldown for the ability when you hit the key before it performs the checks. Meaning, it starts the GCD, then verifies if you can do it, and if you can't, interrupts the GCD for you.

In the fight, just from the rogue's movements, the server checks were interrupting my actions because he would break facing. The rogue did NOT use sprint which would have amplified this problem 10x worse.

There's pretty much no way this can possibly go live without breaking everything and pissing off half your playerbase.

TLDR version: If your ping is anything above 100, you're gonna get owned by the new GCD system and checks.

Edit: Here is the 2nd recording I made against a AR/prep rogue using dual imp sprints with a 85ms ping (half of the first one where I had 150). I recommend you download instead of stream, as always.

http://files.filefront.com/PTRgcd2wmv/;8943169;/fileinfo.html

I basically couldn't even land a hamstring in this fight unless he was mace stunned, and lost a few overpower oppurtunities or had them delayed because of the server interrupting GCD's. Although slightly better ping, I still get "locked" in numerous global cooldowns because of the change. It's especially easy to see at 00:52-54 seconds you can see the overpower GCD go through but the overpower doesnt go off because the rogue puts range between us.

[ Post edited by Serennia ]

by Hortus | 02/11/2007 17:12:10

Hortus

Please retest this on the next PTR build (which should be available soonish).

A number of spellcasting and /castsequence fixes are going into the next build and will hopefully resolve this issue.

Bump! Recently Bumped Threads

 

Blizzard Announcement Recent Blizzard Announcements

 

We suggest