GHT - GCD Hack Tracker 

maybe its just me but i dont really see the importance of having a addon like this unless your trying to teach someone to play and keep there cooldowns as close as possible. but then according to what i read you would be using it for the wrong application. plus im not sure how it would do this but does it check other peoples MS to the sever along with your own ms and then does it calculate it from there?

there is a hack that involves altering an mpq file that allows for an undetectable change in your GCD. It lowers it to 1 second. This is an attempt to catch the hackers and give EVIDENCE to report and get them banned. This is the first real available hack that tournament level players have used and gotten away with. And since this is the first attempt to fix and end this, I commend the author for putting a foot down.

I've watched a video on GCD hack, it showed a mage cast 6 Ice Lance after one Frost Nova. That is six 5K+ damage Ice Lance from one Frost Nova. Link to video: Dump Gcd I can see the importance of catching someone using such a hack.

Not even necessary, there's a program for Windows 7 that does the same. Luckily it seems to be detected by the new beta launcher Warden. It's gotten quite rampant in Arenas, lately.

I assume this is why the hack is "undetectable", at least via combat log.

When you hit a move, it sends the command to blizzard. Server side, the minimum time for the GCD is set to 1 second. When you spam a key, waiting for it to come off cooldown, it is still sending the command to blizzard, and blizzard is responding back "You have not recovered yet." However, if you hit that key during the last 500 ms (the extra .5 of the gcd), blizzard, only having the cap set to 1 second server side, allows the move, and thus, you will have the same effect as the GCD hack.

With the true GCD hack, you will catch them with this program every move. If they are not using a GCD hack, and mash the button, it will report a bunch, but definately not all their moves, as GCD hack. Unfortunately, the program does not currently remember/use the GCD used on all the other moves, in its total. So after time, you will generate nothing but evidence of false positives.

In order to truely establish if they have a GCD hack, perhaps it should remember a count of say, the last 10 GCD's they used, and get the average. If they are just button mashing, the average will not trigger it. If they are GCD hacking, it will catch them without a problem.

>> EDIT (addition):

Without numbers, this is just talk, so I set the cutoff value to 5, and did my rotation, so I could show you whats happening. If we ignore any GCD of over 2.0 from the average, it would be: 31.088 / 21 = 1.48, however, if all you record is false positives, and look at it later...

1.592 (Serpent Sting -> Chimera Shot)
1.149 (Chimera Shot -> Aimed Shot) *FALSE POSITIVE*
1.461 (Aimed Shot -> Arcane Shot)
2.429 (Arcane Shot -> Chimera Shot)
1.54 (Chimera Shot -> Aimed Shot)
1.479 (Aimed Shot -> Arcane Shot)
1.156 (Arcane Shot -> Chimera Shot) *FALSE POSITIVE*
1.442 (Chimera Shot -> Aimed Shot)
4.63 (Aimed Shot -> Arcane Shot)
4.576 (Arcane Shot -> Chimera Shot)
1.703 (Chimera Shot -> Aimed Shot)
1.568 (Aimed Shot -> Arcane Shot)
1.67 (Chimera Shot -> Aimed Shot)
1.453 (Aimed Shot -> Arcane Shot)
1.641 (Arcane Shot -> Chimera Shot)
1.344 (Chimera Shot -> Aimed Shot) *almost *
4.705 (Aimed Shot -> Arcane Shot)
4.613 (Arcane Shot -> Chimera Shot)
1.606 (Chimera Shot -> Aimed Shot)
1.584 (Aimed Shot -> Arcane Shot)
1.297 (Arcane Shot -> Chimera Shot) *FALSE POSITIVE*
1.665 (Chimera Shot -> Aimed Shot)
4.552 (Aimed Shot -> Arcane Shot)
4.644 (Arcane Shot -> Chimera Shot)
1.578 (Chimera Shot -> Aimed Shot)
1.635 (Aimed Shot -> Arcane Shot)
1.295 (Arcane Shot -> Chimera Shot) *FALSE POSITIVE*
1.23 (Chimera Shot -> Aimed Shot) *FALSE POSITIVE*

>> 2nd EDIT (addition):

I set the value to 2 this time, so the log would be cleaner, and have another set of data to use as an example, this time without arcane shot in rotation (normal rotation): 13.023 / 10 = 1.3

1.467 (Serpent Sting -> Chimera Shot)
1.255 (Chimera Shot -> Aimed Shot) *FALSE POSITIVE*
1.204 (Chimera Shot -> Aimed Shot) *FALSE POSITIVE*
1.413 (Chimera Shot -> Aimed Shot)
1.404 (Chimera Shot -> Aimed Shot)
1.216 (Chimera Shot -> Aimed Shot) *FALSE POSITIVE*
1.236 (Chimera Shot -> Aimed Shot) *FALSE POSITIVE*
1.209 (Chimera Shot -> Aimed Shot) *FALSE POSITIVE*
1.285 (Chimera Shot -> Aimed Shot) *FALSE POSITIVE*
1.334 (Chimera Shot -> Aimed Shot)

