Jump to content
Infinity Gaming

Procon Admin Tool

98 files

  1. Insane Limits

    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. Several limits are available in the Procon Plugin Enhancements forum.

    Version 0.9.4.0 and later is optionally integrated with a MySQL server (using the Battlelog Cache plugin). This enables caching of Battlelog stats fetching, which over time should reduce the delay caused by restarting Procon/enabling Insane Limits when your server is full. This should also reduce load on Battlelog, which in turn will reduce the number of Web errors and exceptions. This version is compatible with TrueBalancer and other plugins that use stats fetching.

    In addition to keeping track of player statistics, the plugin also keeps tracks of the number of times a player has activated a certain limit/rule. I got this idea from the ProCon Rulz plugin. With this meta-information about limits, you are able to create much more powerful rules such as Spree messages. If it's not clear now, it's ok, look at end of the documentation for examples that make use if this information.

    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.

    Minimum Requirements
    This plugin requires you to have sufficient privileges for running the following commands:
    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 Additionaly, you need to have Read+Write file system permission in the following directories:
    <ProCon>/
    <ProCon>/Plugins/BF3
    <ProCon>/Plugins/BF4
    Supported Limit Evaluations
     
    OnJoin - Limit evaluated when player joins OnLeave - Limit evaluated when player leaves 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 (suices 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 - (deprecated) Same behavior as OnIntervalPlayers OnIntervalPlayers - Limit evaluated (for all players) every evaluation_interval number of seconds (minimum 10) OnIntervalServer - Limit evaluated once every evaluation_interval number of seconds (minimum 10) OnRoundOver - Limit evaluated when round over event is sent OnRoundStart - Limit evaluated after round over event, when first player spawns OnTeamChange - Limit evaluated after after player switches teams Note that limit evaluation is only performed after the plugin has fetched the player stats from Battlelog. If a player joins the server, and starts team-killing, there will be a couple of seconds before the plugin catches on. Having said that, this is rare behavior. Most of the time, by the time the player spawns for the first time, the plugin would have already fetched the stats.

    When you enable the plugin for the first time in a full server, it will take a couple of minutes to fetch all player stats


    Architecture
    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 evaluating Interval limits. When the enforcer thread finds that a player violates a limit, it performs an action (Kick, Ban, etc) against that player.
    The two threads have different responsibilities, but they synchronize their work.

    Fetch-thread Flow
     
    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. Enforcer-thread Flow
    The enforcer thread runs on a timer (every second). It checks if there are any interval limits ready to be executed. If there are, it will evaluate those limits.
    Each time around that the enforcer checks for the available limits is called an iteration. If there are no players in the server, or there are no limits available, the enforcer skips the current iteration and sleeps until the next iteration.

    The enforcer is only responsible for Limits that evaluate OnIterval, events. Enforcing for other types of events like OnKill, and OnSpawn, is done in the main thread when procon sends the event information.
    Limit Management
    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.
    Limit Definition
    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, and actions will be performed live
    Virtual - the limit will be used, but actions will be done in virtual_mode
    Disabled - the limit will be ignored
    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 Tweet - posts a Twitter status update (default account is @InsaneLimits), if the limit evaluates True PBCommand - executes the specified PunkBuster command, if the limit evaluates True ServerCommand - executes the specified Server command, if the limit evaluates True PRoConChat - sends the specified text to PRoCon's Chat-Tab, if the limit evaluates True PRoConEvent - adds the specified event to PRoCon's Events-Tab, if the limit evaluates True TaskbarNotify - sends a Windows Taskbar notification, if the limit evaluates True SoundNotify - plays a sound notification with the specified sound file, if the limit evaluates True Yell - yells a message to the server (All, Team, or Player), 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 target is 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 accidentaly 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.

    Both Expressions, and Code snippets must be syntactically correct in accordance to the C# language. The plugin compiles your Expression/Code in-memory with the Microsoft C# Compiler. If there are compilation errors, those are shown in the plugin log.

    If you do not know what C# is, or what an expression is, or what a code snippet is ... do not worry. Study the examples in the Examples Index forum thread. Then, if you are still unclear, how to write an expression or a code snippet, ask for help in forums at phogue.net
    Limit Evaluation
    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 False result.
    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. Settings
    use_direct_fetch
    True - if the cache is not available, fetch stats directly from Battlelog
    False - disable direct fetches from Battlelog

    If the Battlelog Cache plugin is installed, up to date and enabled, it will be used for player stats regardless of the setting of this option. If the Battlelog Cache plugin is not installed, not up to date or disabled, setting use_direct_fetch to True will act as a fallback system, fetching stats directly from Battlelog. Otherwise, stats fetching will fail since the cache is not available and this setting is False. use_slow_weapon_stats
    False - skip fetching weapon stats for new players
    True - fetch weapon stats for new players

    Visible only if use_direct_fetch is set to True. Fetching weapon stats from Battlelog takes a long time, 15 seconds or more per player. By default, this slow fetch is disabled (False), so that your Procon restart or initial plugin enable time on a full server won't be delayed or bogged down while fetching weapon stats. However, if you have limits that use the GetBattlelog() function, you must set this value to True, or else stats will not be available. Also, see rcon_to_battlelog_codes. use_stats_log
    False - do not log Battlelog stats to the battle.log file
    True - log player stats to the battle.log file

    If stats fetching is enabled and stats are fetched successfully, all the stats that were fetched will be logged in a file that follows the standard logging file name pattern: procon/Logs/_/YYYYMMDD_battle.log (text file). limits_file
    (string, path) - path to the file where limits, and lists are saved auto_load_interval
    (integer >= 60) - interval in seconds, for auto loading settings from the limits_file
    player_white_list
    (string, csv) - list of players that should never be kicked or banned clan_white_list
    (string, csv) - list of clan (tags) for players that should never be kicked or banned virtual_mode
    True - limit actions (kick, ban) are simulated, the actual commands are not sent to server
    False - limit actions (kick, ban) are not simulated console
    (string) - you can use this field to run plugin commands

    For example: "!stats micovery" will print the player statistic for the current round in the plugin console.

    Note that plugin commands, are currently supported only inside ProCon, and not In-Game. rcon_to_battlelog_codes
    String[] Array - Syntax: RCON=Battlelog, e.g., U_XBOW=WARSAW_ID_P_WNAME_CROSSBOW

    Visible only if use_slow_weapon_stats is True. Lets you define mappings from RCON weapon codes to Battelog weapon stats codes. Useful when new unlocks or DLC are released and in-use before the next update of this plugin is available. You can also override incorrect mappings built-in to the plugin, if any. smtp_port
    (string) - Address of the SMTP Mail server used for Mail action smtp_port
    (integer > 0) - port number of the SMTP Mail server used for Mail action smtp_account
    (string) - mail address for authenticating with the SMTP Mail used for Mail action smtp_mail
    (string) - mail address (Sender/From) that is used for sending used for Mail action

    This is usually the same as smtp_account ... depends on your SMTP Mail provider. say_interval
    (float) - interval in seconds between say messages. Default value is 0.05, which is 50 milli-seconds

    The point of this setting is to avoid spam, but you should not set this value too large. Ideally it should be between 0 and 1 second. wait_timeout
    (int) - interval in seconds to wait for a response from the game server

    If you get several Timeout(xx seconds) expired, while waiting for ... exceptions in plugin.log, try increasing the wait_timeout value by 10 seconds. Repeat until the exceptions stop, but you should not exceed 90 seconds.
    Plugin Commands
    These are the commands supported by this plugin. You can run them from within the console field. Replies to the commands are printed in the plugin log.
    !round stats
    Aggregate stats for all players, current round

    !total stats
    Aggregate stats for all players, all rounds

    !weapon round stats
    Weapon-Level round stats for all players, current round

    !weapon total stats
    Weapon-Level stats for all players, all rounds

    !web stats {player}
    Battlelog stats for the current player

    !round stats {player}
    Aggregate stats for the current player, current round

    !total stats {player}
    Aggregate stats for the current player, all rounds

    !weapon round stats {player}
    Weapon-Level stats for the current player, current round

    !weapon total stats {player}
    Weapon-Level stats for the current player, all round

    These are the most awesome of all the commands this plugin provides. Even if you are not using this plugin to enforce any limit, you could have it enabled for just monitoring player stats.

    When calling player specific statistic commands, if you misspell, or only type part of the player name, the plugin will try to find the best match for the player name.
    !dump limit {id}

    This command creates a file in ProCon's directory containing the source-code for the limit with the specified id
    For example, the following command
    !dump limit 5
    Creates the file "LimitEvaluator5.cs" inside ProCon's directory.   This command is very useful for debugging compilation errors, as you can see the code inside the file exactly as the plugin sees it (with the same line and column offsets). !set {variable} {to|=} {value}
    !set {variable} {value}
    !set {variable}

    This command is used for setting the value of this plugin's variables.
    For the last invocation syntax the value is assumed to be "True". !get {variable}
    This command prints the value of the specified variable.
    In-Game Commands
    These are the In-Game commands supported by this plugin. You can run them only from within the game. Replies to the commands are printed in the game chat. !stats
    List the available stats, Battlelog !stats [web|battlelog]
    List the available stats, Battlelog !stats round
    List the available stats, current round !stats total
    List the available stats, all rounds
    These commands are used as a shortcut for players to view what type of stats they can query. The plugin will try to fit all stat types into a single chat message. !my {type}
    Print Battlelog stat of the specified type for the player that executed the command !my round {type}
    Print current round stat of the specified type for the player that executed the command !my total {type}
    Print all rounds stat of the specified type for the player that executed the command ?{player} {type}
    Print Battlelog stat of the specified type for the specified player ?{player} round {type}
    Print current round stat of the specified type for the specified player ?{player} total {type}
    Print all rounds stat of the specified type for the specified player Annex 1 - Boolean Operators:

    For combining Expressions you use Boolean Logic operators. These are:
    AND (Conjunction): && OR (Disjunction): || NOT (Negation): ! Annex 2 - Relational Operators:

    All the previous examples use the Greater-Than ( > ) operator a lot, but that is not the only relational operator supported. These are the arithmetic relational operators you can use:
    Greater-Than: > Greater-than-or-Equal: >= Less-than: < Less-than-or-Equal: <= Equality: == Not-Equal: !=

    2 downloads

       (0 reviews)

    0 comments

    Updated

  2. ProconRulz

    ONLINE DOCUMENTATION HERE

    SUMMARY :
    ProconRulz is a general-purpose Procon plugin that allows admin actions to be taken based on events and triggers. The most common usage is for weapon limits,

    Example :
    On Kill;Weapon SMAW;Kill (which will limit the SMAW rockets by killing any player that kills with that weapon).

    Or you can limit players NOT using certain weapons,
    Example : For a pistols-only server
    On Kill;Not Damage Handgun;Kill (which will kill any player that kills with anything NOT a pistol).

    Rulz for many example requirements are given at the end of this thread

    If you are new to ProconRulz, and look at the documentation, the fact that ProconRulz is now capable of enabling you to write sets of rulz that behave as kill-streak announcers or in-game admin or rude-word-res-ponders will appear scary at first, so don't forget ProconRulz was designed from the beginning to allow simple rulz to implement weapon limits, so it's easy to start with a single rule

    Example : Limiting nades with
    On Kill;Weapon M67;PlayerCount 3;Say Too many nade kills for %p%;Kill.
    Apply admin commands (e.g. Kill, Kick, Say) to players according to certain 'conditions' (e.g. spawned with Kit Recon). Allows programming of weapon or kit limits, with suitable messages.

    actions include kick, ban, or just a warning (yell, say).
    conditions include kit type, weapon type, and can be applied at Spawn time or on a Kill.

    Each rule has three parts:
    Trigger - i.e. when the rule should fire, On Spawn, On Kill, On Teamkill etc Conditions - list of tests to apply before actions are done, e.g. Headshot, Kit Recon etc Actions - list of admin actions to take if all conditions succeed, e.g. Kill, Kick, Say Currently included rulz sets
    Sniper Limit (proconrulz_sniperlimit.txt) - limits the number of snipers on each team to a maximum set at the top of the rulz. A sniper slot is reserved when the player kills with a sniper rifle. The sniper slot is released when the round ends, the player leaves, or the player kills with some other weapon and an announcement is issued to team. All players have the !snipers command which tells them the current snipers on their team. Also included is proconrulz_sniperdmrlimit.txt which is the same but limits both sniper rifles and DMR's. CREDIT tarreltje and see thread here Sniper Squad Limit (proconrulz_snipersquad.txt) - only permits sniper kills if you are in a particular squad (default Echo). Also supports a !snipers command that tells users what's going on. (As above, also with proconrulz_sniperdmrsquad.txt for snipers andDMR's). CREDIT staazvaind. Announcer (proconrulz_announcer.txt) - gives a few kill messages (Fred knifed Barney) for you to modify. Multi-kills (proconrulz_multikill.txt) - keeps track of short-term multi-kill streaks and makes Quake-like announcements. Credit Bl1ndy and Panther. Rules (proconrulz_rules.txt) - simple rulz that display messages when any player types !rules - for you to modify for your server. Punish (proconrulz_punish.txt) Support of !punish / !p and !forgive / !ffor teamkills. CREDIT ty_ger07 and russel5 Killstreak (proconrulz_killstreak.txt) Announces kill streaks at 5/10/15 kills etc, and when ended. Credit ty_ger07 Best 3 Players (proconrulz_best3players.txt) Particularly for TDM announces current highest kill player & each time that changes. CREDIT tarreltje. proconrulz.pdf

    3 downloads

       (1 review)

    0 comments

    Updated

  3. Mixed Gamemodes v3

    Author: ScHrAnZ DiNgEnS
    For support or to post comments regarding this plugin please visit Plugin Thread
    This plugin works with PRoCon and falls under the GNU GPL, please click here for details. If you would like to donate to support the development of PRoCon, click the link below:
    Toward the right side of the page, there is a location to enter the amount you would like to donate and whether you want the donation to be made public. Your donations are greatly appreciated and will be sent to Phogue (original creator of PRoCon).


    Description
    Nullifies any maplist control by the client and cycles through a set map list, changing gamemodes if need be. There are a lot of feature to control maps and gamemodes to easy fill up your server if the server is empty. The plugin display the next map on the end of a map and have a command to display the nextmap instantly


    Commands
    [prefix]nextmap
    Display the next map instantly to chat Prefixes that can be used are !, @, #, and /
    Settings
    Emptymap Settings
     
    Emptymap enabled
    Choose 'Yes' to enable Emptymap with all other emptymap features like 'Emptymap Maplist' and 'Playerbased Gamemodes' or No to disable.  
    Emptymap Staytime
    Choose the time in minutes how long the last map should stay before the server switch to a specific emptymap.  
    Position of Emptymap
    Specify the position of the map from Maplist wich should played if there are no players on the server to fill the server up. You can also set the value to '-1' to rotate between all maps in the Maplist. NOTE: Mapindex begins with 0 and if you have maps in 'Emptymap Maplist' the index of 'Emptymap Maplist' is used! If u enable 'PLayerbased Gamemodes' u have to choose a Squadrushmap or if Squadrush is disabled a Squaddeathmatch map! Playerbased Gamemodes
    If u want to play all Gamemodes on your server this feature will make u happy! 0-8 Players -> Squadrush will be played (or Squaddeathmatch if u disable Squadrush) 9-16 Players -> Squaddeathmatch will be played 17-32 Players -> Rush or Conquest will be played Use Playerbased Gamemodes
    choose Yes to enable 'Playerbased Gamemodes' or No to disable. Supported Gamemodes
    You can disable Squadrush here if u choose 'SQDM & RUSH/CONQUEST.
    Emptymap Maplist
    Emptymap Maplist
    This Maplist is used if there are not many players on the server, you can specify the amount of players with 'Emptymap Maplist Maxplayers' Set up the cycle with only 1 map per line and add the most played maps to fill up your server. If you enabled 'Playerbased Gamemodes' you should add Squadrush and Squaddeathmatch maps to this cycle. you can specify the number of rounds after the map e.g: levels/mp_002 1 levels/mp_002 5 levels/mp_002 3 .. or leave blank to play the default rounds for that game type (usually 2) levels/mp_002 Emptymap Maplist Maxplayers
    You can specify the amount of players to use Emptymap Maplist here. NOTE: This has no effect if u enable 'Playerbased Gamemodes' or disable Emptymap!
    Regular Maplist
    Maplist
    This Maplist is used if Emptymap is disabled or if there are more players than 'Emptymap Maplist Maxplayers' on the server. If you want to use PLayerbased Gamemodes you have to fill up this Maplist with Rush/Conquest maps. Set up the cycle with only 1 map per line, you can specify the number of rounds after the map e.g: levels/mp_002 1 levels/mp_002 5 levels/mp_002 3 .. or leave blank to play the default rounds for that game type (usually 2) levels/mp_002
    Additional Information
    CAUTION, enabling will immediately alter your maplist. You cannot have the same map played twice in a row =(
    Credits
    Credits goes to:
     
    Phogue
    For developing ProCon Phogue
    For the basepart of this plugin Hamma & Xp3r7 & powerbits
    Ideas of emptymap features DICE
    For fixing roundbug if we force a mapchange on round 1 of 2

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  4. Mixed Gamemodes

    Description
    Nullifies any maplist control by the client and cycles through a set map list, changing gamemodes if need be.

    Settings
    Maplist
    Maplist
    You can specify the number of rounds after the map e.g: levels/mp_002 1 levels/mp_002 5 levels/mp_002 3 .. or leave blank to play the default rounds for that game type (usually 2) levels/mp_002 Additional Information
    CAUTION, enabling will immediately alter your maplist. You cannot have the same map played twice in a row =( See screenshots for list of available maps

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  5. Basic Mapzone Actions

    Description
    Provides some very basic tags for base protections with map zones. This plugin is provided as an example to other plugin authors, expect more complex tags at a later date.

    Settings
    Detections
    Minimum trespass error
    How much of the circle displayed on the battlemap must be inside of the map zone. The bfbc2 server does not send exact coordinates of players, but instead has +/- 10m to each coordinate. Think of this as a "How likely was the player actually in the zone" variable Maximum distance for base camping
    How far (in meters) must a player be from the opposite player to not be penalized for base camping. Setting to 50m would mean a player is not base-camping if they are 50m's outside of the base. This would mean players can still be killed in the base, but this would give them a lot more breathing room to push an offensive. Set to a really high number if you would prefer zero-tolerance on base camping
    Tags
    Base Protections
    EFAE_PROTECT_U.SARMY
    Kills Russian soldiers if they killed a U.S soldier within the zone EFAE_PROTECT_RUSSIANARMY
    Kills U.S soldiers if they killed a russian soldier within the zone EFAE_PROTECT_NVA
    Kills U.S soldiers if they killed a NVA soldier within the zone EFAE_PROTECT_ATTACKERS
    Kills defenders if they killed an attacking soldier within the zone
    Location/Kit Restriction
    EFAE_ANTICAMPER_SNIPER
    Kills a player for sniping within a no-sniper zone (prevent half the freaking team from camping the hill on Port Valdez.. ATTACK YOU F*$%@RS)
    Additional Information
    EFAE - Eye for an Eye, kills the killer

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  6. TrueBalancer

    Description
    This plugin is used to autobalance Teams in BF3 (All modes except SquadDeathMatch)
    There are 3 major parts within TrueBalancer2:

    1. PlayerNumber - Balancer
    - The PN-Balancer try to keep the teams even by playernumber. Eg: 30vs30

    2. Skill- Scrambler
    - The Scrambler trys to even out the teams at roundend by skill. Eg: Even out the teams by SPM, Skill, K/D...

    3. Balancing Guard
    - Balancing Guard trys to keep teams even by skill during the game. He sorts new players to the teams they fit best and doesn't allow players to switch into the other team if they would unbalance the teams by PlayerNumber or Skill. In all Conquest Modes and TDM - Modes Balancing Guard doesn't allow winning team switching.

    IMPORTANT:
    If you are running the plugins in sandboxmode, make sure you have these ports open:
    https://battlelog.battlefield.com 443
    http://battlelog.battlefield.com 80

    This script is in Beta-Phase. Test at your own Risk. Report back please!


    Tutorials and recommended Settings
    TrueBalancer2 Part 1 of 3 - PlayerNumber Balancer
    TrueBalancer2 Part 2 of 3 - SkillScrambler
    TrueBalancer2 Part 3 of 3 - BalancingGuard

    RECOMMENDED SETTINGS


    InGame Commands
    @scramblenow: Will scramble the teams now. Use with caution. This will make players angry.
    @scrambleround: Will scramble the teams at roundend.

    Due to BalacingGuard the standart move/fmove are not working. TB has it's own commands:
    @tb-fmove: Force move a player into the other team.
    @tb-move: Move a player into the other team upon death.

    Settings
    Here is a link for the recommended settings:
    RECOMMENDED SETTINGS


    Things you need to know:

    Minimum values for the settings

    Prefixes for TrueBalance

     

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  7. Map Variables

    This plugin allows you to have different variables set either throughout each individual map or throughout each location in your map rotation.

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  8. Map Voting

    Description
    Allow players the opportunity to vote on the next gametype and map.

    Commands
    Vote Command
    @< Vote Command > #. Cancel Vote Command
    @< Cancel Command >
    Settings
    Miscellaneous
    Vote Command
    The string players on the server need to enter before their vote option (@ #). Cancel Vote Command
    The string players on the server need to enter to cancel their vote. Full Map List
    Select the gametype - map pair to add or remove (will automatically include the gametype and maps in the appropriate lists). Add or Remove Map in List
    Sets or removes gametype - map pair. Gametype List
    List of gametypes you want players to vote on. Conquest Voting Possibilities
    List of Conquest maps you want players to vote on. Rush Voting Possibilities
    List of Rush maps you want players to vote on. Squad Deathmatch Voting Possibilities
    List of Squad Deathmatch maps you want players to vote on. Squad Rush Voting Possibilities
    List of Squad Rush maps you want players to vote on. Vote Duration
    How long (in minutes) each vote should take before final tally. Number of Vote Prompts
    How many prompts should occur during voting. Yell For Votes
    Should the prompt to vote be yelled at the beginning of the voting or every time a prompt occurs? Number of Conquest Rounds
    If Conquest gametype wins, how many rounds each map should play. Number of Rush Rounds
    If Rush gametype wins, how many rounds each map should play. Number of Squad Deathmatch Rounds
    If Squad Deathmatch gametype wins, how many rounds each map should play. Number of Squad Rush Rounds
    If Squad Rush gametype wins, how many rounds each map should play.

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  9. VIP Slot Manager

    Description
    This FREE Plugin gives you full control over reserved VIP Slots, with many customizations and features. It includes a time management control for each VIP player. This means you can add VIP players for a custom time period, whether it be 30 days, or longer. Expired VIP Slots will be disabled automatically. It is also possible to manage multiple Gameservers with one global list of VIPs or alternatively each Gamerserver separately with his own list of VIPs.

    The Plugin supports a web-based interface to manage a single Gameserver or many Gameservers with different VIP players. This means you can add, edit and remove VIP Slots via the admin website. It is highly recommended to use a website for administrative purposes!

    In addition, you can customize any in-game message based on player events. For example, a welcome message for valid VIPs only, such as '%player% your VIP Slot is still valid for: %time%'.
    NEW: The Aggressive Join detection keeps you informed if a NON-VIP player got kicked to make room for a VIP on full server. If the kicked player rejoins, the Plugin sends him a customized message.



    Installation
    IMPORTANT: This Plugin requires a MySQL database with INNODB support.

    1. Disable the Plugin VIP Slot Manager and open the Plugin settings.
    2. In the settings, you will find the section '1. MySQL Details'. There simply enter your MySQL details (host IP, port, database name, username, password).
    3. In the section '2. Main Settings' you can choose your 'Gameserver Type'.
    4. The 'Server Group' is an important setting, for when you have more than one Gameserver. If two or more Gameservers use the same MySQL database, then the VIP players are valid for all these Gameservers with the same 'Gameserver Type' and 'Server Group' ID. You can change the ID in order to manage the VIPs for each Gameserver separately.
    5. Enable the Plugin.
    6. Install the website (optional): In the downloaded ZIP file you find a free website template for this job. Before you upload the website replace your SQL details (SQL Server IP, dbName, dbUser, dbPW) in the 'config.php' file. The default login (user, pw) after the installation: admin , admin

    After the first start the Plugin will connect to the MySQL database to automatically create tables for the Plugin. After the table is created, it will sync all VIP players from the Gameserver to the MySQL database. All the imported VIP players will get a valid VIP Slot for 30 days by the default settings 'Import NEW VIPS from Gameserver to SQL' = yes (30 days first Plugin installation only). This means that all your VIPs will stay within the SQL database and on your Gameserver! This setting will be changed after the first Sync/Import is completed successfully.


    Website (highly recommended)
    The easiest way to manage reserved VIP Slots is a website with access to the MySQL database. In this way you can manage a single Gameserver or many Gameservers with different VIP players. It gives you full control. You can add, edit and remove VIP players via the website. After a few minutes, the Plugin on each Gameserver receives the updated information automatically and will do the rest.

    It is highly recommended to use a website for administrative purposes! You can find a free website template for this purpose within the downloaded ZIP file from this Plugin. It requires a webspace with PHP support and access to the SQL database.

    Sync Settings
    All VIP informations are stored within the SQL database, in addition to the VIP Slot remaining time for each VIP player. The Plugin updates the Gameserver with the valid VIP Slots. Expired VIP Slots will be removed automatically.

    Multiple Gameservers with one global list of VIPs (optional)
    The following Plugin settings are important to provide multiple Gameservers with one global list of VIPs. The settings 'MySQL details', 'Gameserver Type', 'Server Group', 'Import NEW VIPs from Gameserver to SQL', 'Notify Vip Slot Expiered', 'EA GUID Tracking' and 'Aggressive Join Abuse Protection' have to be exactly equal on all Gameservers. In addition, the setting 'Import NEW VIPs from Gameserver to SQL' must be set to 'no (remove)'. In this way the Plugin and the VIP Sync works perfect.

    Server Groups
    Based on the Plugin settings 'Gameserver Type' and 'Server Group' the VIPs are valid for one or more Gameserver. If two Gameservers use the same 'Server Group' ID, then the VIP players are valid for both Gameservers. You can change the 'Server Group' ID in order to manage the VIPs for each Gameserver separately.

    IMPORTANT: If two or more Gameservers use the same 'Server Group' than the Plugin setting 'Import NEW VIPs from Gameserver to SQL' must be set to no (remove).

    Sync Update Interval
    The Sync between the MySQL database and the Gameserver starts automatically every few minutes. You can change the Sync interval in the Plugin setting 'Sync Interval between SQL and Gameserver'.

    Advanced Import
    This feature is important for the first Plugin start and the first Sync to the SQL database. If the Plugin is found on the reserved slot list on the Gameserver a NEW VIP without an entry into the SQL database (or with the VIP status 'inactive / expired'), then you can configurate what the Plugin have to do with this NEW VIP. Based on the Plugin settings 'Import NEW VIPs from Gameserver to SQL' you can select the following options:
     
    yes (first Plugin installation) - The new VIP player will be added to the SQL database. The new VIP will be activated and valid for the next 30 days. This default setting will be changed to 'no (remove)' after the first Sync/Import is completed successfully. This setting is recommended for the first Plugin start and the first Sync to the SQL database. no (ignore) - The new VIP player will stay on the Gameserver without an entry in the SQL. It is not a valid VIP for the Plugin. The player will stay in the reserved slot list on the Gameserver. The player can not use VIP Commands. no (remove) - The new VIP player will be removed from the Gameserver reserved slot list. This default setting is recommended after the Plugin configuration and the first Sync to SQL is completed successfully. This default setting is also required to enable the function 'EA GUID Tracking', the function'Aggressive Join Abuse Protection' or if two or more Gameservers use the same 'Server Group' ID. yes (as inactive) - The new VIP player will be added to the SQL database with the status 'inactive'. The player will be removed from the Gameserver. On the website with access to the SQL database, you can edit the VIP status to activate them. yes (for 7/30/90/365 days) - The new VIP player will be added to the SQL database. The new VIP will be activated and valid for the next 30 days. yes (permanent) - The new VIP player will be added to the SQL database. The new VIP will be activated and valid for the next 7 years (permanent).
    Manual Force Sync
    For a quick one time Sync you can use the 'Force Sync SQL and Gameserver NOW' function in the settings. The proconrulz.ini file will also be updated (if this feature is enabled).


    Notify & In-Game Messages
    You can enable, disable and customize every single in-game message based on chat and player events. OnJoin, OnSpawn and OnChat are trigger events.
    You do not have to use all the available textboxes for messages, leave it blank if you do not need it.
    The 'Replacement Strings' below are available for any message:

    Replacement StringEffect %player% Will be replaced by the playername %time% Will be replaced by the VIP Slot remaining time (for valid VIPs only) %total% Will be replaced by the total number of all valid VIPs on this server %online% Will be replaced by the number of online VIPs
    Sample Message:
    !VIP %player% valid for: %time%
    !VIPs online: %online%/%total%

    In-Game VIP Commands
    These commands are for valid VIP Slot players only. Each command can be enabled or disabled separately. !lead
    take squad leader position !killme
    admin kill without death in scoreboard !switchme
    switch between teams

    In-Game Admin Commands
    These commands are for in-game admins only. Admins need the privilege 'Can Edit Reserved Slots List'. You can enable or disable this function in the setting 'Enable In-Game Admin Commands'.

    IMPORTANT: Requires the <full playername> with case sensitive!
      !addvip <full playername> <days>
    e.g. !addvip SniperBen 30
    e.g. !addvip SniperBen +7 !removevip <full playername>
    e.g. !removevip SniperBen !checkvip <full playername>
    e.g. !checkvip SniperBen !changevip <old playername> <new playername>
    e.g. !changevip SniperBen SniperBenni !addsemivip <full playername>
    e.g. !addsemivip SniperBen
    The command !addvip with 30 days adds and activates a player’s VIP status for the next 30 days. The time period of 30 days is fixed. When you enter this command more than once it has no effect on the time period.

    The command !addvip with +7 days checks the VIP player’s remaining time (e.g. the VIP Slot is still valid for 5 days). Then the Plugin ADDS 7 days to the 'old' time period. For example: old time period (5 days) + new time period (7 days) = total time period (12 days). Now the VIP Slot is valid for 12 days.

    The command !removevip will remove the VIP from the Gameserver. The player will stay in the SQL database and be marked as 'status inactive'.

    The command !addsemivip will add an Semi VIP Slot temporary (valid on current Gameserver till round end / player rejoin). The plugin setting 'Aggressive Join Abuse Protection' must be enabled to handle Semi VIPs.


    Other Plugin Support
    Other Plugins such as ProconRulz/InsaneLimits can use special commands to remove or add a VIP Slot for a custom time period. Other Plugins can send commands as a 'hidden say' within the in-game chat. Other players will not see this in-game message, but the Plugin receives this information. In the Procon PC Tool you can enter the commands to (say, all players). You can enable or disable this function in the setting 'Enable Commands for other Plugins'.


    Commands (hidden admin say)
    /vsm-addvip <full playername> <days>
    e.g. /vsm-addvip SniperBen 30
    e.g. /vsm-addvip SniperBen +7 /vsm-removevip <full playername>
    e.g. /vsm-removevip SniperBen /vsm-changevip <old playername> <new playername>
    e.g. /vsm-changevip SniperBen SniperBenni /vsm-addsemivip <full playername>
    e.g. /vsm-addsemivip SniperBen Sample Code for ProconRulz (perform 5 knife kills = VIP Slot for 7 days):
    On Kill; Damage Melee; if %c% == 5; Say /vsm-addvip %p% +7

    Advanced ProconRulz Support
    The VIP Slot Manager Plugin can store a list of valid VIPs in the proconrulz.ini file. This file stays on your Procon Layer Server (path: CONFIGS/proconrulz_<ip>_<port>.ini). When you read this file within the Plugin ProconRulz (%ini_vipslotmanager_<playername>%) you will get the VIP timestamp in seconds. This means you can check the VIP status without any player protection for weapon rule punishment (kill, kick, ban). You can enable or disable this function within the setting 'On Round End write VIPs in proconrulz.ini file'.

    For a quick one time update to the proconrulz.ini file you can use the 'Force Sync SQL and Gameserver NOW' function in the settings.

    IMPORTANT: Requires Read+Write file permission in the directory /configs/ on your Procon Layer.
      Sample Code for ProconRulz (in-game command '!check' returns the VIP player status):
    On Say; Text !check; if %ini_vipslotmanager_%p%% != 0; Say Yes, you are a VIP
    On Say; Text !check; if %ini_vipslotmanager_%p%% == 0; Say No, you are NOT a VIP
    Aggressive Join for VIPs
    The 'Aggressive Join' is a server setting that allows VIPs to join a full server without waiting. A random NON-VIP player will be kicked to make room for a VIP.

    The Plugin can detect this kind of kick and keeps you informed if a NON-VIP player got kicked to make room for a VIP on full server. If the kicked player rejoins, the Plugin sends him a customized message. You can enable, disable and customize this feature in the setting 'Private Message after NON-VIP got kicked and rejoins'.

    In addition, the Plugin can disable the 'Aggressive Join' close on round end to keep as many players as possible on the server. On the next round it will be enabled automatically. This feature works for the following game modes: ConquestLarge, ConquestSmall, TDM and Chainlink. You can enable or disable this function in the setting 'Temporary disable the Aggressive Join close on round end'.

    Aggressive Join Abuse Protection
    The function 'Aggressive Join Abuse Protection' is also helpful to track each VIP if he rejoins too many times with an 'Aggressive Join Kick' on full server. When a single VIP triggered is his max. threshold (custom setting value) of this kind of rejoins per round, then he can not rejoin again with 'Aggressive Join Kick' privilege till next round. In this case, if he rejoins again in the same round, then he can NOT bypass the server queue. He have to wait like normal players. While he is on the server, the Gameserver and all Plugins handles him as an valid VIP but without 'Aggressive Join Kick' privilege. All other VIPs can still join with 'Aggressive Join Kick' privilege. On next round he can join again with 'Aggressive Join Kick' privilege.


    Advanced Settings

    Debug Level
    1 - Errors will be displayed.
    2 - will also show log entries for added and removed VIP players.
    3 - will also show log entries when a VIP player joins the server.
    4 - will also show log entries when a player uses the in-game commands (e.g. !lead, !killme).
    5 - just for development and testing.

    Manual Force Sync
    For a quick one time Sync you can use the 'Force Sync SQL and Gameserver NOW' function in the settings. The proconrulz.ini file will also be updated (if this feature is enabled).

    Auto Database Cleaner
    This feature reduces the Sync traffic between SQL and Gameserver. It is necessary because the Sync is limited (max. 800 active/expired VIPs for each Server Group). Each Sync includes a list of valid VIPs and expired VIPs. Expired VIPs will get a notify message on the next spawn event. But if the player does not join the server for long time period (60 days by default setting), then this feature will remove him from the Sync in order to reduce the traffic. It changes the player status from 'expired' to 'inactive' and the player will not recives the expired VIP Slot message.

    In addition, old VIPs with the status 'inactive' will be deleted after 365 days automatically.

    VIP EA GUID Tracking
    If a VIP changes his playername then his VIP Slot will be updated to the new playername automatically. After a VIP joins the server, the Plugin links his playername to his EA GUID. If he joins again with a new/changed playername then his VIP Slot will be updated to the new playername for all Server Groups on current Gameserver Type in SQL database (e.g. for all BF4 Groups 1-99). After the VIP Slot has expired the EA GUID will be unlinked.

    IMPORTANT: If the Plugins runs on two or more Gameservers with the same 'Gametype', then the Plugin setting 'Import NEW VIPs from GS to SQL' must be set to 'no (remove)' on ALL Gameservers to use this function. You can enable or disable the tracking function in the setting 'EA GUID Tracking'.


    How to add, edit and remove VIPs
    Website (highly recommended)
    The easiest way to manage reserved VIP Slots is a website with access to the MySQL database. You can find a free website template in the downloaded ZIP file from this Plugin. It is highly recommended that you use it!

    In-Game Admin Commands
    As an in-game admin you can use the commands: !addvip, !checkvip, and !removevip for the current Gameserver (Server Group).

    Procon PC Tool
    In the Plugin settings you can use the 'Mini Manager - Print VIP list' to display the current VIP list with players remaining time on your Procon PC Tool Chat tab.
    You can also use the commands from the 'Other Plugin Support' function to add and remove VIP Slots. You can enter the commands in the Procon PC Tool chat as a hidden admin say (e.g. /vsm-addvip SniperBen +7). Nobody will see the commands within the in-game chat.


    FAQ

    Do I need a new MySQL database?
    No. For this Plugin, it is NOT necessary to create a new MySQL database. You can use the same MySQL database as the Statslogger Plugin.

    How to manage two or more Gameservers?
    With the web-based interface you can manage a single Gameserver or many Gameservers with different VIP players. If two Gameservers use the same 'Server Group' ID (Plugin settings) (Plugin settings), then the VIP players are valid for both Gameservers. You can change the 'Server Group' ID in order to manage the VIPs for each Gameserver separately. If two or more Gameservers use the same 'Server Group' on the same SQL database then the Plugin setting 'Import NEW VIPs from Gameserver to SQL' must be set to no (remove).

    AdKats Plugin
    It is possible to use the VIP Slot Manager and the AdKats Plugin. Please make sure that Adkats do not manage the reserved VIP Slots. This is disabled by default. Open the settings from Adkats Plugin, then go to Adkats > A16. Orchestration Settings > Feed Server Reserved Slots > False

    What is the diffenence between 'add 30' and 'add +30'?
    The command with + checks the VIP players remaining time (e.g. the VIP Slot is still valid for 5 days), then the Plugin ADDS 30 days to the 'old' time period. For example: old time period (5 days) + new time period (30 days) = total time period (35 days). Now the VIP Slot is valid for 35 days.

    How to clean up the database?
    With the website you can clean up the database to remove all old VIPs with the status 'inactive'. Go to the website. Type 'inactive' into the search box. Mark all entires (click on the first VIP and then hold down the SHIFT key on your keyboard and click on the last VIP). Then open the drop down menu and click on 'DELETE' to delete the marked entries.

    Witch Games are supported?
    The Plugin works fine for BF3, BF4, BFH and BFBC2. The support for other Games are still not tested.

    Where can I find updates and support?
    Updates and support will be handled through the procon thread or on github website:
    https://github.com/procon-plugin/vip-slot-manager

    3 downloads

       (0 reviews)

    0 comments

    Submitted

  10. PRoCon Simple Playertracker

    Description

    This plugin is used to log Player chat and other general Playerinfos like GUID's .
    This inludes: Chat, Playername, PBGUID, EAGUID, IP, Country, ClanTag
    Data is written at the end of a Round

    Requirements
    It reqiues the use of a MySQL database with INNODB engine that allows remote connections.(MYSQL Version 5.1.x or higher is recommendend!!!)
    You will also need to download the MySQL ODBC 5.1 Driver(the latest is 5.1.7(24.08.2010)), and enable ODBC connections in the procon options.
    The Plugin will create the tables by itself.
    Pls Give FEEDBACK !!!

    Installation
    Download and install this plugin Download and install the MYSQL ODBC Connector 5.1 Driver (the latest is 5.1.7(24.08.2010)) Setup your Database this means create a database and the user for it. I highly recommend NOT to use your root user. Just create a user with all rights for your newly created database I recommend MySQL 5.1.x or greater (5.0.x should work too) Important: Your database need INNODB Support Start Procon Go to Tools --> Options --> Plugins --> Enter you databaseserver under outgoing Connections and allow all outgoing connections Restart Procon Enter your settings into Plugin Settings and THEN enable the plugin Now the plugin should work if not request help in the Forum
    Things you have to know:
    Now you can have more than one server per database if you use the tableSuffix feature, if you dont want to use it keep this field blank.

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  11. PRoCon Voteban and Votekick

    Description
    This plugin allows Players to start a Vote against an other Player.
    You are to choose which vote types are activ, also you can set parameter like vote duration or how many player needed to start a vote.
    If a vote is active no other Vote can be started.
    When the vote ends the desired action will be execute if enough player vote for it.
    ATM the voteban uses Namebans only this will maybe change in later version or on request.
    All Players will be informed about the Vote status.

    Requirements
    Adjust the pluginsetting for your needs and Serversize.
    Pls Give FEEDBACK !!!

    Installation
    Download and install this plugin

    Ingame Commands
    [@,#,!]voteban PlayerName [Reason] Starts a Voteban. [@,#,!]votekick PlayerName [Reason] Starts a Votekick. [@,#,!]vote [yes,no] To vote for or against a Player. [@,#,!]vote [cancel] To cancel a you started (Only the player who started the vote can cancel his vote).
    Known issues:
    -none yet but i expect some 😉

    Plans for future release:
    Feature Requests 😉 Changelog:
    1.0.0.1
    Added Whitelist

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  12. Zombie Mode

    Description
    Zombie Mode is a ProCon 1.0 plugin that turns Team Deathmatch into the Infected or Zombie variant play.

    NOTE: the game server must be run in unranked mode (BF3: vars.ranked false, BF4 or BFHL: vars.serverType Unranked). Zombie Mode will not work on a ranked server.

    When there are a minimum number of players spawned, all of the players are moved to the human team (US), except for one zombie (RU). With default settings, Zombies can use knife/defib/repair tool only for weapons and Humans can use any weapon except explosives (grenades, C4, Claymores) or missiles; the allowed/forbidden weapon settings are configurable. Zombies are hard to kill. Every time a zombie kills a human, the human becomes infected and is moved to the zombie team. Humans win by killing a minimum number of zombies (configurable) or when all the zombies leave the server. Zombies win by infecting all the humans or when all the humans leave the server.

    The maximum number of players is half your server slots, so if you have a 64-slot server, you can have a max of 32 players.

    The plugin is driven by players spawning. Until a minimum number of individual players spawns, the match won't start. See Minimum Zombies and Minimum Humans below.

    Recommended BF3 server settings are here: https://github.com/m4xxd3v/BF3ZombieMode/wiki/Recommended-server-settings

    Settings
    There are a large number of configurable setttings, divided into sections.


    Admin Settings
    Zombie Mode Enabled: On/Off, default is On.

    Command Prefix: Chat text that represents an in-game command, default is !zombie. May be set to a single character, for example @, so that instead of the rules command being !zombie rules, the command would just be @rules.

    Announce Display Length: Time in seconds that announcements are shown as yells, default is 10.

    Warning Display Length: Time in seconds that warnings are shown as yells, default is 15.

    Human Max Idle Seconds: Time in seconds that a human is allowed to be idle (no spawns and no kills/deaths) before being kicked. This idle time applies only when a match is in progress. Since zombies can't win unless they can kill humans, the match can stall if a human remains idle and never spawns. The idle time for humans should therefore be relatively short. The default value is 180 seconds, or 3 minutes.

    Max Idle Seconds: Time in seconds that any player is allowed to be idle (no spawns and no kills/deaths) before being kicked, regardless of whether a match is running or not, or whether spawned or not. This idle time applies as long as Zombie Mode is enabled (On). The default value is 600 seconds, or 10 minutes.

    Warns Before Kick For Rules Violations: Number of warnings given before a player is kicked for violating the Zombie Mode rules, particularly for using a forbidden weapon type. The default value is 1.

    Temp Ban Instead Of Kick: On/Off, default is Off. If On, a rules violation results in a temporary ban for Temp Ban Seconds. If Off, a rules violation results in a kick. In both cases, the punishment happens after Warns Before Kick For Rules Violations warnings have been issued to the violator.

    Temp Ban Seconds: Time in seconds that a player is temporarily banned if Temp Ban Instead Of Kick is On. The default value is 3600 seconds, or 1 hour.

    Votes Needed To Kick: Number of votes needed to kick a player with the !zombie votekick command or kill a player with the !zombie votekill command. The default value is 3.

    Debug Level: A number that represents the amount of debug logging that is sent to the plugin.log file in PRoCon. The higher the number, the more spam is logged. The default value is 2. Note: if you have a problem using the plugin, set your Debug Level to 5 and save the plugin.log for posting to phogue.net.

    Rule List: A table of rules, one chat/yell line per rule, displayed when players type the !zombie rules in-game command. The default set of rules reflect the default settings, such as humans not using explosives. Useful for when you change the default weapon limitations for humans and zombies, you can tell players what weapons are allowed or forbidden. Also useful if you want to add more rules, like kicking players for using MAV.

    Admin Users: A table of soldier names that will be permitted to use in-game admin commands (see below). The default value is PapaCharlieNiner.

    Test Weapon: For debugging the plugin only, type in the name of a weapon and test if Humans or Zombies are allowed to use (ON) or not use (off) that weapon.


    Game Settings
    Max Players: Any players that try to join above this number will be kicked immediately. Make sure this number is equal to or less than half of your maximum slot count for your game server. For example, if you have a 48 slot server, set the maximum no higher than 24. This is a limitation of BF3 game servers, you can only use half your slots for this mode. The default value is 32.

    Minimum Zombies: The number of players that will start a match as zombies. The default value is 1.

    Minimum Humans: The number of players that will start a match as humans. The default value is 3. Note: the sum of Minimum Zombies and Minimum Humans (default: 4) is the minimum number of players needed to start a match. Until that minimum number spawns into the round, the Zombie Mode will wait and normal Team Deathmatch rules will apply.

    Zombie Kill Limit Enabled: On/Off, default is On. If On, Humans must kill the number of zombies specified in Goal For Humans in order to win. If Off, the last human left standing is the winner.

    Deaths Needed To Be Infected: The number of times a human must be killed by a zombie before the human becomes infected and is forced to switch to the zombie team. The default value is 1.

    Infect Suicides: On/Off, default is Off. If On, a human that suicides becomes a zombie. If Off, the human stays human but still dies. Neither setting changes suicides for zombies, they are always non-scoring.

    New Players Join Humans: On/Off, default is On. If On, any new players that join the server will be force moved to the human team. If Off, any new players that join the server will be force moved to the zombie team.

    Rematch Enabled: On/Off, default is On. If On, when a team wins and the match is over, a new match will be started after a short countdown during the same map round/level. Matches Before Next Map will be played before the next map is loaded. When Off, the current map round/level will be ended, the winning team will be declared the winner of the whole round and the next map round/level will be loaded and started. Turning this On makes matches happen quicker and back-to-back on the same map, while turning this Off takes longer between matches, but lets your players try out all the maps in your rotation.

    Matches Before Next Map: The default value is 3. If Rematch Enabled is On, this is the number of matches that are played in the same map round/level before the next map is loaded. This assumes the map list is set up to only play eacy map level 1 round.


    Goal For Humans
    If Zombie Kill Limit Enabled is On, humans musts kill the specified number of zombies in order to win. The kill goal is adaptive to the number of players in the match, specified in intervals of four, as follows:

    Kills If 8 Or Less Players: the default value is 12.

    Kills If 12 To 9 Players: the default value is 18.

    Kills If 16 To 13 Players: the default value is 24.

    Kills If 20 To 17 Players: the default value is 30.

    Kills If 24 To 21 Players: the default value is 35.

    Kills If 28 To 25 Players: the default value is 40.

    Kills If 32 To 29 Players: the default value is 50.


    Human Damage Percentage
    At the start of a match, when there is only one or a very few zombies, zombies have to be very tough and hard to kill or else they will never get close to a human to infect them. This is implemented with vars.bulletDamage. The values of the following settings specify the vars.bulletDamage depending on the number of zombies that the humans face. The lower the numbers, the harder the zombies are to kill.

    Against 1 Or 2 Zombies: the default value is 5. When humans outnumber zombies 3-to-1 or more (e.g., 18 vs 1).

    Against A Few Zombies: the default value is 15. When humans outnumber zombies between 3-to-1 and 3-to-2 (e.g., 12 vs 7).

    Against Equal Numbers: the default value is 30. When humans and zombies are roughly equal in number, betwee 3-to-2 and 2-to-3 (e.g., 8 vs 11).

    Against Many Zombies: the default value is 50. When zombies outnumber humans between 3-to-2 and 4-to-1 (e.g., 5 vs 14).

    Against Countless Zombies: the default value is 100. When zombies outnumber humans 4-to-1 or more (e.g., 2 vs 17).


    Zombie Weapons
    This is a lists of weapon types zombies are allowed to use. Weapons that are On are allowed, weapons that are Off are not allowed and will result in warnings and a kick if a zombie player uses them. The default settings allow knife, melee, defib and repair tool and do not allow anything else.

    Human Weapons
    This is a lists of weapon types humans are allowed to use. Weapons that are On are allowed, weapons that are Off are not allowed and will result in warnings and a kick if a human player uses them. The default settings are all guns allowed and do not allow explosives (grenades, C4, claymore, M320 noob tube, etc.) or missiles (RPG, SMAW).

    Commands
    These are in-game commands for managing players and the mode. Some are available to all players, some are for admins only (see Admin Users in Settings). For all of the following descriptions, the default Command Prefix of !zombie is assumed. If you set a different prefix, substitute your prefix into the following.


    Commands for all players

    !zombie help: Shows list of commands available to the player.

    !zombie idle: Shows how long the player typing the command has been idle (no spawns and no deaths/kills) and whether or not the player is spawned into the round.

    !zombie rules: Scrolls all of the Zombie Mode rules to the player.

    !zombie status: Shows the status of the match to the player, for example, if the mode is waiting for more players to join, or if it is Idle (waiting for a player to spawn so that it can reset), counting down to the next match, etc. If a match is in progress (Playing), it also shows some statistics for the match, for example:

    HUMANS: N=4,K=23,G=30
    ZOMBIES: N=16,D=100

    Where N is the number of players on that team, K is the number of zombies the humans have killed, G is the number of zombies the humans need to kill to win, and D is the current bullet damage. If there are votekicks or votekills against you, the current vote counts will also be shown.


    !zombie warn name reason: Sends a warning yell to the player with the specified name. The reason is one or more words. For example:

    !zombie warn PapaCharlie9 Quit glitching u noob!

    will yell the message 'Quit glitching u noob!' to PapaCharlie9.

    !zombie votekick name: Adds a vote to kick the player with the specified name. Only one vote is counted per voter. Once Votes Needed To Kick votes have been reached, the player is kicked. Votes are cleared after the player is kicked.

    !zombie votekill name: Adds a vote to kill the player with the specified name. Only one vote is counted per voter. Once Votes Needed To Kick votes have been reached, the player is killed. The kill does not count for scoring or infection. Votes are cleared after the player is killed. This is useful when humans camp in a spot unreachable by zombies without using an illegal weapon. The zombies can vote to kill the human, which forces him to spawn in a random location.


    Commands for Admins only

    !zombie force: Force a match to start, even if there are not enough players. Useful if players aren't spawning fast enough to get a match started or if the plugin gets into a confused state (please report a bug so we can fix it).

    !zombie heal name: Kills the player with the specified name and if they are on the zombie team, force moves them to the human team. Useful for correting mistakes that the plugin might make (please report a bug so we can fix it).

    !zombie infect name: Kills the player with the specified name and if they are on the human team, force moves them to the zombie team. Useful for dealing with human glitchers or idlers.

    !zombie kick name reason: Kicks the player with the specified name. The reason is one or more words. For example:

    !zombie kick PapaCharlie9 Too much glitching!

    will kick PapaCharlie9 for 'Too much glitching!'. Useful to get rid of cheaters.

    !zombie kill name: Kills the player with the specified name. Useful to force a glitcher to respawn or a player ignoring warnings to pay more attention.

    !zombie mode on/off: Changes the Zombie Mode Enabled setting. Useful if you want to switch a normal TDM round to Zombie Mode or vice versa.

    !zombie next: Ends the current map round/level and loads the next map round/level. Useful to try a new map if you have Rematch Enabled set to On.

    !zombie rematch on/off: Changes the Rematch Enabled setting

    !zombie restart: Restarts the current map round/level. Useful if the tickets/kills for TDM are getting close to the maximum to end a normal TDM round, which might happen in the middle of a quick rematch.

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  13. Vote Ban

    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/kick the player who has a Vote Ban/Kick 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. NOTE: These commands may be redefined by you in the plugin settings.

    Settings
    Vote Ban
    Enable Vote Ban?
    Allows you to enable or disable the ability for players to Vote Ban. Vote Ban Player Count Threshold
    The minimum number of players that must be on the server for Vote Banning to be enabled. 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.)
    Vote Kick
    Enable Vote Kick?
    Allows you to enable or disable the ability for players to Vote Kick. Vote Kick Player Count Threshold
    The minimum number of players that must be on the server for Vote Kicking to be enabled. 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.
    Hack Cry Responder
    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.
    Whitelist

    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. Clan Tags
    Allows you to add Clan Tags to protect the wearer of any tag from being Vote Banned/Kicked. 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.
    In-Game Commands
    These allow you to customize the in-game commands for this plugin.
    Vote Ban Commands
    The commands used to initiate a Vote Ban. Vote Kick Commands
    The commands used to initiate a Vote Kick. Yes Commands
    The commands used to vote yes to the vote in progress. (Also used to confirm a suggested player name.) No Commands
    The commands used to vote no to the vote in progress. (Also used to deny a suggested player name.) Cancel Vote Commands
    The commands used to cancel the vote in progress.
    In-Game Messages
    This allows you to customize all the messages that this plugin sends to the server.
    Reset Messages?
    Use this to retrieve the default list of messages. This is useful when you may have made a mistake and messages start to not show up. Message List
    The list containing all the messages that this plugin sends to the server. Be careful not to delete any lines otherwise things will go wrong!

    5 downloads

       (0 reviews)

    0 comments

    Submitted

  14. Server Settings Change On Map

    Description
    This plugin allows you to set different game modes and custom variables throughout your map rotation. You have the option of Normal Mode, Infantry Only Mode, Hardcore Mode, and Custom Settings mode.

    Settings
    Default Variables (Server Startup Variables) - Set each of these to match whatever your server starts up with using the Startup.txt file. Each one starts with their default values in their fields. This is used to change the unspecified variables back to your server's startup values. For example, when you leave a custom variable field blank for one map, it won't use the same value that was defined for the previous map and will instead revert it back to default per this Default Variables list.

    Get/Refresh Your Map List? - Use this to load each of your maps from your map list into a variable to assign a game mode to. (Plugin must be enabled for this to work)
    Set your maps under Your Map Rotation to whichever game settings you would like to be played for that map.
     

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  15. Remote Banlist

    Description
    Remote Banlist is a plugin designed to simplify the work of managing large banlists across multiple servers.
    Making use of a MySQL-Datebase, the plugin stores all its ban-information independent from the BF3-Server and it's banlists, also providing some more fields to add information like 'Banning Admin', 'Server Name', or some extra 'Comments'.
    Bans can either be viewed or edited in the database directly, or in combination with leibhold's WebAdmin-Page, which also implements the RemoteBanlist-Plugin.
    Please be aware: this is still an early release, so there might be some bugs within the code. Please report back if you encounter any errors!

    Settings
    MySQL Host
    Hostname or IP of your MySQL-Server MySQL Port
    Port of your MySQL-Server MySQL Username
    Username to identify with your MySQL-Server MySQL Password
    Password to identify with your MySQL-Server MySQL Database
    Name of the database to use Keep server-banlist empty?
    If activated, the plugin issues a 'banList.clear' and 'banList.save' command after adding all bans in the list, thus keeping the local banlists clean. NOTE: DO NOT USE WITH BANLISTS CONTAINING MORE THAN 100 ENTRIES! (see 'Known bugs'). Print kicked players to pluginconsole?
    Prints a message to the pluginconsole, stating that a specific player has been found when kicking him. Debug levele
    0 is no debug, 1 = min 9 = verbose messages to plugin-console Ingame-Bancommand (without @, #, !)
    NOT FUNCTIONAL - The ingame-command you are using for banning people. NOT IN USE Enter this without any prefixes (like '@', '#', '!', '/', etc).
    Known Bugs
    'Keep server-banlist empty?' doesn't work properly with banlists > 100 entries
    Remote Banlist currently just uses the standard 'banList.list' command, which shows the first 100 bans. If there are more than that in the gameserver's banlist (NOT the remote banlist), the other ones will get lost. Working on a fix. PunkBuster-Bans don't get added to the remote banlist automatically
    The automatic ban-add mechanism currently supports adding PB-Bans to your MySQL-Database automatically.

    5 downloads

       (0 reviews)

    0 comments

    Submitted

  16. Admin InGame Map Commands

    Description
    Provides in-game commands for maplist manipulations. Those can be to define the next map to be run or to query available maps for the running gametype. It interacts with BasicInGameInfo & InGameAdmin.

    How it works

    Being enabled the plugin will get a list of all available maps for all supported gamemodes in the running mod (vanilla BFBC2 or BFBC2-Vietnam). Next it will check which is the current map and the gamemode. With this information it provides the list of available maps. Maps which should be selected are checked against maps in the running gamemode. If a selection is confirmed the plugin checks if that map is already in the current maplist rotation. On a hit the nextLevelIndex is set to that map in the rotation. If the selected map is not in the rotation it is instered into the maplist rotation and the nextLevelIndex is set to that map. The placement is done regarding the setting (add map method). A map is inserted with two rounds to play.

    You need to issue the InGameAdmin 'Next Map' command (nextlevel by default) to forward to the selected map.

    Commands
    @map usable by all players will list all available maps in the running gamemode @map [MapName] [optional: fast] only usable by admins (Procon account holder) with CanUseMapFunctions privileges [MapName] can be the level file name (Levels/mp_001sr) or the friendly name (Panama Canal). A short form can be used. [optional: fast] adding 'fast' to the command while pointing/searching a map filename will directly load the map.
    Note: You must select a map by the filename to use fast-option! sets the selected and confirmed map as the next map @rotation usable by all players will list all maps in the current mapList/Rotation with id-nr, name and filename. @shownextmap usable by all players will show which map will be next in the rotation. If the nextmap is another round the output will show that. @gamemode usable by all players will list all available gamemode @gamemode [GameMode] [optional: mapFileName / all] [optional: fast] [optional: override] only usable by admins (Procon account holder) with CanUseMapFunctions privileges [GameMode] has to be one of the keywords just like the server wants it for admin.setPlaylist command.
    (CONQUEST/RUSH/SQRUSH/SQDM) [mapFileName] can be the keyword 'all' to add all maps/levels of the selected gamemode to the new rotation.
    To add a specific map use the correct filename incl. 'Levels/' path. [fast] use this keyword to change to the new gamemode and map directly. [override] use this keyword to override the gamemode maxPlayer count.
    (CONQUEST & RUSH up to 32 players, SQDM up to 16 players, SQRUSH up to 8 players) sets the selected and confirmed gamemode if the actual player count fits the selection clears the maplist, adds all available maps for the selected gamemode and forwards to the first map in the selected gamemode.
    Settings
    Miscellaneous
    Map command
    Defines the map command keyword. MapList command
    Defines the command to prints the current mapList/Rotation. Show next map command
    Defines the command to show the next map to be played. Gamemode command
    Defines the gamemode command keyword. Confirm command
    Defines the keyword to confirm selections. Add map method
    Sets if a selected map which is not in the actual rotation should be inserted after the running map or to the end of the rotation. Save maplist
    Select Yes to save all changes to the maplist to the maplist file and make it reboot save. This will also save a changed playlist/gamemode. Restart on zero
    Restarts the current map as playercount hits zero. Console output
    Prints status informations to the plugin console. Debug output
    Prints status and debug information to the plugin console.
    Credits
    Phogue for Procon Ploho League Controls, parts of it are used in here other plugin authors for all the plugins and code insperations Procon users for your ideas, comments and feedback

    5 downloads

       (0 reviews)

    0 comments

    Submitted

  17. BFBC2 Chat, GUID, Stats and Map Logger

    Description
    This plugin is used to log player chat, player GUID's und player Stats and Weaponstats and Mapstats.
    This inludes: Chat, PBGUID, EAGUID, IP, Stats, Weaponstats, Dogtags, Killstreaks, Country, ClanTag to be continued.. 😉

    Requirements
    It reqiues the use of a MySQL database with INNODB engine that allows remote connections.(MYSQL Version 5.1.x or higher is recommendend!!!)

    Also you should give INNODB some more Ram because the plugin mainly uses this engine if you need help ask me

    You will also need to download the MySQL ODBC 5.1 Driver(the latest is 5.1.7(24.08.2010)), and enable ODBC connections in the procon options.

    The Plugin will create the tables by itself.
    Pls Give FEEDBACK !!!

    Installation
    Download and install this plugin Download and install the MYSQL ODBC Connector 5.1 Driver (the latest is 5.1.7(24.08.2010)) Setup your Database this means create a database and the user for it. I highly recommend NOT to use your root user. Just create a user with all rights for your newly created database I recommend MySQL 5.1.x or greater (5.0.x should work too) Important: Your database need INNODB Support Start Procon Go to Tools --> Options --> Plugins --> Enter you databaseserver under outgoing Connections and allow all outgoing connections Restart Procon Select the GameMod (BC2 / VIETNAM / Shared) Default is BC2 or let the plugin detect the GameMod Enter your settings into Plugin Settings and THEN enable the plugin Now the plugin should work if not request help in the Forum
    Things you have to know:
    You need to drop your old tables or use the mysql script in the zip file
    Now you can have more than one server per database if you use the tableSuffix feature, if you dont want to use it keep this field blank.
    You can add additional Names for weapons in the Pluginsettings But only use UpperCase, no Spaces and comma to seperate the words.
    Example: 40MMGL{NOOBTUBE} --> 40MMGL{NOOBTUBE,GL,TUBE}
    Dont change the first word!!! only these in brackets if there are no brackets you can add them.

    Ingame Commands
    [@,#,!]stats
    Tells the Player their own Serverstats [@,#,!]rank
    Tells the Player their own Serverstats [@,#,!]session
    Tells the Player their own Sessiondata [@,#,!]top10
    Tells the Player the Top10 players of the server [@,#,!]stats WeaponName
    Tells the Player their own Weaponstats for the specific Weapon [@,#,!]rank WeaponName
    Privately Tells the Player their own Weaponstats for the specific Weapon [@,#,!]top10 WeaponName
    Privately Tells the Player the Top10 Player for the specific Weapon of the server [@,#,!]dogtags WeaponName
    Privately Tells the Player his Dogtagstats
    Replacement String for Playerstats

    Replacement String for Weaponstats

    Replacement String for PlayerSession

    NOTE:
    Tracked stats are: Kills, Headshots, Deaths, All Weapons, TKs, Suicides, Score, Playtime, Rounds, MapStats, Dogtags
    The Rank is created dynamical from Query in my opinion much better than write it back to database.
    The Stats are written to the Database at the end of the round
    Cheaterprotection uses Stats from BFBCS only!!!
    Cheaterprotection kicks in if both values are over the limit


    Known issues:
    If you reason is too long the Ban wont work(Eaguid Ban, Nameban)
    Avoid using Special characters in the Reason Messages

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  18. Ban Manager

    Description
    Banlist Manager is a plugin based on MorpheusX(AUT) CRemoteBanlist V 1.0.0.11
    (Website: http://www.phogue.net/forumvb/member.php?565-MorpheusX(AUT)).
    Making use of a MySQL-Datebase, the plugin stores all its ban-information independent from the BF3-Server and it's banlists, also providing some more fields to add information like 'Banning Admin' and 'Server Name'.
    Bans can either be viewed or edited in the database directly. It implements its own Ingame Admin Commands. Please make use of it, if you want banning admin information in the database, bans taken via Procon can't provide the banning admin.
    Please be aware: this is still an early release, so there might be some bugs within the code. Please report back if you encounter any errors!

    Settings
    MySQL Host
    Hostname or IP of your MySQL-Server MySQL Port
    Port of your MySQL-Server MySQL Username
    Username to identify with your MySQL-Server MySQL Password
    Password to identify with your MySQL-Server MySQL Database
    Name of the database to use Keep server-banlist empty?
    If activated, the plugin issues a 'banList.clear' and 'banList.save' command after adding all bans in the list, thus keeping the local banlists clean.
    NOTE: ONLY DEACTIVATE FOR TESTPURPOSE! Test Run?
    If activated, the plugin will only print a kick Notification to the plugin console, but will not kick the player who are in the banlist Keep server-PBbanlist empty?
    If activated, PBbanlist will be cleared after adding the bans to the database
    Note: Plugin will not add all PBBans if deactivated and there are more than about 100 Entries. ONLY DEACTIVATE FOR TESTPURPOSE! disable Punkbuster support?
    If set to yes, no Punkbuster Bans/Tempbans will be added to the database, but they are still working! Print kicked players to pluginconsole?
    Prints a message to the pluginconsole, stating that a specific player has been found when kicking him. Server Group?
    If 0 all bans will forced to every Gameserver, else only to this servergroup Debug level
    0 is no debug, 1 = min 9 = verbose messages to plugin-console Enable Ingame Commands
    TO GET ALL FEATURES OF THIS PLUGIN FORCE ALL BANS WITH THE INGAME COMMANDS OF THIS PLUGIN e.g. BANNING ADMIN
    SYNTAXE: [command] [substring of the player] [optional: reason] Global Bancommand
    If you uses more servergroups and wants to do a ban over all servers then use this command, it will set the servergroup to 0 for this ban Unban Command
    Remove a ban from the database if the ban is global or corresponding to this servergroup. You need the excat name to unban. If a banentry is without the name in the database it can't be removed with this command
    SYNTAXE: [command] [exact playername]

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  19. xVoteWeapon

    Description
    Main
    * Everyone playing on the server can vote which weapon is allowed for use.
    * Only one weapon type (+ knife) is allowed each round, the weapon vote from the previous match decides it.
    * Players who break the rules are killed, then kicked, then TBanned.
    * If a Melee weapon e.g. repair tool is chosen, the knife may not be used.
    * If nobody votes during a match, the weapon for the next match is chosen randomly from the list below.
    * If a player has not unlocked the current set weapon they must use the knife, no exceptions.
    * Players must not use underslung weapons. Thanks to DICE the auto-admin thinks they don't exist, they will get the players killed.
    * When a Melee weapon is chosen (e.g. Defib, RepairTool), you cannot use the knife (Tags or Slash Kills).

    Suggestions
    * Use a low ticket count to let everyone have a chance at getting their favorite weapons played. Rounds are to be quick and dirty.

    Settings
    * 'Delay Before Kill' - The amount of time(ms) after an infraction is committed that the player is slain. This gives them time to read the yell banner. Default is 2000ms.
    * 'Infractions Before Kick' - The number of infractions at which the player is kicked from the server. Default is 3.
    * 'Infractions Before TBan' - The number of infractions at which the player is Temp Banned from the server for 2 Hours. Default is 4.
    * 'Protect 'reserved slots' players from Kick or Kill' - Whether 'reserved slot' players will be protected from infraction punishment. Default is No.
    * 'Server Name Template' - This variable is a template for the server name. Add %W% in the server name where you want the weapon description to be.

    Future Settings
    * 'Disallowed Weapons' - List of Weapons that will show up as 'Disallowed Weapon' or 'Invalid Weapon Code' and cannot be used as a vote.

    Current In-Game player Commands
    * 'vote WEAPONCODE' : Places your vote for the next weapon, where WEAPONCODE is a code from the list below, and WEAPONCODE is NOT case sensitive.
    It will start the vote system if not started already, and will tell you if the 'next weapon' was altered by your vote.
    * 'currentweapon' : Tells you the current allowed weapon.
    * 'nextweapon' : Tells you the current decided weapon for the next round.
    * 'killme' : If you spawn with the wrong weapon on accident, type this command and you will be killed but your death count will not be incremented.
    * 'weaponlist' : Sends 5 random weapons with their codes to the player's chat list.

    Future In-Game player Commands
    * 'skipweapon' : 10 players type this command and the current weapon is skipped, the next round is then started, all kills/deaths from the previous round remain.

    Future In-Game admin Commands
    * 'runnextround' : Just like skipweapon for players, but when run by an in-game admin requires no votes.

    Weapon Codes
    | 870 Combat Shotgun | 870 |
    | AEK-971 Assault Rifle | AEK |
    | AKS-74u Assault Rifle | AKS |
    | AN-94 Abakan Assault Rifle | AN94 |
    | AS Val Supressed Assault Rifle | ASVAL |
    | DAO-12 Striker Shotgun | DAO12 |
    | Defibrillator | DEFIB |
    | F2000 Assault Rifle | F2000 |
    | FAMAS Assault Rifle | FAMAS |
    | Glock 18 Pistol | G18 |
    | MP5 Assault Rifle | MP5 |
    | Jackhammer/MK3A1 Shotgun | MK3A1 |
    | JNG90 Sniper Rifle | JNG90 |
    | Knife | KNIFE |
    | L96A1 Sniper Rifle | L96 |
    | LSAT Light Machine Gun | LSAT |
    | M416 | M416 |
    | M417 Sniper Rifle | M417 |
    | M1014 Semi-automatic Shotgun | M1014 |
    | M16A4 Assault Rifle | M16A4 |
    | M16A3 Assault Rifle | M16A3 |
    | WWII M1911 .45 Pistol | M1911 |
    | M240B Machine Gun | M240B |
    | M249 SAW | M249 |
    | M26 MASS Shotgun | MASS |
    | M27 IAR | M27IAR |
    | M320 Grenade luncher | M320 |
    | M39 Sniper Rifle | M39 |
    | M40A5 Sniper Rifle | M40A5 |
    | M4A1 Carbine | M4A1 |
    | M60 LMG | M60 |
    | M67 Grenade | M67 |
    | M9 Pistol | M9 |
    | Baretta M93R | 93R |
    | MG36 | MG36 |
    | MK11 Mod 0 Sniper Rifle | MK11 |
    | Barrett M98B Sniper Rifle | M98B |
    | MP7 Machine Gun | MP7 |
    | PKP Pecheneg Machine Gun | PKP |
    | PP-19 Bison SubMachine Gun | PP19 |
    | PP-2000 SubMachine Gun | PP2000 |
    | QBB-95 Light Machine Gun | QBB95 |
    | QBU-88 Sniper Rifle | QBU88 |
    | QBZ-95 Assault Rifle | QBZ95 |
    | Repair Tool | REPAIRTOOL |
    | RPG/SMAW | RPG |
    | RPK-74M Light Machine Gun | RPK74M |
    | SCAR-L Assault Rifle | SCARL |
    | Saiga 20K Shotgun | SAIGA |
    | Simonow SKS-45 Rifle | SKS |
    | SPAS-12 Shotgun | SPAS12 |
    | SV98 Snayperskaya | SV98 |
    | SVD Sniper Rifle | SVD |
    | Aug A3 Assault Rifle | AUG |
    | Taurus .44 Magnum revolver | MAGNUM |
    | Type88 Machine Gun | TYPE88 |
    | USAS-12 automatic Shotgun | USAS12 |
    | A-91 Assault Rifle | A91 |
    | AK-74 Assault Rifle | AK74 |
    | G36C Assault Rifle | G36C |
    | G3A3 Battle Rifle | G3A3 |
    | C4 Explosive | C4 |
    | Claymore mine | CLAYMORE |
    | KH2002 Assault Rifle | KH2002 |
    | Magpul Personal Defense Rifle | MAGPUL |
    | MP412 REX Revolver | REX |
    | MP-443 Grach Pistol | MP443 |
    | P90 Sub Machine Gun | P90 |
    | SCAR-H Assault Rifle | SCARH |
    | UMP-45 SubMachine Gun | UMP45 |
    | L85A2/SA80 Assault Rifle | L85A2 |
    | ACW-R Assault Rifle | ACWR |
    | L86A2 Light Machine Gun | L86A2 |
    | M5K Submachine Gun | M5K |
    | MTAR-21 Assault Rifle | MTAR |
    | Tactical Crossbow | XBOW |
    | Robot Kill (MAV, EOD, MORTAR) | ROBOT |

    Development
    Started by ColColonCleaner for ADK Gamers on Oct. 31, 2012

    Changelog
    0.1 (31-OCT-2012)
    - initial version
    0.2 (31-OCT-2012)
    - initial updates and bug fixes
    0.3 (1-NOV-2012)
    Weapon Codes:
    Glock18 Pistol code is now 'G18'
    Repair Tool code is now 'REPAIRTOOL'
    Grenade code is now 'M67'
    Bug Fixes and Enhancements:
    Weapon codes are no longer case sensitive.
    ASVal and RepairTool bugs fixed.
    Implemented Kick after 3 infractions and TBan for 2 hours after 4 infractions.
    Plugin now tells players what the current weapon is on join, before spawning.
    Now players may start a vote just by saying 'vote WEAPONCODE', no need to say 'voteweapon' first, although that can still be done.
    Still to fix:
    Find other bugs and fix them.
    0.4 (2-NOV-2012)
    Weapon Codes:
    No Updates
    Bug Fixes and Enhancements:
    Bugs found with AN-94 and the premium knife, fixed.
    ASVal and RepairTool bugs fixed.
    Now if a melee weapon is chosen, only that melee weapon will be allowed, others disabled.
    Server name is updated each match with the new allowed weapon.
    Surprise added for TheLazyEngineer.
    Still to fix:
    Notify the admin if proconrulz is not running.
    Find other bugs and fix them.
    1.0 (26-JAN-2013)
    Weapon Codes:
    Added XBow
    Bug Fixes and Enhancements:
    Bugs found with weapon code for getting tags, fixed.
    Surprise removed for TheLazyEngineer.
    Still to fix:
    Nothing, dev done unless other enhancements wanted. 1.1 (11-FEB-2013)
    Weapon Codes:
    Added Robot
    Bug Fixes and Enhancements:
    Added customization to server name, now admin can change the server name template.
    Added a warning for players if the plugin is restarted during a match, since the weapon is randomized on restart.
    Still to fix:
    Nothing, dev done unless other enhancements wanted. 1.2 (11-FEB-2013)
    Weapon Codes:
    Added m16a3
    Bug Fixes and Enhancements:
    fixed crossbow.
    Still to fix:
    Nothing, dev done unless other enhancements wanted.

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  20. AutoMessages

    This plugin allows you to have automated messages in your server

    Welcome Message
    This allows you to have a custom welcome message that is displayed to every player or the players squad when they join
    User [playerName] to insert the players name that just spawned in.

    Leave Message
    This allows you to alert everyone to let them know that a specific player has left the server
    Use [playerName] to insert the players name that just left the server.

    Auto Messages
    This allows you to setup automated messages that scroll throughout the game, it will automatically start at the first message and scroll through with a delay of so many seconds which can be set.

    You can have multiple lines print when a message pops up by typing the message then right after it put a | or {newline} which will print everything after it on the next line.

    For Example: you put
    Message 1 Line 1|Message 1 Line 2
    or
    Message 1 Line 1{newline}Message 1 Line 2
    will display two different lines at the same time

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  21. BF3AntiSpawnCamp

    Prelude
    A small plugin to monitor and punish, if necessary, players that seem to be repeatedly spawn killing/camping.
    Plugin can Automatically Punish or allow Spawn Killed players to Punish, depending on if the maximum infractions have been reached.

    AntiSpawnCamp Debug
    Debug Depth
    0 - provides no debug info and keeps the plugin console free of clutter from this plugin. 1 - will provide some minimal info regarding players, and is a good way to make sure the plugin is actually working. 2 - is more for me, but can provide some extra debug info if you think that the plugin is acting oddly. This info can possibly help me to fix an issue in the future.
    AntiSpawnCamp Settings
    # of seconds between Spawn and Death
    Determine how long you want to monitor a player after spawning. Maximum amount of time is 10 seconds, there really is no need to track after that. Keep in mind that a player does not have control over their soldier for about 2 seconds after the server registers them spawning into game. Infractions cool down time in seconds
    For every x number of seconds, without committing a spawn kill(according to the plugin), the offending player will have an infraction removed. Maximum value is 1800 seconds(i.e. 30 minutes) Take Action Auto/By Player/Both
    Choose to Auto Kill, Kill By Player Punish, or utlize Both When using Both and "Max # of Infractions before Auto Slay Action is taken" is smaller than "Max # of Infractions before Player Punish" then Player Punish will never fire. Max # of Infractions before Auto Slay Action is taken
    Set how many times a player can commit spawn kills(according to the plugin), before action is taken against the offending player. Maximum allowed value is 20. Max # of Infractions before Player Punish
    Set how many times a player can commit spawn kills(according to the plugin), before the last victim of the spawn killer can punish for it. Maximum allowed value is 20. Time a player has to punish his killer(seconds)
    Only available if "Take Action Auto/By Player" = "By Player" Number of seconds the last Spawn Killed player has to punish or the punishment choice will pass onto the next player Spawn Killed by the Killer. If the Victim player does not Punish then the next Infraction will be larger than the needed Infractions, I left it like this so that other players can see that it is getting out of hand, and hopefully are more likely to punish if they get Spawn Killed. In Game Command to Punish
    Only available if "Take Action Auto/By Player" = "By Player" Ability to change the In Game Command so that it does not conflict with other plugins.
    In Game Messages AntiSpawnCamp
    Admin Messages show Header
    Turn "Admin Message Header" "On/Off" Determine if the plugin should add a Header to each In Game message. Admin Message Header
    Provides the ability to customize a Header for Admin Messages. Admin Messages show Slay Player
    Turn "Admin Message Slay Player" "On/Off" Admin Message Slay Player
    Message that is displayed In Game to everyone on the server when a Spawn Killer is alive killed by BF3AntiSpawnCamp.
    String Replacement Variables {0} = Killer {1} = Victim {2} = Killer's Current Infractions {3} = "Max # of Infractions before Action is taken" Admin Messages show Committed Spawn Kill
    Turn "Admin Message Committed Spawn Kill" "On/Off" Admin Message Committed Spawn Kill
    Message displayed everytime a Spawn Kill occurs.
    String Replacement Variables {0} = Killer {1} = Victim {2} = Killer's Current Infractions {3} = "Max # of Infractions before Action is taken" Admin Message Victim Punish
    Only available if "Take Action Auto/By Player" = "By Player" Message displayed to a player/squad that was the last victim of a Spawn Killer reaching the "Max # of Infractions before Action is taken" Informs the Victim how to take action against the Spawn Killer.
    String Replacement Variables {0} = Killer {1} = Victim {2} = "Time a player has to punish his killer(seconds)" {3} = "In Game Command to Punish"
    Versions
    BF3AntiSpawnCamp 0.6 Beta
    Fixed: Punish Message was being broacast to all players, not the squad of the Victim/Punisher. BF3AntiSpawnCamp 0.5 Beta
    Modified: "Take Action Auto/By Player" - changed to "Take Action Auto/By Player/Both" allows the server to enforce both methods of killing a spawn killer. Added: "Max # of Infractions before Player Punish" - Infractions count at which players recieve notification to be able to puish a spawn killer Removed: "Admin Messages show Slay Player Dead" and "Admin Messages Slay Player Dead" - With the information of to much chat box clutter and being a somewhat redundant feature I removed it. Fixed: "Admin Messages show Slay Killer Alive" and "Admin Messages Slay Killer Alive" - It was worded improperly and I removed the Slay Player Dead messages. So it is now "Admin Messages show Slay Player" and "Admin Messages Slay Player". Modified: Moved each In Game Message to it own setting section to make it easier modify them. Fixed: Example messages were firing upon plugin loaded, change them to only show if they are modified. BF3AntiSpawnCamp 0.4 Beta
    Removed: "Take Action when Max Infractions reached" - removing the extra chat feature to prevent excessive chat spam. Removed: "Admin Messages Take No Action" - removing the extra chat feature to prevent excessive chat spam. Modified: Punish methods. Reworked: Admin Messages BF3AntiSpawnCamp 0.3 Beta
    Fixed: Retardedly I was calculating every kill not just the ones that counted as a Spawn Kill. Ahh the dumb things you overlook testing by yourself. Added: Ability to allow players to choose to punish or have PROCon Auto Punish. Added: Time limit a player has to punish their Killer. Added: In Game command for the Player Punish feature. BF3AntiSpawnCamp 0.2 Beta
    Fixed: had an issue with not setting TeamID's correctly unless it was a connecting player. Affected players that were on the server when the plugin was loaded. BF3AntiSpawnCamp 0.1 Beta
    Initial release of the plugin to see waht others may help me to find for issues, or additions.

    3 downloads

       (0 reviews)

    0 comments

    Submitted

  22. BF3Manager

    Prelude
    This is my first plugin for PROCon and my first attempt at coding/scripting C#. So please keep that in mind if you notice some retarded stuff in the code.
    All the not so retarded code I learned from reverse engineering other coders plugin features to determine how things work in C#.

    Many Thanks to all scripters on here who post on the forums answering questions. I found most of what I needed by using the search feature + google, and only had to ask 2 questions regarding how things work.

    Special Thanks to Zaeed for explaining how some of the internal methods work. And micovery for answering on how to submit a plugin.
    This plugin is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

    I recommend creating a backup of the settings for this plugin once you have created a setup you are happy with, as there is a lot of stuff to go thru and reset should the settings get wiped from the servers PROCon config file.

    Description
    Gives admins the ability to utilize and manage up to 7 different map lists dependent on current player count on the server. Time Based Map List provides the abillity to run 1 map list between set Time periods. Map lists are able to set variables on a per map/per list basis. Also allows the adjustment of in-game commands to suit your needs or to prevent a conflict with another plugin. Provides some internal plugins somewhat by enabling and disabling features. Map Vote(Rock the Vote) Empty Map Rotate Random Map Rotation Dynamic Infantry Only for low player counts Variables by Map w/ a defaulting list of variables Max Players by MapList/GameType/Max Player allowed on Server.
    .: BF3Manager
    BF3Manager (Select Internal Plugin)
    Allows the ability to select what area of the plugin you want to modify. This implementation was simply to alleviate clutter with to many settings to scroll through at the same time.
    .: Messages - (InGame Admin) & (Plugin Console)
    InGame Admin Messages (0=Off 1=On 2=VisualAid)
    0: Will completely disable all in-game admin messages from this plugin, except for the nextmap command. 1: Will show the most basic of info when producing in-game admin messages 2: Will add a prefix line to each message. To provide a bit of a visual aid distinguishing the messages from regular chat. *****Map Lists***** *****Next Map***** *****Rock the Vote***** Debug Depth (How thorough debugging is)
    99: Will provide every thing that can be dumped to PluginConsole Other allowed values are the same as VarDebug Depth and MapDebug Depth. VarDebug Depth (How thorough debugging is)
    MapDebug Depth (How thorough debugging is)
    0: Will completely disable all Plugin Console messages. Except for some variable limit messages. 1: Will just provides basic info regarding changes to variables, so you know things are taking effect. 2: Will provide a slight bump in info from 1. 3: Will provide a slight bump in info from 2.
    .: InGame Commands - (Settings)
    !,@,#,/
    are all acceptable prefixes for in-game commands nextmap
    Will show the nextmap decided by random or regular rotations, and Rock the Vote map winner. rtvlist
    If someone missed the maps available for voting it will send a new list to chat. rtv
    Informs PROCon that you are adding a request for a map vote. rockthevote
    Same as above left in so newcomers can see it and have a better idea of what !rtv is. vote #
    While Rock the Vote is active this will add your vote to the list for the map you select by a number value. stoprtv
    Will stop and reset a Rock the Vote at any time. Only available to admins that can manipulate the map list in procon.
    .: Rock the Vote - (Settings)
    Rock the Vote (On/Off)
    Enable and disable the use of the Rock the Vote feature. When !rtv goes thru and a map vote starts if 2 maps have equal votes or noone votes then it will randomly select a map from the list to set as the next map. Rock the Vote (Current Map Included)
    Determine if Rock the Vote should include the current map in its "random" selection. Does not mean it will always be a selectable map in the vote, just that it is considered when the random maps are chosen Rock the Vote (Allow RTV on Multi Rounds)
    Yes = RTV will work during the first round of maps that have more than 1 round. No = RTV only works if the server is on the last round for the map, from the MapList.txt. Rock the Vote (Change After Vote)
    Determine if you want maps to finish playing out or if they should be changed after a vote gooes through. Rock the Vote (Change After Vote Wait in Seconds)
    If Rock the Vote (Change After Vote) is enabled tehn this sets the amount of time to wait before changing the map. Value is in seconds and can not be more than 60 seconds. Rock the Vote (# of maps to use in vote)
    Set the number of maps that will be included in the !rtvlist Value can be between 2 - 5, more than that and it is difficult to see all the maps at the top of the list. If you set this value lower than your smallest map list maps count then it will produce results with the same maps multiple times in the !rtvlist when a vote is called. Rock the Vote (Wait Minutes after LevelLoad)
    How long after a level has loaded before !rtv is recognized. Value is in minutes and can not be more than 30 minutes. Rock the Vote (Duration Minutes to collect votes)
    How long to accept the !vote # command after !rtv has started. Value is in minutes and can not be more than 5 minutes. Considering upping the time to a larger value if it is asked for enough. Rock the Vote (% Players on Server)
    Percentage of the current player count on the server needed to type !rtv for a Rock the Vote to start.
    .: Map Lists - (General Settings)
    # of Map Lists
    Determine how many Map Lists are to be set and available. Will store settings for Map Lists if this value is changed to a lower number than previously set. Use Empty Map Rotation
    Turn Empty Rotate On/Off. While On this will rotate your maps every so often determined by the setting below, if there are no players connected. Empty Time in Minutes
    How long to wait before rotating an empty map if Use Empty Map Rotation is On. Value is in minutes and can not be less than 5 minutes or more than 30 minutes. Use Random Map Rotation
    Turn Random map rotation On/Off While On this will randomly select a map from the current map list as the nextmap after a level loads. Use Time Based Map Rotation
    Turn Time Based Map List On/Off While On this will modify the Server Map List at a specified time, no matter what the player count is.

    :: Map Lists - (Lists Settings)
    List Settings will be created individually depending on how many lists are set to be created.

    #: Map List (Name NameOfList)
    Gives the Map List a friendly in-game name for admin messages. Will also add teh name to all settings that apply to this list. #: Map List Min Players 2 Use (NameOfList)
    Minimum player count before this map rotation will be enabled, and loaded to the server. Keep in mind that by design Map List 1: is your largest player count Map List, and Map List 7: would be your lowest player count map list. An Empty Map List can be created by setting your smallest player count list to 0 players minimum and the next Map List to 2 or 1 players minimum. #: Map List Max Players 2 Use (NameOfList)
    This value is only a Visual Referance so that it is evident at what player counts the List will run at. YOU CAN NOT EDIT THIS VALUE #: Map List (NameOfList)
    This is the actual list of maps. It accepts maps exactly like the MapList.txt file does. XP1_001 SquadRush0 2 XP1_001 SquadDeathMatch0 1 XP1_001 TeamDeathMatch0 1 XP1_001 RushLarge0 2 XP1_001 ConquestSmall0 1 XP1_001 ConquestSmall1 1 XP1_001 ConquestLarge0 1
    :: Map Lists - (Time Based List)
    Only visible if "Use Time Based Map Rotation" = "Yes"

    Time Based Map List Start
    The time that the Server should switch to the Time Based Map List. This value must be in a proper DateTime format i.e. 9:32 PM Time Based Map List Stop
    The time that the Server should switch back to running the regular Map Lists. This value must be in a proper DateTime format i.e. 4:15 AM Time Based Map List
    The list of maps that will be used for Time Based Map Lists. XP1_001 SquadRush0 2 XP1_001 SquadDeathMatch0 1 XP1_001 TeamDeathMatch0 1 XP1_001 RushLarge0 2 XP1_001 ConquestSmall0 1 XP1_001 ConquestSmall1 1 XP1_001 ConquestLarge0 1
    .: Variables - (Settings)
    Max Players allowed on Server
    Maximum players that the server can hold, generally determined by what you rent from your GSP(Game Server Provider). Is used for a lot of the plugins functions so make it a valid value. Value can not be less than 8 or more than 64. Use Max Players by Maps List/GameType/MaxPlayerServer
    If you use AdaptiveServerSize plugin or any other plugins that modify vars.maxPlayers then do not use this as the plugins will conflict a bit. Determine if the plugin should set the maxplayers dynamically for the server, and by what method. Use Variables by Map
    If you use CSettingChangeOnMap plugin or any other plugins that modify game variables then do not use this as the plugins will conflict a bit. Turn On/Off the ability to set variables on a per map/per list basis. Events are fired on round end. Use Infantry Only
    Due to issues with some maps spawning vehicles when vars.vehicleSpawnAllowed false is set before or at level load, then vars.vehicleSpawnAllowed true is set after the level has been loaded. I have made a work around with several options for I.O. to try and cater to all the available methods it can be setup and work. Turn dynamic Infantry Only On/Off. Tells PROCon to start performing I.O. checks and setting values according to how you have I.O. set up with the below settings.
    This can cause your Server to show as Custom in BattleLog if you run Hardcore Depending on how you set "I.O. Default Game Mode". If you Run Normal mdoe it will change between Normal and InfantryOnly I.O. Off @ Player Count
    Set the player count needed on the server to disable the Infantry only completely until the player count falls back below this value. Value can not be less than 0 or more than 64. I.O. Default Vehicle Spawn Delay
    Used only if you have "I.O. Default Game Mode" set to "Retain Hardcore" When I.O. is fired on a hardcore server then it turns vars.vehicleSpawnAllowed false and vars.vehicleSpawnDelay 999999, once the level has loded it then sets vars.vehicleSpawnAllowed true. If I.O. is disabled it then sets vars.vehicleSpawnDelay to this default value. I.O. Default Game Mode
    Allows a server admin to determine what type of I.O. is to be used on the server. Normal/Infantry Only Used if the server is setup to run Normal mode. Will cause Battlelog to show as Infantry Only when it is fired on PROCon Retain Hardcore Used if the server is setup to run Hardcore mode. Will cause Battlelog to show as Hardcore when it is fired on PROCon. Will only completely work on some maps. SQDM maps always spawn a vehicle and do not respond to vars.vehicleSpawnDelay. Some CQ/Rush maps will spawn vehicles, but once destroyd the first time will not spawn until I.O is disabled again. Allow Custom If using Hardcore as a default this will ignore trying to retain Hardcore in Battlelog and just completly turn vehicle spawning off until I.O. is disabled for player count.

    :: Variables - (Max Players)
    Provide a list of max player settings depending on what value is selected for Use Max Players by Maps List/GameType/MaxPlayerServer.

    Maps List
    Provides a Max Player setting for each map list that has been created. GameType
    Provides a Max Player setting for each GameType supported by BF3. Squad Rush SQDM TDM Rush Conquest ConquestAssault Conquest 64 MaxPlayerServer
    This will ensure that your server Max Players(vars.maxPlayers) never drops below the value set for Max Players allowed on Server.
    ~: Variables - (Map Lists)
    Variables are acceptted exactly like they are in the StartUp.txt file on the server.
    vars.gameModeCounter 100 vars.autoBalance true Default Vars Settings
    A list of default values for variables on the server. Any variables set for a specific map or maps should have a counter value for most of the other maps in a list. This setting allows for those defaults to be sved and set at round end for each map. Map List Variables to modify
    Provides drop down list of all the map lists, it will only provide maps to adjust settings for if that Map List has maps in it and if it is the selected value. (NameOfMap)
    If you have maps in the currently selected Map List Variables to modify, then there will be an input box for each map in that map list to set variables on a per map basis. Variables set for each map are only fired for that map if it is the next map in rotation at round end. This list is compared to the Default Vars Settings to ensure that if a variable exists in both that only the map setting will be applied. All variables from Default Vars Settings that are not in each maps settings will be fired on round end as well.

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  23. Team Kill Kicker

    Description

    This plugin monitors the server for team killing. When a set number of team kills is reached by any player, they are warned to stop team killing. After a second set number of team kills that player is removed from the server. The team kill count is reset for each level.

    Options
    =======================================
    Yell Warnings – When this is enabled warnings will be yelled to the player that did the team killing. Yell Time – Time to display the yelled warning. Display kicks in global chat – Option to enable display of kicks in global chat for all players. Log in Console – Display a log of all team kills and actions in the plugin console. Kick at (TKs) – Number of team kills before player is kicked. Kick message (Private) – Message that is displayed in the “You have been kicked” dialog. (Kick reason). Kick message (Public) – Message that is displayed to all players in global chat (only used if “Display kicks in global chat” is on). Warn at (TKs) - Number of kills before player is warned. Player will be warned for every team kill between warn and kick values. Warning Message - Message sent to player warning them of the coming kick if they keep team killing. Ban Team Killers - Temp ban team killers rather than kicking them. Ban Time (Minutes) - Time to ban players for if tbanning is enabled in minutes. Enable Mirror TK - Kill the team killer as punishment. Kill at (TKs) - Number of TKs before killing starts if Mirror TKs is enabled. Mirror TK Warning Message - Message that the team killer will recieve before being killed.

    5 downloads

       (0 reviews)

    0 comments

    Submitted

  24. Vote Ban BF3

    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/kick the player who has a Vote Ban/Kick 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.
    NOTE: These commands may be redefined by you in the plugin settings.

    Settings
    Vote Ban
    Enable Vote Ban?
    Allows you to enable or disable the ability for players to Vote Ban. Vote Ban Player Count Threshold
    The minimum number of players that must be on the server for Vote Banning to be enabled. 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.)
    Vote Kick
    Enable Vote Kick?
    Allows you to enable or disable the ability for players to Vote Kick. Vote Kick Player Count Threshold
    The minimum number of players that must be on the server for Vote Kicking to be enabled. 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.
    Hack Cry Responder
    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.
    Whitelist
    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. Clan Tags
    Allows you to add Clan Tags to protect the wearer of any tag from being Vote Banned/Kicked. Action TakenThe 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.
    In-Game Commands
    These allow you to customize the in-game commands for this plugin.
    Vote Ban Commands
    The commands used to initiate a Vote Ban. Vote Kick Commands
    The commands used to initiate a Vote Kick. Yes Commands
    The commands used to vote yes to the vote in progress. (Also used to confirm a suggested player name.) No Commands
    The commands used to vote no to the vote in progress. (Also used to deny a suggested player name.) Cancel Vote Commands
    The commands used to cancel the vote in progress.
    In-Game Messages

    This allows you to customize all the messages that this plugin sends to the server.
    Reset Messages?
    Use this to retrieve the default list of messages. This is useful when you may have made a mistake and messages start to not show up. Message List
    The list containing all the messages that this plugin sends to the server. Be careful not to delete any lines otherwise things will go wrong!

    2 downloads

       (0 reviews)

    0 comments

    Submitted

  25. Advanced Scramble

    Description
    Advanced Scramble lets you manage the teams on your Bad Company 2 server.
    This plugin expands upon functionality introduced in the Simple Scramble plugin. This plugin allows server administrators to scramble (or, more appropriately, distribute) players on their Bad Company 2 server. The ability to ignore and group players has been added as well. The command for this plugin is ascramble.

    To use the ascramble command, the player must have an account on procon with the permission "Allowed to move players between teams and squads". For syntax, see the following:
    [@!#/]ascramble <now/round/map> <random/clan>
    Descriptions:
    The now option will scramble the players immediately. You can delay the scrambler by specifying either round or map to scramble upon round end and map end respectively.
    The random option will scramble the players without bias. You can specify clan to attempt to keep clans together.

    3 downloads

       (0 reviews)

    0 comments

    Submitted

  • Member Statistics

    33
    Total Members
    36
    Most Online
    vc20194
    Newest Member
    vc20194
    Joined

×
×
  • Create New...