Description

provides an in-game command which allowes the players to request the server rules. You define the text to be displayed in the plugin settings. The in-game command is also registered with the BasicInGameInfo plugin and can be requested by using the help command of that plugin.

The option for a welcome message is 1:1 conversion.

It is left in for compatibility reasons and will be droped in a later version. You may test if it fits your needs but I advice you to use for example the onSpawn message of my

plugin.

The method here is a bit unsecure because if a player does not spawn during the time period you set with the delay he does not see the message.

Note

This plugin checks for admin status.

A user is an admin if his playername can be matched against a procon account name and this account has any privilege. The smallest possible privilege is to be able to login to the layer.

If a player is detected as admin (see above) using the rules command with the global command scope the output is send to all users.

Installation Instructions

Please refer to the download section down below.

Configuration

The settings should be self explaining.

Data done in the abandoned plugin should be noticed and used by this plugin automatically.

Technical Support

If you experience any issues with this plugin, please report here.

Description

This plugin allows players to start a vote to ban or kick another player on the server. This is particularly useful to work against all the hackers we have seen so much of lately.

(

)

In-Game Commands

• !voteban <player_name> - Puts in a request to initiate a Vote Ban on the specified player.
  
• !votekick <player_name> - Puts in a request to initiate a Vote Kick on the specified player.
  
• !yes
  
  • Votes YES to ban/kick the player who has a Vote Ban/Kick in progress on them.
    
  • Also, agrees to the suggested name after misspelling a name when trying to Vote Ban or Vote Kick.
• !no
  
  • Votes NO to ban the player who has a Vote Ban in progress on them.
    
  • Also, disagrees to the suggested name after misspelling a name when trying to Vote Ban or Vote Kick.
• !cancelvote - Cancels the current vote in progress. This command is only available to players who have an account created and are able to connect to the Procon Layer.

These commands may be redefined by you in the plugin settings.

Settings

• Enable Vote Ban? - Allows you to enable or disable the ability for players to Vote Ban.
  
• Start Vote Ban Number - The number of !voteban requests needed to initiate a Vote Ban on the specified player.
  
• Vote Ban Pass Percentage - The percentage of YES votes of the total players needed for a Vote Ban to pass.
  
• Vote Ban Duration (in minutes) - How long Vote Bans last before they are ended.
  
• Vote Ban Progress Display Interval (in seconds) - The recurring number of seconds that the progress of the current Vote Ban is displayed in chat.
  
• Ban Type - The type of ban (GUID, Name, IP, or PB GUID) that is issued upon a successful Vote Ban.
  
• Ban Duration - How long bans last upon a successful Vote Ban.
  
• Ban Length (in minutes) - If Ban Duration is set to Temporary, bans last for this length of time before they expire.
  
• Ban Reason Message - Set this to whatever you would like the ban reason to be upon a successful Vote Ban. (Use %player% for the banned player and %reason% for the reason the players Vote Banned the player.)

• Enable Vote Kick? - Allows you to enable or disable the ability for players to Vote Kick.
  
• Start Vote Kick Number - The number of !votekick requests needed to initiate a Vote Kick on the specified player.
  
• Vote Kick Pass Percentage - The percentage of YES votes of the total players needed for a Vote Kick to pass.
  
• Vote Kick Duration (in minutes) - How long Vote Kicks last before they are ended.
  
• Vote Kick Progress Display Interval (in seconds) - The recurring number of seconds that the progress of the current Vote Kick is displayed in chat.

• Enable Hack Cry Responder? - Allows you to enable or disable the Hack Cry Responder.
  
• Hack Cry Trigger Number - The number of times that the word "hack" needs to be said in chat, recurrently, to trigger the responder.
  
• Hack Cry Trigger Response - The server message response sent when the responder is triggered. (Use %vbcommand% and %vkcommand% for your currently set Vote Ban and Vote Kick commands.)
  
• Additional Triggers - Any additional words in chat that you would like to trigger the responder.

This whitelist guards admins as well as additional players of your choice from being Vote Banned/Kicked. It recognizes players as admins if they have an account created and are able to connect to the Procon Layer.

• In-Game Names - Allows you to add additional players to the whitelist.
  
• Action Taken - The action taken (None, Kill, Kick, Temporarily Ban, Permanently Ban) against a player that tries to Vote Ban/Kick a player in the whitelist.
  
• Temporary Ban Length (in minutes) - If Action Taken is set to Temporarily Ban, bans last for this length of time before they expire.

These allow you to customize the in-game commands for this plugin.

• Vote Ban Command - The command used to initiate a Vote Ban.
  
• Vote Kick Command - The command used to initiate a Vote Kick.
  
• Yes Command - The command used to vote yes to the vote in progress. (Also used to confirm a suggested player name.)
  
• No Command - The command used to vote no to the vote in progress. (Also used to deny a suggested player name.)
  
• Cancel Vote Command - The command used to cancel the vote in progress.

Future Plans

• Add Vote Kick.
  
• Find out how to implement the player name suggestion when a player misspells the name of the one he requests a Vote Ban on.
  
• Add a whitelist so that admins cannot be voted against. Also allow the option to slay, kick, or ban whoever attempts an admin Vote Ban.
  
• Add the option of the Ban Type.

Known Issues

System.Timers seems to be faulty in Procon plugins and some Timers (such as the one that controls the Vote Progress Display every x seconds) are occasionally unable to be disabled during run time. This causes an infinite loop of any of the timed events in this plugin even when the vote should have ended. The only solution is to restart your Procon running the plugin.

Conflict - If you are an admin and are using !yes or !no for the

plugin, this plugin will also respond to it with "There is no vote in progress" if there is no vote going on or will vote if there is a vote going on. This conflict should hardly be of any consequence but for a solution you can just redefine the voting commands in the plugin settings.

When a Vote Kick has already been initiated on a player and someone puts a request in to initiate another Vote Kick later in that round, the number of requests goes below 0 since it isn't reset until a new round.

This plugin will constantly reserve a determined number of slots on your server much like the previous Battlefield 2 reserved slot system. It does this by checking if the server has less than X number of slots free, if it does it will kick the last connected player that occupied the reserved slot. The plugin may not eliminate the queueing system if your server is popular, but it will automatically clear through it, ensuring when a VIP does connect they do not have to wait through a long queue.

Settings

- Whether the plugin will actively kick to keep reserved slots available. (Plugin will always keep track of who is last joiner when it is activated regardless of this setting)

- Refresh the Reserved Slot list

