Just wondering if this guy was able to hack, modify, exploit, tricked whatever words wer are using the server side data(mechanism) he can do other dirty tricks
to the blizz server I am pretty sure about it.![]()
Just wondering if this guy was able to hack, modify, exploit, tricked whatever words wer are using the server side data(mechanism) he can do other dirty tricks
to the blizz server I am pretty sure about it.![]()
Having an issue and sorry for bringing this up. I opened both the jar and zip file to get the necessary files to get the hack goin, but all it came up is some class files, meta folder and such. I dont see a patch update or anything to start the hack. Any help? Thanks!
Most of servers have fixed a patch that prevents No GCD...
Can the hack be updated in order to not be detected?
I am talking about private servers not the official's... Can't you understand? I posted twice about it and it seems you don't give a damn to read well.
Campfire and some others (there is list somewhere in model edit section) but those are model edits. DBC edits should be "safe" for now.
Dreadlox already released on ds "always owerpover" - got fixed on some private servers, and i have no idea if it works on retail... so yes you can do more with dbc edits...
You are not supposed to open *.jar file. Download it, unrar it, execute *.jar file or open *.zip file. Apply patch. Profit.
No there is no way how to bypass serverside check sorry...
Take it easy![]()
Thanks Zlobr for answering my questions.I have another one for you.
If the server will be updated soon,I don't know,let's say 3.4.0 and your hack will be compatible with this update,will the No-GCD hack work?
You will not be able to use this exact same hack when the next patch hits (4.0.1). Ghostcrawler hinted that they were working on a server-sided fix for the GCD length reduction. On top of that, Spell.dbc has greatly changed, and many spells have been removed/changed/added. Theres only about a third of the original fields for each spell now, none of which look like GCD values like it does now.
blizz fix no-gcd
![]()
Question: If I understand, this can actually improve the game experience, if I have high latency right? Just set the GCD a little bit lower (GCD - my latency = new GCD) and it won't be detectable. I could spam instants as if I had latency 0, because when the cast reaches server, it will look like it was sent after the correct GCD.
If they want to fix this, they would actually have to take the latency in account, otherwise, the GCD still needs to be both server and client-side, right? So there is hope this could be done even in the next patch.
Last edited by kixer; 10-07-2010 at 11:10 PM. Reason: Grammar
this still safe atm?