VAC2 does not ONLY use data detection, but it is one of the protection mehtods it had/has used.
Organners VAC Dumper does work well in allowing normal users to know if/when VAC has updated, but only client sided. ALL of VAC updates begin on the server side. So, in reality, you are only seeing half the picture.
So of you guys here, my know of me, many may not. I am CampStaff, admin and contributor of where many of your hacks are made. I have been around this scene for a long time; just google my name and see.
Reason I am here, posting today is due to Mario's post. Seems he came onto my site, and stated that VAC had updated, when in fact, this is not the case. He then proceded to respond in threads stating such and such a cheat had been detected, when in fact, one cheat had just been released no more than 2 days prior.
I am here to set the record straight with facts and figures, and not speculation.. listen carefully.
Quote:
Originally Posted by Dark Assassin
19:19:49-> Loading VAC2: [C:\Users\DARKSW~1\AppData\Local\Temp\~DDFF.tmp] RetAddress: [6421070]
19:19:49-> VAC2 Module CRC32: -->[365f7882]<--
When ever this code is updated you can pretty much forget about using a hack, especially if it's a Public one. |
DarkAssassin has done half the work for me. In his above post, hes laid down what the current CRC32 of the VAC module currently is.
I have stated to Mario, in private message at my site that he was posting incorrect information. I am stately publicly that there is irrefutible evidence backing the statement, " The VAC2 client side module had
NOT updated ".
The CRC32 of the module is still the same as it was since August 17th 2008.