- The exact soldier names of the players you wish to reserve a slot for. The list will update names with the Reserved Slot list saved on the server but you can add others here if needed (to get the plugin to update the list from the servers list go to the Reserved Slots tab in Procon and refresh it).

- The maximum size your server can be (For compatibility with Adaptive Server Size)

- How many slots you wish to reserve. (Recommended: 2)

- The server population you wish to reward for helping start your server. This allows you to give the first X number of people on your server a temporary reserved slot as they have helped you populate. This reserved list will be cleared when the server empties.
Kick Reason - The reason given when a player is kicked from the server.
Debug - Whether to print debug statements. Will spam A LOT (Recommended: No)

Ingame Commands

- Enables the plugin to start actively kicking to ensure reserved slots are available. (Requirements: Account)

- Disables the plugin so it will cease to kick for reserved slot. (Requirements: Account)

Author:

synchronizes your Bad Company 2 / Battlefield 3 server with a Teamspeak 3 server, moving players into their respective channels on Teamspeak dependent on the player's team in Bad Company 2 / Battlefield 3. The plugin also allows you to "yell" at players who are not in your Teamspeak server, yet playing on your Bad Company 2 / Battlefield 3 server.

All parameters for the plugin are described in the plugins details tab.

To see the plugin running, you can join this TS/BC2/BF3 server:

Teamspeak 3 : 184.173.95.3:9988

Bad Company 2 : (Enter this into your search box in BC2) TeamPlayerGaming.com

Battlefield 3 : (Enter this into your search box in BF3) TeamPlayerGaming.com

• Under rare conditions, a player may get tossed around a bit before ending up in the right channel when a round ends.

Here are the plans I have for this plugin, currently:

• Add a specifiable parent channel other than the staging channel.
  
• Bug fixes?

• Copy the plugin (TeamspeakSync.cs) into your plugins directory (Plugins/BFBC2 or Plugins/BF3) ORinstall the plugin from the packages tab within PRoCon.
  
• If you are running your plugin's in a sandbox, make sure your config file (Configs\procon.cfg), has the following line:
  
  • procon.private.options.trustedHostDomainsPorts ip_of_teamspeak query_port_of_teamspeak
• Make sure the box PRoCon is being hosted on allows outgoing and incoming connections. This plugin must connect to your Teamspeak 3 server using TCP/IP. It binds to a random local port that is open at the time the plugin is enabled.

• Add your PRoCon's IP to query_ip_whitelist.txt. If your Teamspeak 3 server is being hosted by someone else, ask your provider to do this for you.
  
• Setup your ServerQuery Login through Teamspeak by going to Tools -> ServerQuery Login -> *Enter A Username* -> *Receive Auto Generated Password*.
  
• To find what port your Teamspeak 3 server uses as its query port, look in the server.ini file. The default value is 10011. If your Teamspeak 3 server is being hosted by someone else, ask your provider for the query port.

Description

Reports and enforces bans on players. Go to

to sign up for a API key.

You can find more information for your rcon tools on the

- Thanks to Zaeed

In procon simply go to the Packages tab, and search for Metabans. Install that by clicking the install button. You'll then have to restart procon. If you log in to a layer, you'll have to restart the Layer server also.

You then need to register at

.

Once this is done, go to the settings page, and on the API tab, you'll see long string. Copy that into the 'API Key' field for the Metabans plugin, along with your Metabans username.

Description

Calls an in-game vote for the next map near the end on the round. Randomly selects four maps (by default, can be adjusted) from the current maplist to vote on. Before the options are displayed, a banner can be shown to get the players attention that voting is about to commence.

The votes are tallied and if there are more votes than the set threshold, the winner is the map with the most votes. If there is a tie, the winner is selected at random from the tied maps. The next map is announced and it can be periodically displayed until the end of the round.

In-game Screenshots

Four displayed voting options without gamemode showing. Also shows vote confirmation message.


Optional voting banner used to get the attention of players before/during a vote.

Installation

Unzip the 'xVotemap.cs' into your '..\Plugins\BF3\' folder.

In-game Commands

/# While a vote is in progress, votes for the option represented by the #.

/v Displays the vote options while a vote is in progress. If typed before a vote, it will display the predicted amount of time before the vote begins.

/nextmap Displays the next map.

/votemap Initiates/restarts a votemap if the player has map changing priviledges in Procon.

Settings

Display

Enable Vote Banner?: Is the banner (designed to get the attention of players) displayed before the voting commences.

Voting Options Interval: Integer, in seconds, representing how often the map vote options are displayed once the voting poll opens.

Next Map Display Interval: Integer, in seconds, representing how often the winning next map is displayed after the voting is over but the round hasn't ended yet. A value of -1 will disable nextmap messages.

Show Gamemode in Voting Options? Determines if the shorthand notation for the gamemode is displayed in the voting options. This is most useful for those running mixed mode servers, especially if the same map is in the maplist with different gamemodes.

Map Options

Number of Vote Options Integer, between 2 and 8, representing the number of vote options to be displayed when a mapvote is called.

Exclude Current Map From Vote Options?: If yes, the current map with be excluded from the next map voting options, so to not allow the same map to be played twice.

Randomness: An integer from 0 to 10 representing the randomness of the map options for a vote. The algorithm changes the probability of each map and gamemode pair being selected as a vote option depending on how long ago it was last played.


Randomness = 0: Will rotate through the maplist, only showing the maps that haven't been played in a long time. Players should end up playing every map in the cycle.


Randomness = 5: Maps that haven't been played in a long time will have the highest probablity and recently played maps will have the lowest probability of being selected as vote options.


Randomness = 10: Every map has the same chance of being selected as an option. Players will tend to play the most popular maps repeatedly.

Voting

Trigger: If Automatic, the voting will be triggered automatically near the end of the round. If Manual, the voting will have to be triggered manually with the /votemap command.

Voting Threshold: Integer, representing the minimum total number of votes that must cast for the highest voted map to become the nextmap. If no map reaches this threshold, then the map will just roll over to the next map in the maplist.

Voting Duration: Integer, in seconds, representing the target length of time the voting poll is open for.

Time between Voting End and Round End: Integer, in seconds, representing how long from the end of the round the voting will finish. In other words, at what time you want the voting to take place, mear seconds before the end of round or in the middle of round sometime.

Rush Voting Start Time from Start of Round: Integer, representing the time when voting will start, in seconds from the start of the round. In rush, there is no way to predict when the round will finish with the current RCON information, as the status of MCOMs are unknown. So you must estimate how long the shortest rush round would take and start the vote a couple of minutes earlier in order to ensure a vote will take place.

