Jump to content

Search the Community

Showing results for tags 'bc2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • News
    • General Discussion
    • Tech Talk
    • Archives
  • Procon 1.0 Frostbite
    • General
    • Knowledge Base
    • Plugins
    • Localization
    • Deutscher Support (German Support)
  • Games
    • General
    • Battlefield 2
    • Battlefield Bad Company 2
    • Battlefield 3
    • Battlefield 4
    • Battlefield Hardline
    • Battlefield 1
    • Battlefield V

Product Groups

  • Hosting Services
  • One Time Donations

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


IGN

Found 5 results

  1. Originally Posted by bambam*: Donations: none needed - ProconRulz is 100% free software. Please acknowledge any support by clicking the Rate this thread link just above this post, and sharing the rulz you come up with. Thank You. MAJOR UPDATE TO V44. BF4 SUPPORT, PLUS SUPPORT FOR EXTERNAL PROCONRULZ SCRIPT FILES 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, e.g. "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, e.g. 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 killstreak announcers or in-game admin or rude-word-responders 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 e.g. limiting nades with On Kill;Weapon M67;PlayerCount 3;Say Too many nade kills for %p%;Kill. ONLINE DOCUMENTATION HERE How to enter your rulz click here to expand this section: See below in this thread for sample rulz and an explanation of BF3/BF4 limitations so you don't ask the same "how do I block mortars" question as everyone else... ProconRulz has a very flexible range of conditions and actions that can be applied, so as your rulz get fancy you are in effect creating a custom plugin. But everyone begins thinking they "just" want a simple weapon limit. NEWS 25-Dec-2013: version 44j1 uploaded. Rulz .txt files now reloaded on plugin enable (useful for layer-server users). NEWS 17-Dec-2013: version 44h6 uploaded. New On RoundOver trigger that fired on end-of-round (useful for BF4). !knife rulz added. NEWS 9-Dec-2013: version 44g3 uploaded. BUGFIX version for new "On Init" trigger with BF3/4. Users who downloaded 44g.2 should replace with this version if they want to use the new On Init trigger (also used in snipersquad rulz set). NEWS 6-Dec-2013: version 44g2 uploaded. Sniper Squad limiter rulz added. Added Linux support for %ini_..% vars file. New 'On Init' trigger that can be used for simple startup values for rules. NEWS 2-Dec-2013: version 44f1 uploaded. Support for Linux external .txt rulz files. Updated sniper limit with additional !setsniper command (e.g. !setsniper bam) for admin to guarantee sniper slot to a player. NEWS 26-Nov-2013: version 44e2 uploaded. Support for BF4 with four weeks of testing (thanks D1bble, Tarreltje). Now rulz can be held in an external file and loaded by the plugin making it easier to share rulz sets e.g. for weapon limits, teamkill limits, announcers, etc. Older news click to expand: ProconRulz has been extensively used on BFBC2 servers (for BFBC2 see this thread*). That thread now has hundreds of entries so for BF3 I've started this new one. ProconRulz has relatively comprehensive documentation on its 'Details' tab, so please refer to that. For info, if you haven't downloaded the plugin yet, you can check out an cached version of the details info online here. Of course for the most up-to-date version of the documentation, check the plugin 'Details'. ProconRulz allows rulz of the format "Trigger;Conditions...;Actions..." with a wide choice of triggers, conditions and actions. The most trivial forms of weapon limits can be implemented with a single rule, e.g. to kill players using the M320 underslung rifle nade, use the single rule given as an example at the top of this post. However, with a bit of thought, it is possible to provide rulz with a more complex behaviour, e.g. warn on the first kill, kill on the third, kick on the fifth. ProconRulz installs with half-a-dozen default simple rulz that provide a template for your rulz if that helps. 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 / !f for 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. ************************************************** ************************************************ Plus, you can still edit additional rulz directly into the Plugin settings with these as examples for ideas below ************************************************** ************************************************ BF3 Map names and modes In case you need them in Map or MapMode conditions, BF3/BF4 names and modes are collected into this post*. ProconRulz doesn't really care what keys you use - it's up to you to check your conditions match whatever your server is sending. This is collected documentation for BF3 that you can find on the internet. Some current limitations of BF3/BF4 to be aware of click to expand: Some sample rulz KEEP the default logging On Kill rule at the end of all your rulz. This has a 'Log' action which is very helpful when your rulz don't pick up the condition you expected... (e.g. Log %pt% %k% %p% killed %v% with %w% (%wk%), damage %d%). You don't need to understand this now, just leave it in. Example 1. Limit a single weapon (usage suicidal, kick on 4th kill, ban on 6th kill): Click to expand: Example 2. Limit a weapon category via Damage condition (usage suicidal, kick on 4th kill, ban on 6th kill): Click to expand: Example 3. For a sniper/pistol server (usage of other weapons is suicidal, kick on 4th kill, ban on 6th kill): Click to expand: Example 4. Make teamkills suicidal Click to expand: Example 5. Stop use of rockets on map Operation Metro: Click to expand: Example 6. If you want to reduce the frequency of a weapon use e.g. limit players to max 2 nade kills per minute: Click to expand: Example 7. Kill Streak Announcer by ty_ger07. Please see this dedicated thread* Example 8. Basic Cheater Detector Click to expand: Example 9. Limit vehicle use when teams are small Click to expand: Example 10. Easy in-game admin Click to expand: Example 11. No MAV's on Metro Click to expand: Example 12. Unreal Tournament Multi Kills Announcer by Bl1ndy Please see this dedicated thread* Example 13. Sniper Limit V2!!! (credit tarreltje) Please see this dedicated thread* Click to expand for a bit of explanation of how these rulz work in BF3: Example 14. Multi-language 'join' welcome messages (credit Angry_AGAIN) Click to expand: Example 15. Knife/Defib/Repair Tool Kill YELL Announcer This plugin will put a Yell message on the screen each knife or other melee weaon kill Click to expand: Example 16. End of Round Stats Announcer by tarreltje These rules give the 'most kills', 'most knife kills', 'most headshots' playernames and kill counts during and near the end of the round. As with all ProconRulz rulz you can tweak the rulz for different stats or timings as you want. Please see this dedicated thread* Example 17. Country filter by L2Devlier Here's an interesting concept, illustrating the global villiage we live (game) in. It's possible you live in a small country, adjacent to a large country (e.g. China), and you're trying to build a local community, but end up with the server being dominated by large numbers of gamers texting in the foreign language from the large-country-next-door, what can you do. L2Devlier came up with this solution in in a long PM to me emphasized this is not about being racist, just trying to compensate for limitations in the EA queueing system if you're trying to build a local community. For other-country-applicability you'll need to read the rulz, understand what they do, and tweak the country-codes as appropriate. Click to expand the rulz: Example 18. BEST 3 PLAYERS Announcer by tarreltje Every 100 tickets, these rulz announce the top 3 players based on kills, e.g.: BEST 3 PLAYERS : 1st Tarreltje 1000 kills 2nd Gaga 580 kills 3rd Noob 30 kills Please see this dedicated thread* Example 19. SERVER STATS by tarreltje On the first kill of each round, server will announce the player names with the highest kill counts, e.g. DUTCH COWBOYS SERVER STATS 1st RINUSS 1000 kills 2nd BAMBAM 500 kills 3th GAGA 200 kills Most Knives: RINUSS 3000 knives Please see this dedicated thread* Example 20. !punish and other TeamKill protection rulz by ty_ger The !punish, !forgive commands you've probably seen on a variety of servers, plus optional rulz so you can automatically punish teamkillers if you prefer that for your server. Please see this dedicated thread* Example 21. !votekick - ingame command for players to vote to kick another player Click to expand: Example 22. Adaptive SPAMBOT by tarreltje Easy to modify, these rulz 'chat' different messages according to the map 'Mode' that is currently running, i.e. you can have message for TeamDeathMatch, and different messages for Conquest. The same rulz could be tweaked if you want messages based on Map, rather than MapMode (i.e. some messages for Caspian, different messages for Seine Crossing...) Please see this dedicated thread* Example 23. Simple Aimbot headshot detector credit russel5 These rulz count headshots and if it's more than 60% after 30 kills (these params in line 5) and it's not a sniper rifle, player is banned. click here for rulz: Versions summary: v44 (Nov 26 2013): Support for BF4, plus the support for separate rulz .txt files (incl Linux from 44f.1 credit FritzE).On RoundOver trigger. v43 (Aug 21 2012): Arithmetic in Set/If statements, permanent 'ini' vars, rounding, new date/time and teamsize variables, logging options. New player %score% variable, '+' as 1st character on line allows multi-line rulz. v41 (Jun 29 2012): More flexible support for in-game admin commands e.g. !kick v40 (May 15 2012): Quoted strings can be used in rulz e.g. Set %server_message% "Get ready for next round" v39 (Apr 12 2012): Yell added (with BF3 R20). Yell/Say can now be to all, Player, Squad, Team (e.g. SquadYell). Player/Victim country codes available (e.g. %pcountry% see online docs). Tickets remaining now in %team_score%. v38 (Jan 18 2012): any order now permitted for intermixing actions and conditions. server, team, squad, player variables now more easily mixable, Exec can now run PunkBuster commands in addition to the v37 PBBan & PBTempBan, TargetPlayer condition enhanced for ease of use in rulz. v37: PunkBuster Kicks/bans, new rulz processing flow, rulz variables v34: Players 'protected' from kicks, kills, bans by ProconRulz now Admins, Admins+Reserved_Slots, Neither, plus Player and Clan whitelist. v33: BF3 compatibility v1..32 (see ProconRulz BFBC2 thread) Downloads: 15,811 + count on this version: Please note: There is an unsupported version below ProconRulz_NL.zip which allows new lines in messages. Example new line: Code: On Say;Text /show;PlayerYell \nHello %p%\nThis is your first visit, please type !rules It should look like this on the player screen: [ADMIN] Hello DarthVader This is your first visit, please type !rules Attached Files: ProconRulz_44j1.zip ProconRulz_NL.zip proconrulz_documentation.pdf
  2. View File Procon Client Download for Procon 1.X for BFC2, BF3, BF4, MoH & BFH Attached to this post, you can find the latest downloads of Procon 1.X and everything attached to it. To download the latest version available, simply click the big LATEST VERSION link. In order to be able to run Procon You can find the changelogs for all patches in this thread: TBD If you're interested in some of the older versions of Procon 1.X, please follow this link: TBD Starting with version 1.4.1.4, we will not include the media files (maps, kill icons, etc.) for Battlefield: Bad Company 2 and Medal of Honor with the regular Procon download anymore. This measure allows us to drastically reduce the size of each Procon download and thus saves us and your bandwidth and resources during updates. For version 1.4.1.4, we have however included the media files once more (renamed as "AlphaPack") to allow a smooth transition for BFBC2 and MoH users. Version 1.4.1.5 and upward will no longer contain these files, however, they will be available as a separate download: procon_mediapack_bfbc2_moh.zip The source code of Procon 1.X can be found at our GitHub-repository: https://github.com/AdKats/Procon-1 Note: Starting from version 1.5.3.0 you will need to have .NET 4.7 installed. Old Versions can be downloaded from here. Submitter Prophet731 Submitted 12/24/19 Category Procon  
  3. Assassination & WAR Mode plugin for Procon ? Havent seen such plugin. Would be nice when there mini games for procon.
  4. VIP Slot Manager 1.0.0.6 [bF3, BF4, BFH, BC2] 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. NOTE: When you use this Plugin, make sure that AdKats (if you use it) does not touch the vips or reserved slot list. Download Download the Plugin and website template: HERE (zip file) Installation IMPORTANT: This Plugin requires a MySQL database with INNODB support. 1. Upload the VipSlotManager.cs file to your Procon Layer Server into the folder procon/Plugins/BF4 (procon/Plugins/BFHL OR procon/Plugins/BF3). Restart your Procon Layer. 2. Start your Procon PC Tool. Open the VIP Slot Manager Plugin settings. In the settings, you will find the section '1. MySQL Details'. There simply enter your MySQL details (host IP, port, database, 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 '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 the 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! It requires a webspace with PHP support and access to the SQL database. You can find a free website template for this purpose within the downloaded ZIP file from this Plugin. 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', then 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: %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] - this is case sensitive! !addvip [full playername] [days] e.g. !addvip SniperBen 30 This cmd 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. !addvip [full playername] +[days] e.g. !addvip SniperBen +7 This cmd 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. !removevip [full playername] e.g. !removevip SniperBen This cmd will remove the VIP from the Gameserver. The player will stay in the SQL database and be marked as 'status inactive'. !checkvip [full playername] e.g. !checkvip SniperBen This cmd will display the remaining time !changevip [old playername] [new playername] e.g. !changevip SniperBen SniperBenni This cmd will change the VIP Slot playername !addsemivip [full playername] e.g. !addsemivip SniperBen This cmd 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'. /vsm-addvip [full playername] [days] e.g. /vsm-addvip SniperBen 30 This cmd 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. /vsm-addvip [full playername] +[days] e.g. /vsm-addvip SniperBen +7 This cmd 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. /vsm-removevip [full playername] e.g. /vsm-removevip SniperBen This cmd will remove the VIP from the Gameserver. The player will stay in the SQL database and be marked as 'status inactive'. vsm-changevip [old playername] [new playername] e.g. /vsm-changevip SniperBen SniperBenni This cmd will change the VIP Slot playername /vsm-addsemivip [full playername] e.g. /vsm-addsemivip SniperBen This cmd 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. 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_.ini). When you read this file within the Plugin ProconRulz (%ini_vipslotmanager%) 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'. No Aggressive Join Close On Round End (optional) 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 (optional) 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 Lvl 1: Errors will be displayed. Lvl 2: will also show log entries for added and removed VIP players. Lvl 3: will also show log entries when a VIP player joins the server. Lvl 4: will also show log entries when a player uses the in-game commands (e.g. !lead, !killme). Lvl 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 (optional) 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), 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. It is recommended that all Gameservers use the same MySQL database. If two or more Gameservers use the same 'Server Group', 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. Otherwise the Plugin clean up old entries with the status 'inactive' automatically after 365 days. Witch Games are supported? The Plugin works fine for BF3, BF4, BFH and BFBC2. The support for other Games are still not tested. Changelog 1.0.0.6 (23.06.2018) Add: Aggressive Join Abuse Protection (optional) Add: Command !addsemivip to add temporary VIP till round end / rejoin (optional) Add: Advanced Log to Adkats (optional) Add: Alternative Link to github 1.0.0.5 (26.01.2018) Add: VIP EA Guid Tracking to update playername changes automatically (optional) Add: Command !changevip to change VIP Slot playername Modification: In-Game VIP Command !lead (optional VIP protection) Modification: Small code improvements Fix: SQL Credentials after server restart Fix: BC2 Procon compatibility Fix: Website compatibility to php 5.6 / 7.0 / 7.1 / 7.2. / 7.3 New features and filters for better workflow 1.0.0.4 (04.10.2017) Add: Aggressive Join features 1.0.0.3 (12.08.2017) Add: Auto Correction for case sensitive difference in playername Add: Auto Database Cleaner Fix: Website (add days button) 1.0.0.2 (09.05.2017) Fix: Website blank site 1.0.0.1 (02.05.2017) Fix: In-Game VIP Commands Download Download the Plugin and website template: HERE (zip file)
  5. Prophet731

    Procon Client

    Version 1.5.3.4

    35104 downloads

    Download for Procon 1.X for BFC2, BF3, BF4, MoH & BFH Attached to this post, you can find the latest downloads of Procon 1.X and everything attached to it. To download the latest version available, simply click the big LATEST VERSION link. In order to be able to run Procon You can find the changelogs for all patches in this thread: TBD If you're interested in some of the older versions of Procon 1.X, please follow this link: TBD Starting with version 1.4.1.4, we will not include the media files (maps, kill icons, etc.) for Battlefield: Bad Company 2 and Medal of Honor with the regular Procon download anymore. This measure allows us to drastically reduce the size of each Procon download and thus saves us and your bandwidth and resources during updates. For version 1.4.1.4, we have however included the media files once more (renamed as "AlphaPack") to allow a smooth transition for BFBC2 and MoH users. Version 1.4.1.5 and upward will no longer contain these files, however, they will be available as a separate download: procon_mediapack_bfbc2_moh.zip The source code of Procon 1.X can be found at our GitHub-repository: https://github.com/AdKats/Procon-1 Note: Starting from version 1.5.3.0 you will need to have .NET 4.7 installed. Old Versions can be downloaded from here.
×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.