There is absolutely no benefit in warning anyone.... enough of the "wrist slapping BS"!
VAC will always be updated whenever a new cheat is released so long the project doesn't fall apart
We trusted CSGuard/HLGuard and almost never questioned when a cheater was caught! It caught a cheater and banned them (unless the Admin was lenient). Admin were happy back then!
Regards
Alexander Kobbevik wrote:
Buffer them for a day then? You don't see the benefit from this?
Let's say those magots make a new cheat.. test it.. and it goes through VAC2; They now have a working cheat for thousands to download without the fear, right?
Unless VAC2 will be updated without notice?
I still stand by my idea, but maybe between updates is too long.
-Alex
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of BoNfiRe Sent: 30. mars 2005 12:46 To: hlds@list.valvesoftware.com Subject: Re: [hlds] Suggestion for VAC2.
----- Original Message ----- From: "Andrew Armstrong" <[EMAIL PROTECTED]> To: <hlds@list.valvesoftware.com> Sent: Wednesday, March 30, 2005 11:14 AM Subject: Re: [hlds] Suggestion for VAC2.
Personally I want cheaters banned as soon as they join the server, none of this 'checking' stuff.
I will second that no pint in giving these ppl a timaeframe to cheat, and IMO I can't see the difference between the threat of being banned as soon as you join to being banned a week later. The fear is there and giving them a week gives them a chance to anoy people while your waitng for the next update to get them banned.
----- Original Message ----- From: "Alexander Kobbevik" <[EMAIL PROTECTED]> To: <hlds@list.valvesoftware.com> Sent: Wednesday, March 30, 2005 8:02 PM Subject: [hlds] Suggestion for VAC2.
I been away from this list for a while and after seeing the last update notice I ran back.
Can I make a suggestion for VAC2, please?
I know its only fair to warn before inserting a new system that will try
to
catch cheaters. I also know that it's the right way to do it when you are acctually trying to get more players, and not less.
But, here goes.
What if you update VAC2... but only record cheats until the next update. Then you ban the collected list and start a new recording after the new
VAC2
update. This way you create a fear for cheating... which is one of the most successfull ways of stopping people from trying to cheat...
They can't just have someone else check if the cheat gets detected first, then use it until the next VAC2 update.
To me this sounds like a really good idea, but it popped up an hour ago while reading the archive.. so maybe I missed some side affect...
If people comment on this idea, maybe valve will consider it?
-Alexander [GNIZ]
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