Xtras

Debug Level: Integer between 0 and 5, where 0 outputs no plugin debug messages, and 5 which outputs even the most mundane steps.

Development

• If the maplist is changed during a vote the winning map will not correctly be the next map.

• Complete gametype display rollout.
  
• Test out varying vote weightings.
  
• Investigate possible long map names.
  
• Detect maplist change.

Description

This is a re-write of the famous Insane Punisher from Battlefield Bad Company 2. In this version I have removed all the features not supported by Battlefield 3, and added a couple of new features. See the full change-log at the end of this post.

Think this plugin is awesome? You can buy me a beer.

Installation Instructions

• Download the zip file containing the plugin source (in the attachments)
  
• Extract the source file InsanePunisher.cs
  
• Copy the source file to ProCon's Plugins/BF3 directory

Minimum Requirements

• serverInfo
  
• admin.listPlayers all
  
• punkBuster.pb_sv_command pb_sv_plist
  
• banList.add
  
• banList.save
  
• admin.kickPlayer
  
• admin.killPlayer

Features Summary

• Retribution
  
  Victims of team-killers are allowed to !punish, !forgive, !votekick, and !voteban
  
• Queued Punishments
  
  If the team-killer is dead at the time of !punish, the punishment is queued, and enforced the next time he spawns.
  
• Individual Punishments
  
  If victim was team-killed by multiple players, the plugin remembers all the team-killers. This allows the victim to punish the team-killer, using the !punish {player} command, even if {player} was not the last one to team-kill.
  
• White-list
  
  Players that are in the white-list have immunity against all punishments.
  
• Automatic Punishments
  
  If desired, you can set the plugin so that it automatically punishes the team-killer immediately after each violation
  
• Automatic Actions
  
  If desired, you can set the plugin to automatically kick or ban team-killers after they receive a certain number of punishments
  
• Customizable Warnings
  
  Allows you to change the default team-kill warnings that are sent to the team-killers
  
• Customizable Slaps
  
  Allows you to have a !slap command for players to have fun and bitch slap each-other
  
• Customizable Insults
  
  Allows you to have an !insult command for players to have fun and insult each-other
  
• Track Violations
  
  Allows you to use commands such as !violations or !violations {player} to view a detailed history of player violations during the round

Missing Features

• Punishment for Base-Raping
  
• Punishment for Base-Camping
  
• Private messages
  
• White-list based on Clan-Tag

Rules of Engagement - Punishable Incidents

Code:

Legend
-- base boundary

Team Killing
(inside or outside base)
+-------------------------+
¦ ¦
¦ o \o_ ¦
¦ \=--> / ¦
¦ /\ // ¦
¦ ¦ o \o_
¦ ¦ \=--> /
¦ ¦ /\ //
¦ ¦
+-------------------------+

Settings

• console
  (String) - used for running commands from within ProCon
  
  e.g !violations micovery
  
• debug_level
  (integer >= 0) - Level of tracing messages printed to the plugin console. 0 is the lowest, with least debug messages. The higher the value, the more tracing messages could be printed.
  
• max_kick_votes
  (integer > 0) - maximum number of votes that a soldier can receive before being kicked.
  e.g if max_kick_votes = 3, soldier is kicked that the 4th vote.
  
• max_ban_votes
  (integer > 0) - maximum number of votes that a soldier can receive before being banned.
  e.g if max_ban_votes = 3, soldier is banned that the 4th vote.
  
• say_team_kill
  true - inform killer and victim (in chat box) of team kill violation
  false - do not inform killer or victim of team kill violation
  
• punish_team_kill
  true - allows victim to punish the team killer
  false - forbids victim from punishing the team killer
  
• forgive_team_kill
  true - allows victim to forgive the team killer
  false - forbids victim from forgiving the team killer
  
• kick_team_kill
  true - allows victim to vote kick the team killer
  false - forbids victim from vote kicking the team killer
  
• ban_team_kill
  true - allows victim to vote ban the team killer
  false - forbids victim from vote banning the team killer
  
• mock_suicide
  true - server mocks the soldier that suicided (private message)
  false - no message sent on suicide
  
• slap_player
  true - allows soldiers to slap each other with a big smelly tuna fish
  false - forbids soldiers from slapping each other
  
• insult_player
  true - allows soldiers to insult each other, random insult is sent privately
  false - forbids soldiers from insulting each other
  
• admin_list
  (Stringlist) - list of soldiers that are allowed to modify/view plugin settings while in-game.
  
• player_white_list
  (Stringlist) - list of soldiers that have immunity against punish, kick, and ban
  
• ban_type
  GUID - ban players by EA GUID
  Name - ban players by EA soldier name
  IPAddress - ban players by IP Address
  
• ban_duration
  Permanent - ban indefinitely
  Round - ban until the end of the current round
  Temporary - ban temporarily (you need to set ban_minutes as well)
  
• ban_minutes
  (integer > 0) - Number of minutes to ban a player after being vote banned

Advanced Settings

Do not use these settings if you are just beginning to learn how to use this plugin. These settings allow you to tweak default behaviors for actions againts rule violators, as well as default messages.

• auto_action
  None - no action is perfomed when auto_action_max threshold is reached
  Ban - player is banned when auto_action_max threshold is reached
  Kick - player is kicked when auto_action_max threshold is reached
  
• auto_action_max
  (interger >= 1) - maximum number of punishments that a player can receive before being auto kicked or banned
  For example, if the value of auto_action_max is 3, the player will be kicked/banned on the 4th punishment received
  
• auto_punish_team_kill
  true - team killer is automatically punished, and victim is not allowed to take any action
  false - team killer is not automatically punished
  
  Note that when auto_punish_* settings are enabled, then the corresponding setting punish_* is ignored.
  
• slap_msg_list
  (StringList) - list of messages used for the !slap command
  
• mock_msg_list
  (StringList) - list of messages used to mock a player after suicide
  
• insult_msg_list
  (StringList) - list of messages used for the !insult command
  
• team_kill_warn_list
  (StringList) - ordered list of warning messages that are sent to team killers after a violation.
  
  Note that the order of the messages in the warning lists is relevant.
  The first message is sent when the first violation happends.
  The second message is sent when the second violation happens, and so on.

Public Commands

