Remember that sourcemod, besides stuff like @red and @blue, also has
@aim, so you can spectate someone who changes name non-stop, and then
use "sm_ban @aim" to ban the person you are spectating


On Thu, Feb 2, 2012 at 18:03, Lance Waidzunas <lswa...@gmail.com> wrote:
> Sorry to chime in late, and if this has already been brought up, I
> apologize...
>
> But is there anyway Valve could implement a minimum time between name
> changes?  I could care less about the hackers and what not, but it's kind of
> a pain in the butt when you're trying to ban someone quickly in server and
> their name keeps changing.  My admins and myself are usually playing when
> these idiots drop by the eXtv servers and it'd be great if there was even
> like 5-10 second minimum between name changes so we have a moment to pop a
> ban in and carry on w/ the game.
>
>
> On Thu, Feb 2, 2012 at 10:57 AM, Mart-Jan Reeuwijk <mreeu...@yahoo.com>
> wrote:
>>
>> Well, here you go:
>>
>> http://www.youtube.com/watch?v=mD7Fi7xC-gg
>> They dont even care bout VAC anymore, for that takes couple weeks, couple
>> weeks they can cheat around, and then take a new one.
>>
>> And I think its more appropriate to fork the topic with its own thread
>> about DDOS attacks etc.
>>
>> ________________________________
>> From: Chad Hedstrom <chad.hedst...@gmail.com>
>> To: Half-Life dedicated Win32 server mailing list
>> <hlds@list.valvesoftware.com>
>> Sent: Thursday, 2 February 2012, 0:13
>>
>> Subject: Re: [hlds] Dealing with persistent cheaters
>>
>> Note to gameserver coders: it would be great to have some sort of
>> rudimentary DDoS protection, i.e. gameserver level firewall that says
>> "ignore packets from IPs X, Y, Z.
>>
>> I've been dealing with a very persistent DDoS attack on my BF3 servers
>> recently (he has it set on a nightly timer!) and we almost had to
>> switch to a virtual managed server to take advantage of Windows
>> Server's more advanced firewall options - at $180 a month. A huge
>> shout out to John at NFO for helping me with this. The DDoS attacks
>> wouldn't crash the server, but it would cause the server to drop all
>> the players.
>>
>> Long story short, DDoS tools are becoming more of a problem and easier
>> to find (LOIC anybody?) and it would be nice to have some rudimentary
>> protection built in, if only so that the plugin community can expand
>> upon it. Maybe something to think about for CS:GO and HL3DM? ;)
>>
>> On Sun, Jan 29, 2012 at 3:18 PM, Connor M. <wickedplayer...@gmail.com>
>> wrote:
>> > Just hope that they don't go deep into illegal territory and (D)DoS your
>> > servers. If they happen to do so, get a hold of your host/ISP (if you're
>> > running a server that you built/bought and are not using a host) and
>> > explain
>> > what happened as some programs that do such things can produce EXTREME
>> > amounts of bandwidth which can net you with a $15K bill (like someone on
>> > Facepunch experienced, didn't see the thread myself because there's too
>> > much
>> > traffic all the time). Then, look up the IP so that you can get a hold
>> > of
>> > local authorities and their ISP and tell them that they're doing illegal
>> > things. Hope for the best, and rest feeling good that you got rid of
>> > another
>> > skid.
>>
>> _______________________________________________
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>>
>>
>>
>> _______________________________________________
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>>
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
>

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

Reply via email to