> it doesn't really matter, it's far easier prevent people from connecting by > tying up all the free slots (google q3fill). > > > I already have that patched in my ioquake3-server branch. I actually have 2 things: 1. If a certain server cvar is set, limit the number of "connect" packets from a single IP address to a rate of 4 every six seconds. 2. A new server cvar defines the maximum number of players that can connect form a single IP address. I usually have this set to 2 or 3.
These patches at least partially fix the problem you mention.
_______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