• !punish [name-substring]
  
  This is the main command, and most fun of all. It allows victims to punish soldiers who violated the rules of engagement. If "!punish" is used without specifying the soldier name, then the last aggressor with ROE violation (against the victim) is punished. Punishments cannot be stacked. For example, if an aggressor team kills a victim twice, then the victim can only punish the aggressor once. However, punishments by different victims are stackable. For example, if an aggressor team kills two victims, and both decide to punish him, then the aggressor is punished twice consecutively. Note that if an aggressor is dead, punishments are queued and applied on re-spawn.
  
• !votekick [name-substring]
  
  This is a lesser used command, but still powerful. It allows victims to cast votes against soldiers who violated the rules of engagement. If "!votekick" is used without specifying the soldier name, then the last aggressor with ROE violation (against the victim) is voted against. Votes are stackable. For example, if an aggressor team kills a victim twice, he can vote once against the aggressor, with two votes being cast. When a victim casts a kick vote against an aggressor, all other victims of that aggressor, who have not taken action, are reminded to vote. This is similar to a traditional votekick, with the difference that only victims of the aggressor are allowed to vote.
  
• !voteban [name-substring]
  
  This is also a lesser used command, but extremely powerful. It allows victims to cast votes against soldiers who violated the rules of engagement. If "!voteban" is used without specifying the soldier name, then the last aggressor with ROE violation (against the victim) is voted against. Votes are stackable. For example, if an aggressor team kills a victim twice, he can vote once against the aggressor, with two votes being cast. When a victim casts a ban vote against an aggressor, all other victims of that aggressor, who have not taken action, are reminded to vote. This is similar to a traditional voteban, with the difference that only victims of the aggressor are allowed to vote.
  
• !forgive [name-substring]
  
  This is a command of camaraderie. It allows victims to forgive soldiers who violated the rules of engagement. When forgiving, the victim waives the right to take action against the aggressor for all previous ROE violatons. This command is mostly used by soldiers forgiving teammates afer an accidental team kill.
  
• !slap [name-substring]
  
  This command is just for fun. It allows soldiers to slap each other publicly. The type of slap is chosen randomly from the settings file.
  
• !insult [name-substring]
  
  This is another useless, but fun command. It allows soldiers to privately insult each other. The pre-defined insults in the settings file are mostly jokingly insults. Insults are chosen at random.
  
• !my violations
  
  This is a statistics command. It allows a soldier to view his rules of engagement violations, such as team killing, base raping, and base camping. It displays the name of the victims, together with the total and pending violations against each victim. Pending violations are those for which the victim has not yet taken action.

Admin Commands

• !punisher settings
  
  This command prints the values of all plugin variables.
  
• 1. !set {variable} {to|=} {value}
  2. !set {variable} {value}
  3. !set {variable}
  
  This command is used for setting the value of this plugin's variables. For the 3rd invocation syntax the value is assumed to be "true".
  
• !get {variable}
  
  This command prints the value of the specified variable.
  
• !enable {variable-substring}
  
  This command is a shortcut for enabling (setting to "true") multiple variables at the same time.
  For example, the following command
  
  
  
  
  
  

  
  
  !enable punish

  esults in all variables that contain the word "punish" being set to "true"
  
• !disable {variable-substring}
  
  This command is a shortcut for disabling (setting to "false") multiple variables at the same time.
  For example, the following command
  
  
  
  
  
  

  
  
  !disable punish

  results in all variables that contain the word "punish" being set to "false"
  
• !violations {name-substring}
  
  This command prints a detailed report of the specified soldier's ROE violations. This is similar to !my violations command.
  
• !violations
  
  This command prints a summary of all soldiers' ROE violations

Default Team-Kill Warnings

The warnings list is modifiable from within the plugin in the Advanced section. You don't have to modify the plugin source code.

Code:
/*
######################################################################################
## Team kill warnings
######################################################################################
####
#### This is list of warnings that are sent to team killer.
#### For each team kill, one warning is sent to the player who violated the rules.
####
#### You can have as many warnings as you want.
#### They are sent in the same order as listed.
####
#### The following replacements can be used:
####
#### %killer% - the name of the soldier that team killed
#### %victim% - the name of the soldier that was team killed
#### %count% - the number of team kills by the killer
####
*/


List<string> default_warn_team_kill = new List<string>(new string[]
{
"%killer%, no team killing please",
"%killer%, you have two team kills!",
"%killer%, you have %count% team kills!"
});

Default Insults

The insults list is modifiable from within the plugin in the Advanced section. You don't have to modify the plugin source code.

Code:
/*
######################################################################################
## Insults
######################################################################################
####
#### This is a list of insults that users can send to each other with the '!insult' command
#### You can have as many insults as you want. Insults are chosen at random. Only the sender
#### and the reciever of the insult see the message in the chat box.
####
#### The variable 'insult_player' controls whether insulting is allowed or not.
####
*/

List<string> default_insults = new List<string>(new string[]
{
"%name%, don't go away mad. Just go away.",
"%name%, I'd like to help you out ... which way did you come in.",
"%name%, you are so down to earth but not quite far down enough.",
"%name%, you are living proof that manure can grow legs and walk.",
"%name%, you are no longer beneath my contempt.",
"%name%, tell me where your family tree is I'd like to cut it down!",
"%name%, when I look into your eyes, I see the back of your head.",
"%name%, I reprimanded my son for mimicking you. I told him not to act like a fool.",
"%name%, make a mental note ... oh, I see you're out of paper!",
"%name%, I hear you changed your mind! And got back two cents.",
"%name%, I heard you got a brain transplant and the brain rejected you!",
"%name%, I heard the doctors examined your head and found nothing.",
"%name%, I know you are nobody's fool. You're everybody's.",
"%name%, you are so ugly, the tide runs away from you.",
"%name% is so ugly he went to the zoo and they kept him.",
"%name% is so so ugly, he went to a freak show and got a permanent job.",
"%name% fell out of the ugly tree, you hit every branch on the way down.",
"%name%, in the morning I will be sober, but you will still be ugly!",
"%name%, Is it Halloween? Oh ... that's your real face.",
"%name%, don't turn the other cheek. It's just as ugly.",
"%name%, your'so ugly the only place you're ever invited is outside."
});

Default Mocks

The mocks list is modifiable from within the plugin in the Advanced section. You don't have to modify the plugin source code.

Code:
/*
######################################################################################
## Mocks
######################################################################################
####
#### This is a list of mockeries that are sent to soldiers when they suicide.
#### The suicide mockery message is chosen at random.
####
#### The variable 'mock_suicide' controls whether soldiers are mocked on suicide or not.
####
*/

