I'd prefer a valve run (or even just valve blessed) global banlist
system. Admins can register a "strike" against a player. Users can
register increments of a strike against a user.

So say people are playing like they do, someone comes in and starts
obviously hacking. the players votekick the player. 0.0 strikes. the
player comes back and starts hacking again. the players 'voteban (with
strike)' him. 0.25 strikes. the admin clears the banlist to give
banned players another chance. the player comes back and starts
cheating again. admin elects to add a piece of a strike to fill him
out to 1 (admin_add_strike steamid strike value <reason>)

so the syntax would be:
"admin_add_strike STEAM_0:0:31337 0.75 "obvious hacking, mygot tag.""

Strikes are limited to a max of 1 for admin, 0.1 and .25 by majority user vote.

Players must be on a server or must have just been on server within 1
hour of vote issuance. So if the lamer leaves before he gets voted,
the server can still register him being struck. Admins can choose to
participate in the global banlist, and the global banlist can choose
who is allowed to participate (IE: if mygot gets a server and someone
notices it, all the strikes they've issued are nullified. If Bob wants
to run a hacking server, he can choose not to participate in the
global ban system, or even not run it on his server temporarily.

All servers should have an ID, all IDs should be tied to a name and
player steamID/account.

Obviously, admins can choose not to run a ban-enabled server, and for
this to work entirely there should be more than one layer of security:
(IE Valve decides to bless it with a link in the steam system to the
global banlist site to check the user's strike status and enforce it
by greying out certain mods/content. (perhaps even display a "time
left until unbanned" message.) Should the user be able to somehow
bypass the steam menu, the servers check each joining player's steamID
and let them play a minute or so until the allow/deny message comes
back. Considering a DB failure, perhaps a server outage, the user
should have a token attached to his client that contains a public key
secured warnlevel, client ID and other such information. Should the
user modify the file from what's on the server, (and there hasn't been
an outage) well, how's a strike each changed byte sound.)

Strikes:
First strike is an email message to the steam account's E-mail.
Second strike is a 1 hour ban.
At 3 strikes, it's a 24 hour ban from the selected mod.
At 5 strikes, it's a week's worth of ban. from all games.
at 7 strikes, a month.
if the user gets 10 strikes it's a 1 year ban.
If the user picks up an 11th strike, he's gone. permanently banned.

Yeah, I think the fear of the almighty ban will straighten up most
cheaters. I think moreso the fear of the wrath of their victims when
they gain the power to do something will straighten the rest.

If they don't want to be banned, I'm sure Valve would be happy to sell
them another copy of their game. hurt them in the wallet, where it
really counts.

On Sun, 2 Jan 2005 12:06:36 +0100, Dominik Tugend
<[EMAIL PROTECTED]> wrote:
> I think this is the right list!
> Since engine-knowledge etc. is a must 4 AntiCheat tools (it would be strange
> to only catch signatures of known cheats when you have an modable engine)!
>
> But I think VALVe won't do much, because it is pretty obvious that they
> can't support or don't have the will to support CS 1.6 anymore (currently).
> If VAC doesn't get updated for CS 1.6 then tools like CD are our only option
> (actually I think s.o. at United Admins is leaking or has leaked
> confidential information (this may happen in future again), also huge parts
> of UA members seem to have lost interest in CD for CS 1.6 (there are only a
> few active programers that do all the work).
>
> I think a demo analyzing tool would be interesting.
> It should be able to analyze 1st person demos and should also compare these
> with an HLTV demo that shows the same match (because dem files can be
> modified very easy).
> Also it should take BSP data (the levels) into account.
> But since this tool could never proof a cheat (it only could assist admins)
> and the efforts to do it would be realy high (since I don't know of s.th.
> compareable yet, there are only some dem + bsp specifiaction docs and
> scripts out there) I don't think there will be such a tool.
>
> Also let's be honest:
>
> Most likely CS 1.6 has entered the last timespan of it's lifecycle.
> The community will either move on to CS:S or other games or old players will
> quit gaming and new players will start with CS:S or other games.
>
> The chances of an revival are minimal.
>
> I think our only options  currently are an VAC update (won't happen or will
> only happen for a last time I think) or an CD fix.
> Also I think if we stop leagues because of many players cheating, we've
> already lost the battle (but also I have no good suggestion what could be
> done otherwise, I am realy very sorry for this).
>
> An good idea would be if UA could relase some parts of the CD source or at
> least start additional anticheat projects, so that when one anticheat has
> been
> taken down totally may be an other one still detects many of the new cheats
> (so the teams can exchange engineknowledge and so on).
>
> Of course this is only my point of view, it's not problem if you have other
> opinions :)
>
> In conclusion I am looking forward to an Cheating:Death Update with some of
> the critical parts rewritten (if possible).
>
> Greetings and so on blah :)
>
> ----- Original Message -----
> From: "Jarrett Hawrylak" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Sunday, January 02, 2005 6:18 AM
> Subject: Re: [hlcoders] useful anti-cheat tool alternatives?
>
> > Wrong list, this is HLCoders. And I haven't kept up with GOLDSRC, but
> > I think you're pretty much stuck with no anti-cheat if you're going to
> > ditch CD and VAC because they don't work. I don't think HLGuard does
> > anything, either, and thats the only other anti-cheat that comes to
> > mind. Maybe punkbuster?
> >
> >
> > On Sun, 2 Jan 2005 04:54:40 +0100, mercury <[EMAIL PROTECTED]> wrote:
> >> Hello dear readers of the hlds mailing list, dear VALVe Employees,
> >>
> >> I just wanted to ask if anybody out there knows any anti-cheat tool
> >> for Counter-Strike 1.6 which is usefully working at the moment.
> >>
> >> As we all know, VAC is outdated since several months and CD has been
> >> hacked lately. At the moment, there is no way of realizing a fair
> >> competition regarding CS games. Both mainstream anti-cheat tools, VAC and
> >> CD are not worth a penny right now.
> >>
> >> Some days ago, when things regarding this CD - Crack went public we
> >> (the ESL, the biggest european online gaming league) decided to stop
> >> all our Counter-Strike Ladders. And this is not something we like to
> >> do very often. Read more here if interested:
> >> http://www.esl-europe.net/eu/news/9661/
> >> http://www.steambans.com/news.php?id=1267
> >>
> >> Please dont get me wrong, i am not trying to sound important here. But
> >> i have to reach as many people as i can to try to find some
> >> information about other possible, not much-known alternatives to
> >> prevent cheating. The situation regarding cheats today is even worse
> >> than it was some months ago. And it wont get any better. If you know
> >> any tool which might be useful at the moment, please report it to me.
> >> You may even contact me directly if you can help in any way. We are
> >> definately interested in any way of cooperation for anything that you
> >> might provide that can help us all.
> >> Please dont let cheating prevail.
> >>
> >> --
> >> Best regards,
> >> mercury            mailto:[EMAIL PROTECTED]
> >>   ESL Master League Admin Counter-Strike Germany
> >>   counter-strike.de Editor & Server Administrator
> >>
> >> _______________________________________________
> >> To unsubscribe, edit your list preferences, or view the list archives,
> >> please visit:
> >> http://list.valvesoftware.com/mailman/listinfo/hlcoders
> >>
> >>
> >
> > _______________________________________________
> > To unsubscribe, edit your list preferences, or view the list archives,
> > please visit:
> > http://list.valvesoftware.com/mailman/listinfo/hlcoders
> >
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives, please 
> visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>
>

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders

Reply via email to