>> RESULTS ANALYSIS

So if you look at only the false positives, I would be "GCD hacking". If you look at the average, I am above your threshold of 1.3 (right on the line really), and if you look at the full time rotation (the 5s minimum average), everything averages to 1.48.

>> GCD ANALYSIS OF SOMEONE GCD HACKING

I am not niave, I know people who do use GCD hacking, so I had them do it, and gathered their data, this is without arcane shot: 11.176 / 10 = 1.11

1.255 (Serpent Sting -> Chimera Shot)
1.241 (Chimera Shot -> Aimed Shot)
1.82 (Aimed Shot -> Chimera Shot)
1.171 (Chimera Shot -> Aimed Shot)
1.112 (Chimera Shot -> Aimed Shot)
1.129 (Chimera Shot -> Aimed Shot)
1.159 (Chimera Shot -> Aimed Shot)
1.127 (Chimera Shot -> Aimed Shot)
1.139 (Chimera Shot -> Aimed Shot)
1.152 (Chimera Shot -> Aimed Shot)

With arcane shot: 12.929 / 10 = 1.29

1.071 (Serpent Sting -> Chimera Shot)
1.646 (Chimera Shot -> Aimed Shot)
1.143 (Aimed Shot -> Arcane Shot)
1.786 (Arcane Shot -> Chimera Shot)
1.233 (Chimera Shot -> Aimed Shot)
1.167 (Aimed Shot -> Arcane Shot)
1.31 (Arcane Shot -> Chimera Shot)
1.368 (Chimera Shot -> Aimed Shot)
1.086 (Chimera Shot -> Aimed Shot)
1.119 (Aimed Shot -> Arcane Shot)

>> OVERALL ANALYSIS

When they were not using arcane shot, wow, very impressive, an effective GCD of 1.11 ! With arcane shot, 1.29, both under the 1.3 threshold average.

>> FINAL SUGGESTIONS

1) Record the last 10+ gcd timings, and get the average.
2) Set threshold to 2 for recording, anything over this is because of actual cast times, or they stopped.
3) Compare the average with 1.3 for determining if gcd hacking.

I hope this helps, I look forward to stopping these people. GCD hacking, clearly, gives an advantage to them, but not really as much as I thought. However, if you do not spam keybind, you are clearly at a severe disadvantage, and GCD hacking, in effect, allows you to be slower/not work as hard, and should be stopped. I think if you implement the average check, rather than just the straight false positives, you will catch true GCD hacking without a problem, and not falsely accuse anyone who knows how to mash buttons faster.

Interesting, adding wing clip and running data.

added:

[2974] = true, -- Wing Clip

>> ME, 15.248 / 10 = 1.52

1.63
1.509
1.475
1.654
1.641
1.702
1.244 *FALSE POSITIVE*
1.62
1.437
1.336 *close*

>> GCD HACKER, 12.03 / 10 = 1.20

1.147
1.114
1.11
1.268
1.163
1.28
1.147
1.094
1.296
1.411

>> ANALYSIS

The same over time analysis should work fine. I think to really be able to abuse this, you need a spammable move, without cooldown. All I can think is prot warrior, devastate spamming. Perhaps this is why so many prot warriors in bgs lately? Otherwise, I think the real advantage is being able to chain the bursts faster, which is definately brutal. A full 3 seconds advantage @ ~5k each is definately a game changer.

>> RANDOM AFTERTHOUGHT

Maybe blizzard allows ranged attacks to go trigger early because of travel time?

I downloaded your latest version and attacked the dummy for 5 min straight. No report at all. I had the GCD hacked guy do the same, detected him without a problem. Awesome job.

Yes indeed, works great, now get those other classes in there! (and put this on curse gaming please!)

Releasing this to the public will have mixed results. The good: It will be easier to find people that are indeed GCD hacking. The bad: The smart people that have been GCD hacking will have already stopped because they are now aware of this addon, so they won't get banned from player reports. Should've kept this relatively private if you wanted to nail the hackers.

Curse can take a while. If you use a version control upload instead of packaged addons you shouldn't have a wait time at all, though. At least that's what happens with my Warhammer addons.

i have been falsely accused of using this cheat to the extent that a thread has been made on my realm forums. i play an arms warrior in pvp and fury pve. i download my guilds WOL almost daily, freely avalible for all to view, yet all it took is this addon picking me up for god knows what reason to start the fingers pointing. im unsure if the accusations are just down right lies by someone my team beat in arena from the same server, or an addon detection error.

please see thread:

http://forums.wow-europe.com/thread.html?topicId=14574620010&sid=1

just to make myself totally clear, i am not using this hack yet apprently was still detected......