List<string> default_mocks = new List<string>(new string[]
{
"%name% suicided, epic fail!",
"%name% suicided, are you even trying soldier!",
"%name% suicided, press Alt-F4 for auto-revive! "
});

Default Slaps

The slaps list is modifiable from within the plugin in the Advanced section. You don't have to modify the plugin source code.

Code:
/*
######################################################################################
## Slaps
######################################################################################
####
#### This is a list of slaps that users can give each other with the '!slap' command.
#### You can have as many types of slaps as you can come up with. Slaps are chosen at random.
#### Slaps are publicly announced.
####
#### The variable 'slap_player' controls whether insulting is allowed or not.
####
*/

List<string> default_slaps = new List<string>(new string[]
{
"%sender% slapped %receiver% with a big smelly tuna fish!",
"%sender% bitch slapped %receiver%!",
"%sender% slapped %receiver% to the back of the head!",
"%sender% ninja slapped %receiver%!",
"%sender% pimp slapped %receiver%!",
"%sender% cheek slapped %receiver%!",
"%sender% butt slapped %receiver%!",
"%sender% slapped %receiver% in the face with a rotten old fish!",
"%sender% slapped %receiver% with a large trout!",
"%sender% slapped %receiver% with the remains of a big Smelly Trout!",
"%sender% slapped %receiver% with a big bucket of fish!",
"%sender% slapped %receiver% with a silk glove!",
"%sender% slapped %receiver% with a wet noddle!",
"%sender% slapped %receiver% to wake him up!",
"%sender% slapped %receiver% with a fluffy pillow!",
"%sender% slapped %receiver% with a rubber chicken!",
"%sender% slapped %receiver%'s face so hard, %receiver% has to walk backwards from now on to see where he/she is going!",
"%sender% slapped some sense into %receiver% with a red brick!",
"%sender% slapped %receiver% with a fire hose!",
"%sender% slapped %receiver% with a huge law suit!",
"%sender% slapped %receiver% with a great big, wet, 100% rubber duck!",
"%sender% slapped %receiver% with a gallon of hot fudge covered ice-cream topped with peanut-butter M&M's!",
"%sender% slapped %receiver% with a large squid ... I hope you like seafood!",
"%sender% slapped %receiver% with a soft feather pillow full of drake feathers!",
"%sender% slapped %receiver% on the butt really hard!",
"%sender% slapped %receiver% in the nuts!"
});

Description

This plugin is a customizable limits/rules enforcer. It allows you to setup and enforce limits based on player statistics, and server state.

It tracks extensive Battlelog stats, and round stats. If you feel that there is a stat, or aggregate, or information that really needs to be included, post feedback on this thread. The plugin supports events like OnKill, OnTeamKill, OnJoin, OnSpawn, etc. You are able to perform actions triggered by those events.

For a full list of examples, jump to the index in the Insane Limits - Examples thread.

By default, the plugin ships with virtual_mode set to True. This allows you to test your limits/rules without any risk of accidentally kicking or banning anyone. Once you feel your limits/rules are ready, you can disable virtual_mode.

Think this plugin is awesome? You can buy me a beer.

Video Demo



Disclaimer

If you are careless with the rules, sometimes you can end up hurting more than helping. Having said that, it's not up to me or anyone to judge the merit of a limit/rule, otherwise this can become a flame war. Be polite when replying to posts in this thread, and don't flame others because you don't like their rules. I just give you the tool, and you (the server admin) make the rules.

My advise is, think creatively when coming up with the rules, and be open minded. If you do not know how to express your limit ideas in C#, ask in this thread. The data is there, available, ready to be consumed ... you just have to come up with the ideas.

• Download the zip file containing the plugin source (in the attachments)
  
• Extract the source file InsaneLimits.cs
  
• Copy the source file to ProCon's Plugins/BF3 directory

• serverInfo
  
• mapList.list
  
• mapList.getMapIndices
  
• admin.listPlayers all
  
• punkBuster.pb_sv_command pb_sv_plist
  
• punkBuster.pb_sv_command pb_sv_ban
  
• punkBuster.pb_sv_command pb_sv_kick

• <procon>/
  
• <procon>/Plugins/BF3

• OnJoin - Limit evaluated when player joins
  
• OnSpawn - Limit evaluated when player spawns
  
• OnKill - Limit evaluated when makes a kill (team-kills not counted)
  
• OnTeamKill - Limit evaluated when player makes a team-kill
  
• OnDeath - Limit evaluated when player dies (suicides not counted)
  
• OnTeamDeath - Limit evaluated when player is team-killed
  
• OnSuicide - Limit evaluated when player commits suicide
  
• OnAnyChat - Limit evaluated when players sends a chat message
  
• OnInterval - Limit evaluated every check_interval number of seconds
  
• OnRoundOver - Limit evaluated when round over event is sent by PRoCon
  
• OnRoundStart - Limit evaluated after round over event, when first player spawns

When the plugin is enabled, it starts two threads:

• The fetch thread is in charge of monitoring the players that join the server. It fetches player statistics from battlelog.battlefield.com
  
• The enforcer thread is in charge of checking limits/rules against the players. When the enforcerthread finds that a player violates a limit, it performs an action (Kick, Ban) against that player.

When players join the server, they are added the stats queue. The fetch thread is constantly monitoring this queue. If there is a player in the queue, it removes him from the queue, and fetches the battlelog stats for the player.

The stats queue can grow or shrink depending on how fast players join, and how long the web-requests take. If you enable the plugin on a full server, you will see that almost immediately all players are queued for stats fetching. Once the stats are fetched for all players in the queue, they are added to the internal player's list.

The enforcer thread monitors the internal player's list at specific time intervals (check_interval). It goes through the list, one player at time. For each player, it evaluates the available limits/rules. For each limit that the player violates, the enforcer thread, executes the associated limit action.

Each time around that the enforcer thread goes through the entire player's list is called an iteration. If there are no players in the server, or there are no limits available, the enforcer skips the currentiteration and sleeps until the next iteration.

The enforcer is only responsible for Limits that evaluate OnJoin, and OnIterval, events. Enforcing for other types of events like OnKill, and OnSpawn, is done in the main thread when ProCon sends the event information.

Creation - In order to create a new limit, you have to set new_limit variable to True.

This creates a new limit section with default values that you can change.


Deletion - In order to delete a limit, you have to set the variable delete_limit to the numerical id of the limit you want to delete.

Each limit has an id number, you can see the id number in the limit name, e.g. Limit #5.

