Cheating Death

abtm

<div class="IPBDescription">Why it doesn't work with VAC</div> Alot of server operators tend to use Cheating-Death as of yet for client side prevention of popular "OGC" or (Online Gaming Cheats) that "hook" into a client and enable them such features like, autoshoot, autoaim etc etc...

In a post regarding the 1.1 update, it was mentioned by Flayra that indeed VALVe anti-cheat (VAC) would be implimented into this release of Natural-Selection. This means that Server Operators will *NOT* be able to use their Cheating-Death server application to detect "hacks, hooks" and others via Cheating-Death.

The problem lies not within the server-side of Cheating-Death but the client side. As of yet, Cheating-Death uses a similar method of "client hooking" to stop cheaters in their tracks, much like cheaters use TO cheat. To this end, Cheating-Death is/will be recognized or mistakenly so by VAC as a "hook" which would ban the user from prospective gaming on VAC enabled servers for the time of the ban. So what are server operators to do? Well, a representative from UnitedAdmins suggests "This is why most people just use either VAC or Cheating-Death".

Currently, there are no plans on either side to support the other, so until VAC allows Cheating-Death some exception or visa-versa modificiations, there seems to be no other course than to simply live with one or the other.

hullu

C-D automaticly closes half-life when trying to connect to VAC enabled server to prevent false VAC bans.

verbose

<!--QuoteBegin--abtm+Apr 21 2003, 12:58 PM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (abtm @ Apr 21 2003, 12:58 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> In a post regarding the 1.1 update, it was mentioned by Flayra that indeed VALVe anti-cheat (VAC) would be implimented into this release of Natural-Selection.  This means that Server Operators will *NOT* be able to use their Cheating-Death server application to detect "hacks, hooks" and others via Cheating-Death. <!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->
To prevent some confusion, allow me to amend this statement. VAC support will be in NS 1.1. You will still be able to use Cheating-Death on your server, as long as you disable VAC by setting <b>secure "0"</b> in your liblist.gam.

abtm

Hullu: An op from #UnitedAdmins/#CheatingDeath told me that there was work-around and that it was not possible

Secondly, as I said, to use CD/VAC you need to set secure to 0 obviously I should have said EXACTLY that, but I did say to disable it <!--emo&:D--><img src='http://www.unknownworlds.com/forums/html/emoticons/biggrin.gif' border='0' style='vertical-align:middle' alt='biggrin.gif'><!--endemo-->

Duck

<!--QuoteBegin--abtm+Apr 21 2003, 12:58 PM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (abtm @ Apr 21 2003, 12:58 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> This means that Server Operators will *NOT* be able to use their Cheating-Death server application to detect "hacks, hooks" and others via Cheating-Death. <!--QuoteEnd--> </td></tr></table><span class='postcolor'> <!--QuoteEEnd-->
This is what made everyone think that you meant cheating-death would not be an option. We shall see if VAC is a better alternative.