![[rtcw.co.uk logo homelink]](http://www.rtcw.jolt.co.uk/images/logo.jpg){kind=logo}
Complaint LimitsEnemy Territory has two seperate complaint limit settings, both based on the "F1 complaint" after a teamkill. Further, since 1.02 update you can disable complaints for teamkills that result from certain things. Also PB has a method to autokick likely lamers. g_complaintlimit 6 - Players will be kicked if they receive more than x F1 complaints, regardless of who filed them. Default is 6. g_ipcomplaintlimit 4 - Players will be kicked when complained against by x number of different IP's, i.e. when x number of different players file a complaint. Not associated with g_complaintlimit - player will be kicked if either rule is met. Default is 3. g_disableComplaint 1 - disables the complaint system for certain type of kills, 1 = mines, 2 = airstrike/artillery (a.k.a. 'FFE'), 4 = mortar. This cvar is a bitflag variable, so to disable complaints for more than one type of TK, add together for multiple types (7 would mean players cannot file if they are TK'ed as a result of running onto mines, into support fire or a mortar landing on their head). This setting was sdded with 1.02 patch, hence it requires server to be running 1.02 for this to function. With Punkbuster, there is also a related setting: pb_sv_scoreKick x - Players will be kicked by Punkbuster if their score goes this low. Obviously, set it to a negative figure. It doesnt exactly work well in ET since you only lose "score" (experience points) if someone files a complaint, and anyway are likely to easily rack up sufficient scores to remain in the positive regardless of teamkilling antics. The scorekick worked a lot better in rtcw though, and does prevent players rejoining for the duration of whatever you have pb_av_autokicklen set to. |