At its basic, there are four fields that determine the structure of a limit. These fields are state, action, and first_check, and second_check.

• state
  Enabled - the limit will be used by the enforcer thread
  Disabled - the limit will be ignored by the enforcer thread
  Virtual - the limit will be used, but actions will be done in virtual_mode
  
  This field is useful if you want to temporarily disable a limit from being used, but still want to preserve its definition.
  
• action
  (string, psv) - list of actions for this limit (Pipe separated ""|"")
  
  e.g. Say | PBBan | Mail
  
  These are all the allowed actions:
  
  • None - no action is performed against the player
    
  • Kick - player is kicked, if the limit evaluates to True
    
  • EABan - player is banned (using the BF3 ban-list), if the limit evaluates True
    
  • PBBan - player is banned (using PunkBuster ban-list), if the limit evaluates True
    
  • Kill - kills the player (delay optional), if the limit evaluates True
    
  • Say - sends a message the server (All, Team, Squad, or Player), if the limit evaluates True
    
  • Log - logs a message to a File, Plugin log, or both, if the limit evaluates True
    
  • Mail - sends an e-mail to specified address, if the limit evaluates True
    
  • SMS - sends an SMS message to the specified phone number, if the limit evaluates True
    
  • TaskbarNotify - sends a Windows Taskbar notification, if the limit evaluates True
  Depending on the selected action, other fields are shown to specify more information about the action.
  
  Supported PB ban-duration: Permanent, Temporary
  Supported PB ban-type: PB_GUID (default)
  
  Supported EA ban-duration: Permanent, Temporary, Round
  Supported EA ban-type: EA_GUID, IPAddress, Name
  
  Also note that each of these actions have a target player. You have to be careful on what targetis for each action.
  
  For example, during a Kill event, the target of the action is the Killer. But, during a Death event, the target of the action is the player that was killed. You don't want to accidentally Kick/Ban the wrong player!
  
• first_check
  Disabled - the limit does not evaluate anything in the first step of evaluation
  Expression - the limit uses a C# conditional expression during the first step of evaluation
  Code - the limit uses a C# code snippet (must return true/false) during the first step of evaluation
  
• second_check
  Disabled - the limit does not evaluate anything in the second step of evaluation
  Expression - the limit uses a C# conditional expression during the second step of evaluation
  Code - the limit uses a C# code snippet (must return true/false) during the second step of evaluation
  
  Depending on the selected check type, an extra field will be shown for specifying the Expression, or Code text.

After compilation, limit evaluation is by far the most important of all steps this plugin goes through.

Limit evaluation is comprised of three steps:

• first_check Evaluation
  
  During this step, the plugin executes the Expression/Code in first_check to get a True or Falseresult.
  
  If the result is False, the plugin does not perform any action, and quits. But, if it's True, it keeps going to the next step
  
• second_check Evaluation (optional)
  
  Next, the plugin runs the Expression/Code for the second_check, if it's enabled. If it's not enabled, it keeps going to next step.
  
• action Execution
  
  If the final result of the limit evaluation is True, the plugin then executes the action associated with the limit.
  
  If the final result of the limit evaluation is False, no action is executed.

When writing a limit Expression or Code snippet, there are several globally defined objects that can be used. These are server, player, killer, victim, kill, plugin, team1, team2, team3, team4, and limit. These objects contain values, and functions that can be accessed from within the Expressions, or Codesnippets.

The limit object represents the state the limit that was just activated. This object is only available during the second_check. The limit object implements the following interface:

Code:
public interface LimitInfoInterface
{
//Number of times the limit has been activated, (Current round)
double Activations(String PlayerName);
double Activations(int TeamId, int SquadId);
double Activations(int TeamId);

// Number of times player has activated this limit (Current round) in the given TimeSpan, e.g. last 10 seconds, etc
double Activations(String PlayerName, TimeSpan time);
double Activations();


//Number of times the limit has been activated (All rounds)
double ActivationsTotal(String PlayerName);
double ActivationsTotal(int TeamId, int SquadId);
double ActivationsTotal(int TeamId);
double ActivationsTotal();

// Number of times this limit has been activated by player
/*
* Kill, TeamKill: Spree value is reset when player dies
* Death, TeamDeath, and Suicide: Spree value is reset whe player makes a kill
*
* Spawn, Join, Interval: Spree value is never reset, you may reset it manually.
*/

double Spree(String PlayerName);

// manually resets the Spree value for the player, (only for power-users)
void ResetSpree(String PlayerName);

/* Data Repository set/get custom data */
DataDictionaryInterface Data { get; }
DataDictionaryInterface RoundData { get; } //this dictionary is automaticaly cleared OnRoundStart

/* Other methods */
String LogFile { get; }
}

The teamX object represents the state of the team with id X at the moment that the limit is being evaluated. The teamX object implements the following interface:

Code:
public interface TeamInfoInterface
{
List<playerinfointerface> players { get; }

double KillsRound { get; }
double DeathsRound { get; }
double SuicidesRound { get; }
double TeamKillsRound { get; }
double TeamDeathsRound { get; }
double HeadshotsRound { get; }
double ScoreRound { get; }

int TeamId { get; }
double Tickets { get; }
double RemainTickets { get; }
double RemainTicketsPercent { get; }
double StartTickets { get; }
}

The server object represents the state of the server at the moment that the limit is being evaluated. The server object implements the following interface:

Code:
public interface ServerInfoInterface
{
/* Server State */
int CurrentRound { get; }
int TotalRounds { get; }
int PlayerCount { get; }
int MaxPlayers { get; }

/* Current Map Data */
int MapIndex { get; }
String MapFileName { get; }
String Gamemode { get; }

/* Next Map Data */
int NextMapIndex { get; }
String NextMapFileName { get; }
String NextGamemode { get; }

/* All players, Current Round, Stats */
double KillsRound { get; }
double DeathsRound { get; } // kind of useless, should be same as KillsTotal (suicides not counted as death)
double HeadshotsRound { get; }
double SuicidesRound { get; }
double TeamKillsRound { get; }

/* All players, All rounds, Stats */
double KillsTotal { get; }
double DeathsTotal { get; } // kind of useless, should be same s KillsTotal (suicides not counted as death)
double HeadshotsTotal { get; }
double SuicidesTotal { get; }
double TeamKillsTotal { get; }

/* Weapon Stats, Current Round, All Rounds (Total)*/
WeaponStatsInterface this[String WeaponName] { get; }

/* Other data */
double TimeRound { get; } // Time since round started
double TimeTotal { get; } // Time since plugin enabled
double TimeUp { get; } // Time since last server restart
double RoundsTotal { get; } //Round played since plugin enabled

/* Team data */
double Tickets(int TeamId); //tickets for the specified team
double RemainTickets(int TeamId); //tickets remaining on specified team
double RemainTicketsPercent(int TeamId); //tickets remaining on specified team (as percent)

double StartTickets(int TeamId); //tickets at the begining of round for specified team
double TargetTickets { get; } //tickets needed to win

int WinTeamId { get; } //id of the team that won previous round

/* Data Repository set/get custom data */
DataDictionaryInterface Data { get; }
DataDictionaryInterface RoundData { get; } //this dictionary is automaticaly cleared OnRoundStart
}

