A client-side block then maybe? I was just on a server now with some script kiddie nick-change flooding. The server didn't crash, but the resulting lag was pretty awful :-(. The funny thing was that he was changing nick between "myg0t-ownz-u" and another, just as he was being shot in the head :-) classic moments
--------------------------------------- Chris Adams Fragzzhost T (07005) 964 855 F (07005) 964 857 www.fragzzhost.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric (Deacon) Sent: 21 October 2004 03:35 To: [EMAIL PROTECTED] Subject: Re: [hlds_linux] another crasher :( In a bold display of creativity, m0gely wrote: > There needs to be some decent flood control built in to the server for > stuff like this. Chat spamming and things like this where people are > spamming name changes etc just shouldn't be allowed. So if someone trys > to change their name 2 times in a round or something they just get a msg > "Only one name change per round allowed". Just like team switching too > much. How would that significantly change anything? You're still receiving, acknowledging, and then handling the request, issuing a response... -- Eric (the Deacon remix) _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