The kill object represents information about the kill event. The kill object implements the following interface:

Code:
public interface KillInfoInterface
{
String Weapon { get; }
bool Headshot { get; }
}

The player object represents the state of player for which the current limit is being evaluated. Theplayer object implements the following interface:

Code:
public interface PlayerInfoInterface
{
/* Online statistics (battlelog.battlefield.com) */
double Rank { get; }
double Kdr { get; }
double Time { get; }
double Kills { get; }
double Wins { get; }
double Skill { get; }
double Spm { get; }
double Score { get; }
double Deaths { get; }
double Losses { get; }
double Repairs { get; }
double Revives { get; }
double Accuracy { get; }
double Ressuplies { get; }
double QuitPercent { get; }
double ScoreTeam { get; }
double ScoreCombat{ get; }
double ScoreVehicle{ get; }
double ScoreObjective { get; }
double VehiclesKilled { get; }
double Kpm { get; }

double ReconTime { get; }
double EngineerTime { get; }
double AssaultTime { get; }
double SupportTime { get; }
double VehicleTime { get; }
double ReconPercent { get; }
double EngineerPercent { get; }
double AssaultPercent { get; }
double SupportPercent { get; }
double VehiclePercent { get; }

/* Player data */
String Name { get; }
String FullName { get; } // name including clan-tag
String Tag { get; }
String IPAddress { get; }
String CountryCode { get ; }
String CountryName { get; }
String PBGuid { get; }
String EAGuid { get; }
int TeamId { get; }
int SquadId { get; }


/* Current round, Player Stats */
double KdrRound { get; }
double KpmRound { get; }
double SpmRound { get; }
double ScoreRound { get; }
double KillsRound { get; }
double DeathsRound { get; }
double HeadshotsRound { get; }
double TeamKillsRound { get; }
double TeamDeathsRound { get; }
double SuicidesRound { get; }
double TimeRound { get; }

/* All rounds, Player Stats */
double KdrTotal { get; }
double KpmTotal { get; }
double SpmTotal { get; }
double ScoreTotal { get; }
double KillsTotal { get; }
double DeathsTotal { get; }
double HeadshotsTotal { get; }
double TeamKillsTotal { get; }
double TeamDeathsTotal { get; }
double SuicidesTotal { get; }
double TimeTotal { get; }
double RoundsTotal { get; }

/* Weapon Stats, Current Round, All Rounds (Total) */
WeaponStatsInterface this[String WeaponName] { get; }

/* Other Data */
DateTime JoinTime { get; }

/* Whitelist information */
bool inClanWhitelist { get; }
bool inPlayerWhitelist { get; }
bool isInWhitelist { get; }

/* Data Repository set/get custom data */
DataDictionaryInterface Data { get; }
DataDictionaryInterface RoundData { get; } //this dictionary is automaticaly cleared OnRoundStart
}

The plugin represents this plugin itself. It gives you access to important functions for executing server commands, and interacting with ProCon. The plugin object implements the following interface:

Code:
public interface PluginInterface
{
/*
* Methods for sending messages
*/
void SendGlobalMessage(String message);
void SendTeamMessage(int teamId, String message);
void SendSquadMessage(int teamId, int squadId, String message);

/*
* Methods used for writing to the Plugin console
*/
void ConsoleWrite(String text);
void ConsoleWarn(String text);
void ConsoleError(String text);
void ConsoleException(String text);

/*
* Methods for getting whitelist information
*
*/
bool isInWhitelist(String PlayerName);
bool isInPlayerWhitelist(String PlayerName);
bool isInClanWhitelist(String PlayerName);
bool isInWhiteList(String PlayerName, String list_name);

/*
* Methods getting and setting the Plugin's variables
*/
bool setPluginVarValue(String variable, String value);
String getPluginVarValue(String variable);

/*
* Method: R
*
* Replaces tags like %p_n% (Player Name), %k_n% (Killer Name), %v_n% (Victim Name), etc
*/
String R(String message);

/*
* Methods for player actions
*/
bool KickPlayerWithMessage(String name, String message);
bool KillPlayer(String name);
bool EABanPlayerWithMessage(EABanType type, EABanDuration duration, String name, int minutes, String message);
bool PBBanPlayerWithMessage(PBBanDuration duration, String name, int minutes, String message);
void ServerCommand(params String[] arguments);

/*
* Examples:
*
* KickPlayerWithMessage(micovery , Kicked you for team-killing!);
* EABanPlayerWithMessage(EABanType.EA_GUID, EABanDuration.Temporary, micovery, 10, You are banned for 10 minutes!);
* PBBanPlayerWithMessage(PBBanDuration.Permanent, micovery, 0, You are banned forever!);
* ServerCommand(admin.listPlayers, all);
*/


/* Other Methods */
bool SendTaskbarNotification(String title, String messagge);
bool Log(String file, String messagge);

/*
* Creates a file in ProCOn's directory (InsaneLimits.dump)
* Detailed information about the exception.
*/
void DumpException(Exception e);

/* Data Repository set/get custom data */
DataDictionaryInterface Data { get; }
DataDictionaryInterface RoundData { get; } //this dictionary is automaticaly cleared OnRoundStart
}

The Data object is a nested dictionary of key/value pairs that you can use to store custom data inside the plugin, server, limit, player, killer, and victim objects. The Data object implements the following interface:

Code:
public interface DataDictionaryInterface
{
/* String Data */
String setString(String key, String value);
String getString(String key);
String unsetString(String key);
bool issetString(String key);

/* Boolean Data */
bool setBool(String key, bool value);
bool getBool(String key);
bool unsetBool(String key);
bool issetBool(String key);

/* Double Data */
double setDouble(String key, double value);
double getDouble(String key);
double unsetDouble(String key);
bool issetDouble(String key);

/* Int Data */
int setInt(String key, int value);
int getInt(String key);
int unsetInt(String key);
bool issetInt(String key);

/* Object Data */
object setObject(String key, object value);
object getObject(String key);
object unsetObject(String key);
bool issetObject(String key);

/* Generic set/get methods */
Object set(Type type, String key, Object value);
Object get(Type type, String key);
Object unset(Type type, String key);
bool isset(Type type, String key);

/* Other methods */
void Clear(); /* clear/unset all data from repository */

}

This plugin supports an extensive list of message text replacements. A replacement is a string that starts and ends with the percent character %. When you use them in the text of a message, the plugin will try to replace it with the corresponding value. For example:

The message

Code:
%k_n% killed %v_n% with a %w_n%

Code:

micovery killed NorthEye with a PP-2000

Code:
// Killer Replacements (Evaluations: OnKill, OnDeath, OnTeamKills, and OnTeamDeath)

/* Legend:
* k - killer
* n - name
* ct - Clan-Tag
* cn - Country Name
* cc - Country Code
* ip - IPAddress
* eg - EA GUID
* pg - Punk Buster GUID
*/

%k_n% Killer name
%k_ct% Killer clan-Tag
%k_cn% Killer county-name
%k_cc% Killer county-code
%k_ip% Killer ip-address
%k_eg% Killer EA GUID
%k_pg% Killer Punk-Buster GUID
%k_fn% Killer full name, includes Clan-Tag (if any)

// Victim Replacements (Evaluations: OnKill, OnDeath, OnTeamKills, and OnTeamDeath)

/* Legend:
* v - victim
*/

%v_n% Victim name,
%v_ct% Victim clan-Tag
%v_cn% Victim county-name
%v_cc% Victim county-code
%v_ip% Victim ip-address
%v_eg% Victim EA GUID
%v_pg% Vitim Punk-Buster GUID
%v_fn% Victim full name, includes Clan-Tag (if any)

// Player Repalcements (Evaluations: OnJoin, OnSpawn, OnAnyChat, and OnSuicide)

/* Legend:
* p - player
* lc - last chat
*/

%p_n% Player name
%p_ct% Player clan-Tag
%p_cn% Player county-name
%p_cc% Player county-code
%p_ip% Player ip-address
%p_eg% Player EA GUID
%p_pg% Player Punk-Buster GUID
%p_fn% Player full name, includes Clan-Tag (if any)
%p_lc% Player, Text of last chat

// Weapon Replacements (Evaluations: OnKill, OnDeath, OnTeamKill, OnTeamDeath, OnSuicide)

/* Legend:
* w - weapon
* n - name
* p - player
* a - All (players)
* x - count
*/

%w_n% Weapon name,
%w_p_x% Weapon, number of times used by player in current round
%w_a_x% Weapon, number of times used by All players in current round

// Limit Replacements for Activations & Spree Counts, Current Round (Evaluations: Any)

/* Legend:
* th - ordinal count suffix e.g. 1st, 2nd, 3rd, 4th, etc
* x - count, 1, 2, 3, 4, etc
* p - player
* s - squad
* t - team
* a - All (players)
* r - SpRee
*/

%p_x_th% Limit, ordinal number of times limit has been activated by the player
%s_x_th% Limit, ordinal number of times limit has been activated by the player's squad
%t_x_th% Limit, ordinal number of times limit has been activated by the player's team
%a_x_th% Limit, ordinal number of times limit has been activated by all players in the server
%r_x_th% Limit, ordinal number of times limit has been activated by player without Spree value being reset
%p_x% Limit, number of times limit has been activated by the player
%s_x% Limit, number of times limit has been activated by the player's squad
%t_x% Limit, number of times limit has been activated by the player's team
%a_x% Limit, number of times limit has been activated by all players in the server
%r_x% Limit, number of times limit has been activated by player without Spree value being reset

// Limit Replacements for Activations, All Round (Evaluations: Any)
/* Legend:
* xa - Total count, for all rounds
*/
%p_xa_th% Limit, ordinal number of times limit has been activated by the player
%s_xa_th% Limit, ordinal number of times limit has been activated by the player's squad
%t_xa_th% Limit, ordinal number of times limit has been activated by the player's team
%a_xa_th% Limit, ordinal number of times limit has been activated by all players in the server
%p_xa% Limit, number of times limit has been activated by the player
%s_xa% Limit, number of times limit has been activated by the player's squad
%t_xa% Limit, number of times limit has been activated by the player's team
%a_xa% Limit, number of times limit has been activated by all players in the server

// Other replacements
%date% Current date, e.g. Sunday December 25, 2011,
%time% Current time, e.g. 12:00 AM

%server_host% Server/Layer host/IP
%server_port% Server/Layer port number

%l_id% Limit numeric id"
%l_n% Limit name""

This plugin is intended to adjust the number of tickets based upon the number of players on the server just before the new maps is started (it checks right after the countdown on the stats screen finishes). The number of tickets can be specified as a percentage of the map default, or as an exact number (so that all maps will be the same).

This plugin was designed for use on Conquest maps, so it will ignore maps with other game modes by default, allowing you to run a mixed-mode server and only adjust the ticket count on the Conquest maps. If you want to use the plugin on a server that doesn't play Conquest maps, you can tell it not to ignore the other game modes.

This plug-in has no in-game commands.

If enabled, only changes the ticket count on Conquest maps.

Ticket percentage to use on non-Conquest maps when the previous option is enabled.

Choose whether you would prefer to specify the number of tickets as a percentage of the map default or as an exact number (so that all maps will be the same). On maps that start with a different number of tickets for each side (i.e. Back To Karkand maps), the specified ticket count will be applied to the side with the larger number of tickets.

The percentage or number of tickets that will be set when X players are active on the server. If you don't run a 64-player server, just ignore the options above your max server size, as they will not be used.

If enabled, displays debug info in the console window.

Description: watch the language on the server and take appropriate action

Param :

Max kill before kick

Max kick before Tban

Max Tban before Ban

White list

Kill word

Kick word

Tban word

Ban word

using :

adding >word< in kill word list. (without ><)

ex: con in kill word list.

*** toto say : le petit con

Result : Toto have been killed for using a bad word

Use the regex to a best performance :

*** toto say : j'ai une constipation

If you just use a simple word, you kill toto but constipation is not a bad word :S

You need to use a regex => "con[ne]*[^a-z]+[ .]*"

For adding a regex add "" between the word.

Result : toto is not killed \o/