Jump to content

Search the Community

Showing results for tags 'bf4'.



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 Bad Company 2
    • Battlefield 1
    • Battlefield 3
    • Battlefield 4
    • Battlefield V
    • Battlefield Hardline

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


Discord


IGN

Found 28 results

  1. Battlefield Admin Control Panel - BFACP View File Running on PHP Version 7 This does not work with any version of the BFACP do not try to run this application on that version. Use the latest stable PHP 5.6. Overview The Battlefield Admin Control Panel (BFACP) is a web based admin tool designed to work exclusively with AdKats (v6+) and XpKillers Chat, GUID, Stats and Mapstats Logger (v1.0.0.3). The software is built with the Laravel PHP framework to speed up development time and make my job a lot easier. FAQ Requirements MySQL Database (5.6+) AdKats v6+ XpKillers Chat, GUID, Stats and Mapstats Logger v1.0.0.2+ PHP 5.5+ PHP Mcrypt PHP PDO Features User, Role, and Permission system. Live Scoreboard with chat. Ban Management for AdKats. Detailed player information with graph charts. Server statistics page for each server showing population history, uptime history with data from UptimeRobot, and Mapstats. Metabans support. Report notifications with ability to change alert sounds. Chatlog searching where you can search by multiple players and/or keywords and ability to only show from a certain date/time range. Message of the Day Quick DB Stats overview and more! Download the latest version. Once downloaded unzip it to a temporary folder on your computer. Next open the .env.php file located in the root folder in your favorite text editor. Scroll down to the database settings section and fill in your database connection information. /** * Database Settings */ 'DB_HOST' => 'localhost', 'DB_USER' => 'root', 'DB_PASS' => '', 'DB_NAME' => 'mydatabase', Next we need to create a encryption key. This is IMPORTANT! The default key provided is just a placeholder string and is insecure. I have provided a page where you can get a random 32 character string. I do NOT save these and they are random on each refresh. You can access this page here, scroll down to the CodeIgniter Encryption Keys. Once you have your key open up the file .env.php in the root folder and scroll down till you see the APP_KEY field. Replace the YourSecretKey!!! with the key that was generated. By default it will look like this. /** * Set your app key here */ 'APP_KEY' => 'YourSecretKey!!!' Once completed upload the entire application to your webserver. Once uploaded you will need to modify some file and folder permissions. Change the files and folders permissions under app/storage recursively to 0777. This application was designed to run on a subdomain and not from a folder from the TLD. Make sure to create a subdomain and if possible have domain point to the public folder that's located under the root folder. Now load up application in your web browser and it will begin the process of creating the tables. This process will take a few seconds to run on first load. When it completed you should see the dashboard. Default login Username: admin Password: password You can change the default username and password by clicking on Site Management > Users > Admin Installing from the command line This method is only for those who have shell access to their web server or VPS. This will download and extract the files to your current directory. Make sure it's an empty directory. If you have git installed you can just run the following command to install it. You must have composer and php command line installed. Composer Method (preferred) composer create-project --prefer-dist --no-scripts --keep-vcs adkgamers/bfadmincp . Git Method git clone https://github.com/Prophet731/BFAdminCP.git . composer install --no-scripts This will clone and install the dependencies need for the BFACP to work. This will checkout the master branch which is the stable version. If you would like to run the develop version you will need to run git checkout develop before you issue the composer command. To update it all you will need to do is run git pull and it will pull the latest version on the current branch (master or develop). To make this an automated process you can create a cron job for it. * * * * * cd /path/to/bfacp; git pull >/dev/null 2>&1 Submitter Prophet731 Submitted 12/25/19 Category Plugin Enhancements
  2. Exactly i am searching for some ProconRulz Code or Insane Limits Code I will appreciate every kind of help
  3. View File Advanced In-Game Admin and Ban Enforcer - AdKats ADKATS 7.6.0.4 RELEASED! Admin Toolset with a plethora of features, over 100 available in-game commands, and many customization options. AdKats focuses on making in-game admins more efficient and accurate at their jobs, with flexibility for almost any setup. Includes a cross-server ban enforcer with advanced enforcement features, global admin management, cross-server player messaging, and the BFAdminCP 2.0+ for web-based control has been released. Designed for groups with high-traffic servers and many admins, but will function just as well for small servers. REQUIREMENTS: This plugin requires a MySQL database, and XpKiller's Stat logger plugin to operate. If you do not have an existing database and/or a Procon layer we suggest using Branzone's hosting services. Our group has been with them for years across BF3, BF4, and Hardline; the most performant and reliable host we've found. Web/Database Hosting: Branzone Web Hosting (Used for MySQL Databases) Procon Layer Hosting: Branzone Procon Layers FEATURES Extensive In-Game Commands. Commands for player killing, kicking, punishing, banning, unbanning, moving, joining, whitelisting, messaging, etc, etc... ~100 available in-game commands. Commands can be accessed from in-game, Procon's chat window, database, and from other plugins. Customizable User Roles. Custom user roles can be created for admins and players, with each role given access to only the commands you want them to use. Default guest role is given to all players and can be edited to your desired specs. Roles and powers are automatically synced between servers so you only need to change user information once. Soldiers assigned to users will also keep their powers even if they change their in-game names. Setting sync between servers. All changes to plugin settings are stored in the database and can be automatically synced between your Procon layers. Setting up new layers or switching layers is a breeze as the settings for existing servers are automatically imported on startup. Infraction Tracking System. Punish/forgive players for breaking rules on your servers. Everything is tracked so the more infractions they commit, the worse their punishment automatically gets. Created so all players can be treated equally based on their history, regardless of who is issuing punishments against them. Heavily customizable. Player Reputation System. Based on issued commands from and against players they can form a numeric reputation on the server. Documentation below. A local leaderboard for reputation is provided in the BFAdminCP. Quick Player Report and Admin Call Handling, with Email Support.Notification system and quick handling features for all admin calls and player reports. Reports can be referenced by number for instant action. Automatic PBSS are triggered on reported players. Orchestration and Server List Management. Server reserved slots, spectator slots, autobalance whitelising through MULTIBalancer, ping kick whitelists, and several others can be automatically handled through the AdKats user list, role groups, and orchestration commands. AdKats Ban Enforcer. AdKats can enforce bans across all of your servers and can enforce on all identity metrics at the same time. System will automatically import bans from your servers, consolidating them in one place, and can import existing bans from the BF3 Ban Manager plugin's tables. Full documentation below. Automated Challenge System with Rewards. The challenge system in AdKats is designed to be a multi-server stats-driven way to give players new goals with rewards. You can set up almost any combination of damage types or weapons to be used by players, in multiple tiers. BF3/BF4 "Hacker-Checker" with Whitelist. Battlelog stats can be polled for players in the server, issuing automatic bans for damage mods, aimbots, magic bullet, and several others. The LIVE system can detect damage mods and magic bullet from a single round of play. DPS checks are enabled by default, with others available after a few clicks. Surrender Vote System. When enabled, if players are stuck in their base with no options, they can vote to end the round with the current winning team as winner. Auto-Surrender/Auto-Nuke System. This uses ticket loss rates to detect where teams are on the map, specifically with how many flags are captured. If a team is being base-camped, it can either automatically end the round with current winner, or nuke the team who is causing the base-camp. Optimal values for Metro 2014 and Operation Locker are available, for both surrender and nuke options. Automatic Updates. AdKats automatically updates itself when stable releases are made, only requiring a Procon instance reboot to run updated versions. This can be disabled if desired, but is required if running TEST versions. Ping Enforcer. Automated kick system based on ping, with moving average calculation, modifiers based on time of day and server population, customizable messages, logged kicks, and manual ping options. AFK Manager. Automated kick system based on player AFK time, with manual kick command. Customizable durations, and option to ignore chat messages counting toward active time. Internal SpamBot with Whitelist. SpamBot with options for simultaneous say, yell, and tell. Customizable intervals between each type of message, and ability to whitelist players/admins from seeing spambot messages. Commander Manager. Commanders can cause team imbalance when servers are in low population. This manager can forbid commanders before a certain player count is active. Cross-Server Player Messaging. Private conversations between players can operate not only within the same server, but will work between any online server in the database, and even between any AdKats supported game. Admin Assistants. When fully used this can turn your regular playerbase into a human autoadmin. Trusted players fill the gaps normal autoadmins don't see by utilizing the report system and keeping your server under control even when normal admins are offline. Email Notification System. Email addresses can be added to every user, and once enabled they will receive emails for player reports and admin calls. Fuzzy Player Name Completion. Fully completes partial or misspelled player names. I've been consistently able to find almost any player only a few characters from their name. Can also fetch players who have left the server, are in another server of yours on the same database, or have been in your servers at any point in time. Player Muting. Players can be muted if necessary, giving warnings and kicks if they talk. Automatic mute in specific cases like lanuage can be orchestrated by other plugins like Insane limits. Player Joining. Player's squads can be joined via command, and locked squads can be unlocked for admin entry. Player Locking. Players can be locked from admin commands for a specific timeout, the main purpose is if a certain admin is handling them (checking stats for cheat detection, records, etc.) they shouldn't be interrupted by another admin acting on the player. Player Assist. Player's want to play with their friends, but you don't want to imbalance the teams_ The assist command lets any player join the weak team to help them out and squad up with friends without hurting server balance. Yell/Say Pre-Recording. Use numbers to reference predefined messages. Avoid typing long reasons or messages. e.g. /kill player 3 Server Rule Management. Server rules can be listed, requests for rules logged, rules targeted at other players, and rules can be distributed between servers automatically. External Controller API. AdKats can be controlled from outside the game through systems like the BFAdminCP and through other plugins like Insane Limits. For example, you can issue AdKats punish commands from Insane Limits or ProconRulz and have them logged against the player's profile like any other admin command. Internal Implementation of TeamSwap. Queued move system for servers that are consistently full, players can be queued to move to full teams once a slot opens. Metabans Support. When using ban enforcer all bans can be submitted to metabans and removed if the player is unbanned. Editable In-Game Commands. Command text, logging options, chat access types, and enable options can be edited to suit your needs. Full Logging. All admin activity is tracked via the database per your custom settings for every command, so holding your admins accountable for their actions is quick and painless. If you are using the BFAdminCP nobody but your highest admins will need manual Procon access. Setting Lock. The settings page in AdKats can be locked with a password. This means even admins with access to plugin settings can be blocked from changes using the password. Performance. All actions, messaging, database communications, and command parsing take place on their own threads, minimizing performance impacts. New Extension! Click below to enforce loadouts on-spawn! AdKats Release Notes: https://github.com/AdKats/AdKats/blob/master/CHANGELOG.md#7604-12-jan-2020 I hope you enjoy the plugin. While using this plugin, two players, ColColonCleaner, and PhirePhrey will be added to your server's reserved slot list. If you have any questions, please comment here. Submitter ColColonCleaner Submitted 12/24/19 Category Plugins  
  4. Version 7.6.0.4

    15742 downloads

    ADKATS 7.6.0.4 RELEASED! Admin Toolset with a plethora of features, over 100 available in-game commands, and many customization options. AdKats focuses on making in-game admins more efficient and accurate at their jobs, with flexibility for almost any setup. Includes a cross-server ban enforcer with advanced enforcement features, global admin management, cross-server player messaging, and the BFAdminCP 2.0+ for web-based control has been released. Designed for groups with high-traffic servers and many admins, but will function just as well for small servers. REQUIREMENTS: This plugin requires a MySQL database, and XpKiller's Stat logger plugin to operate. If you do not have an existing database and/or a Procon layer we suggest using Branzone's hosting services. Our group has been with them for years across BF3, BF4, and Hardline; the most performant and reliable host we've found. Web/Database Hosting: Branzone Web Hosting (Used for MySQL Databases) Procon Layer Hosting: Branzone Procon Layers FEATURES Extensive In-Game Commands. Commands for player killing, kicking, punishing, banning, unbanning, moving, joining, whitelisting, messaging, etc, etc... ~100 available in-game commands. Commands can be accessed from in-game, Procon's chat window, database, and from other plugins. Customizable User Roles. Custom user roles can be created for admins and players, with each role given access to only the commands you want them to use. Default guest role is given to all players and can be edited to your desired specs. Roles and powers are automatically synced between servers so you only need to change user information once. Soldiers assigned to users will also keep their powers even if they change their in-game names. Setting sync between servers. All changes to plugin settings are stored in the database and can be automatically synced between your Procon layers. Setting up new layers or switching layers is a breeze as the settings for existing servers are automatically imported on startup. Infraction Tracking System. Punish/forgive players for breaking rules on your servers. Everything is tracked so the more infractions they commit, the worse their punishment automatically gets. Created so all players can be treated equally based on their history, regardless of who is issuing punishments against them. Heavily customizable. Player Reputation System. Based on issued commands from and against players they can form a numeric reputation on the server. Documentation below. A local leaderboard for reputation is provided in the BFAdminCP. Quick Player Report and Admin Call Handling, with Email Support.Notification system and quick handling features for all admin calls and player reports. Reports can be referenced by number for instant action. Automatic PBSS are triggered on reported players. Orchestration and Server List Management. Server reserved slots, spectator slots, autobalance whitelising through MULTIBalancer, ping kick whitelists, and several others can be automatically handled through the AdKats user list, role groups, and orchestration commands. AdKats Ban Enforcer. AdKats can enforce bans across all of your servers and can enforce on all identity metrics at the same time. System will automatically import bans from your servers, consolidating them in one place, and can import existing bans from the BF3 Ban Manager plugin's tables. Full documentation below. Automated Challenge System with Rewards. The challenge system in AdKats is designed to be a multi-server stats-driven way to give players new goals with rewards. You can set up almost any combination of damage types or weapons to be used by players, in multiple tiers. BF3/BF4 "Hacker-Checker" with Whitelist. Battlelog stats can be polled for players in the server, issuing automatic bans for damage mods, aimbots, magic bullet, and several others. The LIVE system can detect damage mods and magic bullet from a single round of play. DPS checks are enabled by default, with others available after a few clicks. Surrender Vote System. When enabled, if players are stuck in their base with no options, they can vote to end the round with the current winning team as winner. Auto-Surrender/Auto-Nuke System. This uses ticket loss rates to detect where teams are on the map, specifically with how many flags are captured. If a team is being base-camped, it can either automatically end the round with current winner, or nuke the team who is causing the base-camp. Optimal values for Metro 2014 and Operation Locker are available, for both surrender and nuke options. Automatic Updates. AdKats automatically updates itself when stable releases are made, only requiring a Procon instance reboot to run updated versions. This can be disabled if desired, but is required if running TEST versions. Ping Enforcer. Automated kick system based on ping, with moving average calculation, modifiers based on time of day and server population, customizable messages, logged kicks, and manual ping options. AFK Manager. Automated kick system based on player AFK time, with manual kick command. Customizable durations, and option to ignore chat messages counting toward active time. Internal SpamBot with Whitelist. SpamBot with options for simultaneous say, yell, and tell. Customizable intervals between each type of message, and ability to whitelist players/admins from seeing spambot messages. Commander Manager. Commanders can cause team imbalance when servers are in low population. This manager can forbid commanders before a certain player count is active. Cross-Server Player Messaging. Private conversations between players can operate not only within the same server, but will work between any online server in the database, and even between any AdKats supported game. Admin Assistants. When fully used this can turn your regular playerbase into a human autoadmin. Trusted players fill the gaps normal autoadmins don't see by utilizing the report system and keeping your server under control even when normal admins are offline. Email Notification System. Email addresses can be added to every user, and once enabled they will receive emails for player reports and admin calls. Fuzzy Player Name Completion. Fully completes partial or misspelled player names. I've been consistently able to find almost any player only a few characters from their name. Can also fetch players who have left the server, are in another server of yours on the same database, or have been in your servers at any point in time. Player Muting. Players can be muted if necessary, giving warnings and kicks if they talk. Automatic mute in specific cases like lanuage can be orchestrated by other plugins like Insane limits. Player Joining. Player's squads can be joined via command, and locked squads can be unlocked for admin entry. Player Locking. Players can be locked from admin commands for a specific timeout, the main purpose is if a certain admin is handling them (checking stats for cheat detection, records, etc.) they shouldn't be interrupted by another admin acting on the player. Player Assist. Player's want to play with their friends, but you don't want to imbalance the teams_ The assist command lets any player join the weak team to help them out and squad up with friends without hurting server balance. Yell/Say Pre-Recording. Use numbers to reference predefined messages. Avoid typing long reasons or messages. e.g. /kill player 3 Server Rule Management. Server rules can be listed, requests for rules logged, rules targeted at other players, and rules can be distributed between servers automatically. External Controller API. AdKats can be controlled from outside the game through systems like the BFAdminCP and through other plugins like Insane Limits. For example, you can issue AdKats punish commands from Insane Limits or ProconRulz and have them logged against the player's profile like any other admin command. Internal Implementation of TeamSwap. Queued move system for servers that are consistently full, players can be queued to move to full teams once a slot opens. Metabans Support. When using ban enforcer all bans can be submitted to metabans and removed if the player is unbanned. Editable In-Game Commands. Command text, logging options, chat access types, and enable options can be edited to suit your needs. Full Logging. All admin activity is tracked via the database per your custom settings for every command, so holding your admins accountable for their actions is quick and painless. If you are using the BFAdminCP nobody but your highest admins will need manual Procon access. Setting Lock. The settings page in AdKats can be locked with a password. This means even admins with access to plugin settings can be blocked from changes using the password. Performance. All actions, messaging, database communications, and command parsing take place on their own threads, minimizing performance impacts. New Extension! Click below to enforce loadouts on-spawn! AdKats Release Notes: https://github.com/AdKats/AdKats/blob/master/CHANGELOG.md#7604-12-jan-2020 I hope you enjoy the plugin. While using this plugin, two players, ColColonCleaner, and PhirePhrey will be added to your server's reserved slot list. If you have any questions, please comment here.
  5. My settings example frequency same as the factions don't change for me. Does the new procon ver cause that?
  6. Hello guys first happy new year to all i use this code , can some one change it for me ! i need make 6 limited when player kill 6 with explosive he got kick that mean 5 warning 6kill kick if (Regex.Match(kill.Weapon, @"(_:SMK|FLASH|Shield)", RegexOptions.IgnoreCase).Success) return false; // show warnings at procon chattab // yes = true | no = false bool bShowToProcon = true; String kCounter = killer.Name + "_NoExplosives_Count"; TimeSpan time = TimeSpan.FromSeconds(5); // Activations within 5 seconds count as 1 int warnings = 0; if (plugin.RoundData.issetInt(kCounter)) warnings = plugin.RoundData.getInt(kCounter); if (warnings == 0) { String globalMessage = killer.FullName + " killed for explosive kill on " + plugin.FriendlyMapName(server.MapFileName) + "!"; plugin.SendGlobalMessage(globalMessage); if (bShowToProcon) plugin.PRoConChat("NoExplosives > Say > " + globalMessage); String privateMessage = "WARNING (1/3)! Explosives are not allowed on " + plugin.FriendlyMapName(server.MapFileName) + "! Read our rules!"; plugin.SendPlayerYell(killer.Name, privateMessage, 10); if (bShowToProcon) plugin.PRoConChat("NoExplosives > Yell[10] > " + killer.Name + " > " + privateMessage); plugin.KillPlayer(killer.Name, 1); plugin.RoundData.setInt(kCounter, warnings+1); return false; } if (limit.Activations(killer.Name, time) > 1) return false; if (warnings == 1) { String globalMessage = killer.FullName + " killed for explosive kill on " + plugin.FriendlyMapName(server.MapFileName) + "!"; plugin.SendGlobalMessage(globalMessage); if (bShowToProcon) plugin.PRoConChat("NoExplosives > Say > " + globalMessage); String privateMessage = "FINAL WARNING (2/3)! Explosives are not allowed on " + plugin.FriendlyMapName(server.MapFileName) + "! Read our rules!"; plugin.SendPlayerYell(killer.Name, privateMessage, 10); if (bShowToProcon) plugin.PRoConChat("NoExplosives > Yell[10] > " + killer.Name + " > " + privateMessage); plugin.KillPlayer(killer.Name, 1); plugin.RoundData.setInt(kCounter, warnings+1); } else if (warnings >= 2) { plugin.KickPlayerWithMessage(player.Name, plugin.R("Kicked for ignoring warnings and killing with explosives!")); } plugin.RoundData.setInt(kCounter, warnings+1); return false;
  7. 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 !rulesIt 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
  8. View File On-Spawn Loadout Enforcer for Infantry/Vehicles - AdKatsLRT Overview All infantry and vehicle loadouts/equipment in Battlefield 4 can be denied on-spawn using this plugin, with customizable messages for each item. Vehicle loadouts and equipment can be enforced on spawn for everyone, or on kill with specific vehicles. Settings allow for enforcement of problem players only, or all players, with per-item gradation of that severity. Basic Enforce every infantry item (any primary, secondary, attachments for either, gadgets, knifes, and grenades) in the game on-spawn. Enforce every vehicle item (primaries, secondaries, countermeasures, optics, and gunner options) in the game, on-spawn. Map/Mode specific enforcement options for mixed-mode servers are available. Any update made to the game's weapons are automatically imported and made available, so if DICE changes or adds weapons, they are immediately enforceable. Players notified and thanked when they fix their loadouts after being killed. Customizable kill messages for each denied item, with combined messages and details if more than one is spawned in the same loadout. Statistics on enforcement, including percent of players enforced, percent killed for enforcement, percent who fixed their loadouts after kill, and percent who quit the server without fixing their loadouts after kill. With AdKats Two levels of enforcement, allowing multiple levels of severity for each item. In-game commands to call more strict loadout enforcement on specific players. Using the reputation system, reputable players are optionally not forced to change their loadouts, as we know they are not going to use them. Admins are optionally whitelisted from spawn enforcement, but still fall under trigger enforcement if marked or punished. Other plugins can call loadout checks and enforcement, so it can enhance your current autoadmin. Development by Daniel J. Gradinjan (ColColonCleaner) If you find any bugs, please inform me about them on the MyRCON forums and they will be fixed ASAP. Procon, and optionally AdKats. Basic functions only require Procon, however, for advanced functions, it requires AdKats 6.9.0.0 or later to be installed and running. Separated Layer IPs. This is a battlelog intensive plugin, do not run it on more than one battlefield server from the same Procon layer IP address. If you have multiple servers to enforce, you must run the plugin from different Procon layer IP addresses. If you do not heed this warning, your layers run the risk of being temporarily IP banned from battlelog. Optionally Install AdKats. AdKatsLRT can run independently from the AdKats base plugin, but certain advanced functions cannot be used as a result. To install the latest version of AdKats, view the AdKats Install Instructions. After install make sure you are running version 6.9.0.0 or later. Download and install AdKatsLRT. The plugin is installed like any other procon plugin. Enable AdKatsLRT. AdKatsLRT will start and fetch required information, then wait for the first player list response from either AdKats or the server. Once that comes through, it will complete startup and loadout enforcement will be online. Enjoy your new admin tool! If you have any problems installing AdKatsLRT please let me know on the MyRCON forums and I'll respond promptly. All instances of AdKatsLRT are tracked once installed. Item Library Every infantry/Vehicle item in the game (about 3500 items), can be enforced here. The settings are split into several sections; Weapons, Weapon Accessories, Gadgets, and Vehicle Weapons/Unlocks, in that order. Loadout Processing Deciding Enforcement Type The gist of it for infantry: Deny on trigger denies that weapon/accessory for problem players and players you've manually marked, deny on spawn denies that weapon for everyone except admins and reputable players. The gist of it for vehicles: By default, enforcement is on kill with specific vehicles. This is important because not everyone uses vehicles, so only those players using restricted vehicles should have their loadouts enforced for those vehicles. Optionally you can enforce on spawn for vehicle loadouts, regardless, which is not advised but is available as an option. Details for infantry: Loadouts have several reasons for being checked; A player spawns, gets reported, gets punished, gets marked, or has more than X (configurable) infraction points. Any of these instances will call a loadout check, and the reason for checking them changes the way the enforcement works. When running loadout enforcement for a specific player, the reason, and action if invalid, is first decided. The following are results for specific reasons, in order of priority: If a player was marked they are set under trigger enforcement and will be slain for invalid loadout of any kind. If a player is punished they are set under trigger enforcement and will be slain for invalid loadout of any kind. If a player was reported and their reputation is non-positive they are set under trigger enforcement and will be slain for invalid loadout of any kind. If they are slain due to a report that report is automatically accepted. If a player has more than X (configurable) infraction points they are set under trigger enforcement and will be slain for invalid loadout of any kind. If none of the above checks are hit, are not reputable, and are not an admin, they are set under spawn enforcement. Secondary checks are customizable. Informing and Acting If a player is about to be slain for loadout enforcement, regardless of enforcement type, they are shown two messages. The first is a generic message containing all denied weapons they have in their loadout "playername please remove [denied weapons] from your loadout". This messages is sent using private SAY. After that, the specific messages written by the admin for each denied item is displayed. These customizable messages are found in setting sections 8A and 8B, once denied items are selected. These messages are sent using private TELL. Immediately after informing the player of denied items in their loadout, they are admin killed. If they are under manual trigger enforcement, admins are notified of their demise, all other messages are private. Thank you messages are given to players who fix their loadouts. If a player is under trigger enforcement, admins are notified that they fixed their loadout. Debug Messages Setting your debug level to at least 2 will display statistics in the console when stats change. The stats available are percent under loadout enforcement (should be nearly 100%), percent killed for loadout enforcement, percent who fixed their loadouts after kill, and percent who quit the server without fixing after being killed. Certain commands in AdKats are modified by this plugin. The changes to those commands are listed below. Command Default Text Changes Punish Player punish Punish works as normal, but also initiates trigger level enforcement on the target player for the duration the plugin is online. Mark Player mark Instead of marking a player for leave notification only, it also initiates trigger level enforcement on the target player for the duration the plugin is online. Report Player report Reports initiate trigger level enforcement on targeted players with non-positive reputation. If the reported player has invalid items in their loadout, the report is automatically accepted, and admins notified of such. Call Admin admin Same changes as Report Player. 0. Instance Settings: 'Integrate with AdKats' - Whether to integrate functions with AdKats. When enabled this unlocks more setting options. 'Spawn Enforce Admins' - Viewable when integrating with AdKats. Adds admins to spawn enforcement. 'Spawn Enforce Reputable Players' - Viewable when integrating with AdKats. Adds reputable players (> 15 rep) to spawn enforcement. 'Trigger Enforce Minimum Infraction Points' - Viewable when integrating with AdKats. Sets the minimum infraction point count to automatically add problem players to trigger level enforcement. 1. Display Settings: 'Display Preset Settings' - When enabled, the 'Preset Settings' section will be displayed. 'Display Map/Mode Settings' - When enabled, the 'Map/Mode Settings' section will be displayed. 'Display Weapon Settings' - When enabled, the 'Weapons' section will be displayed. 'Display Weapon Accessory Settings' - When enabled, the 'Weapon Accessories' section will be displayed. 'Display Gadget Settings' - When enabled, the 'Gadgets' section will be displayed. 'Display Vehicle Settings' - When enabled, the 'Vehicle Weapons/Unlocks' section will be displayed. 2. Preset Settings: 'Coming Soon' - This setting block will soon contain settings for presets, like 'No Frag Rounds', or 'No Explosives'. 3. Map/Mode Settings: 'Enforce on Specific Maps/Modes Only' - When enabled, the Map/Mode selection settings are displayed. Loadout enforcement will only be enabled on the selected maps. '*MapModeIdentifier Enforce?' - When enabled, the selected Map/Mode will be included in loadout enforcement. 4. Weapons: '*WeaponIdentifier Allow on trigger?' - Viewable when integrating with AdKats. Whether this item should be allowed/denied when a player is under trigger level enforcement. '*WeaponIdentifier Allow on spawn?' - Appears when a weapon is denied under trigger enforcement, or not using AdKats integration. Whether this item should be allowed/denied when a player is under spawn level enforcement. 5. Weapon Accessories: '*AccessoryIdentifier Allow on trigger?' - Viewable when integrating with AdKats. Whether this item should be allowed/denied when a player is under trigger level enforcement. '*AccessoryIdentifier Allow on spawn?' - Appears when a weapon is denied under trigger enforcement, or not using AdKats integration. Whether this item should be allowed/denied when a player is under spawn level enforcement. 6. Gadgets: '*GadgetIdentifier Allow on trigger?' - Viewable when integrating with AdKats. Whether this item should be allowed/denied when a player is under trigger level enforcement. '*GadgetIdentifier Allow on spawn?' - Appears when a weapon is denied under trigger enforcement, or not using AdKats integration. Whether this item should be allowed/denied when a player is under spawn level enforcement. 7. Vehicle Weapons/Unlocks: 'Spawn Enforce all Vehicles' - When enabled, if any player spawns with a vehicle loadout that is invalid it will slay them. When disabled, it will wait for them to use the vehicle before slaying them. '*VehicleIdentifier Allow on kill?' - Whether this item should be allowed/denied when a player kills with the specified vehicle. '*VehicleIdentifier Allow on spawn?' - Appears when the 'Spawn Enforce all Vehicles' setting is enabled. Whether this item should be allowed/denied when a player spawns, regardless of where they are. 8A. Denied Item Kill Messages: '*ItemIdentifier Kill Message' - The specific message sent to players when they are slain for having this item in their loadout. 8B. Denied Item Accessory Kill Messages: '*AccessoryIdentifier Kill Message' - The specific message sent to players when they are slain for having this accessory in their current loadout. 8C. Denied Vehicle Item Kill Messages: '*VehicleItemIdentifier Kill Message' - The specific message sent to players when they are slain for having this item in their vehicle loadout. D99. Debug Settings: 'Debug level' - Indicates how much debug-output is printed to the plugin-console. 0 turns off debug messages (just shows important warnings/exceptions/success), 1 includes kill notifications, 2 includes stats, 3 includes queue information, 4 includes each player's full loadout, and 5 is overly detailed. Submitter ColColonCleaner Submitted 12/24/19 Category Plugins
  9. Hello i use this code (Regex.Match(server.MapFileName, @"(MP_Prison|XP0_Metro)", RegexOptions.IgnoreCase).Success && (Regex.Match(kill.Weapon, @"(AA Mine|M320|_LVG|_HE|_3GL|_Claymore|_AT4|_C4|_FGM148|U_Claymore|U_Grenade_RGO_FIM92|_FLASH|_Flashbang|_GrenadeRGO|_M15|_M224|_M34|_M67|_MGL|_NLAW|_RPG7|_Sa18IGLA|_SLAM|_SMAW|_Claymore|_SRAW|_Starstreak|_Tomahawk|_UCAV|_V40|_XM25|ROADKILL|Death)", RegexOptions.IgnoreCase).Success && !Regex.Match(kill.Weapon, @"(_SMK|_Smoke|_Suicide|_SoldierCollision|_DamageArea)", RegexOptions.IgnoreCase).Success)) all work but there is some explosive not banned like rog can some one added all explosive please big thank !
  10. Prophet731

    Procon Client

    Version 1.5.3.1

    30931 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.
  11. skulls

    BF4DB

    Version 2.0.13

    79 downloads

    Installation There are a few steps to complete before this plugin will be operational. You must first have created an account with us and then claim a server. Once you have a server claimed you will be given an API key. Once you have placed the plugin in your Procon layer, the last step is to set up the plugin with the API key and change any settings you might need. Each of these steps will be outlined below. Claiming Server To claim a server please log in and click Server Tools under the user menu. On the Server Tools page, you can claim new servers and manage existing ones. You will then see a box that contains a unique code each time this page is visited and an input for your server Battlelog GUID. You must have admin access to your servers to claim them. The next step is to use whatever tool you use to manage your server to include the unique code in your server name. This is just temporary and can be changed once you have claimed the server. You do not need to change the entire server name to just the unique code, it only has to be in it somewhere. Once the name has been changed with the correct code, then place your server Battlelog GUID in the field and press Claim. If everything was correct you will have successfully claimed a server. Repeat this process for any or all servers you need to set up the plugin for! Get API Key Once you have a server claimed you will be given an API key to be used with our plugin. To get this key visit your Server page under Settings and click on the API Key button next to the server. A box will pop-up with your API key. This key will never expire and can always be accessed here as long as you have the server claimed. This key will only work for the server it was claimed with. Copy the API key for the next step. BF4DB reserves the right to revoke any API key generated for any server at any time. If a server is deemed to be a "hacked" server or is openly harboring hackers (abusing the whitelist function), then it's API key will be revoked and account owners will be unable to claim additional servers in the future. Setup Plugin You must already have a Procon layer setup and running either hosted remotely or locally. Download the plugin using the links below. It will come in a .zip file and contain two files within. Unzip this and place both the included files in the Plugins\BF4 folder on your Procon layer filesystem. Please refer to the Procon manual or your layer provided for file access. After the files are in place restart your layer. Configuration You will then need to open Procon to enable and configure the plugin. Before enabling please input the given API key and change any settings you may want. When the correct API key for that server is included you may then enable the plugin. Settings API Key: You must claim the server on BF4DB.com to receive an API key for this server. Enable Auto Bans: When set to Yes, any players banned on BF4DB will be removed from your server. Defaults to Yes. Enable Announcements: When set to Yes, player status during verification will be announced in chat. Defaults to Yes. Player Whitelist: Place any player names(one per line) to be excluded from BF4DB checks and server removal. Debug Level: Mainly for BF4DB developers. If you encounter an issue please set to one of the following levels before submitting a bug report. 0: Disabled. Not debugging in the console will occur. 1: Only player information will be logged. 2: Player and server information will be logged. 3: Player, server, and PunkBuster information will be logged. Development For any support or bug reports please visit our forums or use #plugin-support in our discord server. Please include as much information or debugging as you can. Notes If your procon layer host does not allow uploads of .dll files: Rename BF4DB_API.dll to BF4DB_API.cs, then open BF4DB.cs and edit lines 103 and 105 from BF4DB_API.dll to BF4DB_API.cs, save, then proceed to upload the plugin. If you're not sure which line to edit (if your editor doesn't show line numbers), simply search (Ctrl+F) for .dll and change it to .cs. After you upload the plugin, you will need to reboot your Procon layer. License BF4DB Server Protection by skulls is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License. Permissions beyond the scope of this license may be available at https://bf4db.com/tos.
  12. Hello . is there any core or plugins for make Defibrillator 100% when try rev ? well , i mean one click revive 100% not 20%
  13. Version 2.0.2

    19 downloads

    Running on PHP Version 7 This does not work with any version of the BFACP do not try to run this application on that version. Use the latest stable PHP 5.6. Overview The Battlefield Admin Control Panel (BFACP) is a web based admin tool designed to work exclusively with AdKats (v6+) and XpKillers Chat, GUID, Stats and Mapstats Logger (v1.0.0.3). The software is built with the Laravel PHP framework to speed up development time and make my job a lot easier. FAQ Requirements MySQL Database (5.6+) AdKats v6+ XpKillers Chat, GUID, Stats and Mapstats Logger v1.0.0.2+ PHP 5.5+ PHP Mcrypt PHP PDO Features User, Role, and Permission system. Live Scoreboard with chat. Ban Management for AdKats. Detailed player information with graph charts. Server statistics page for each server showing population history, uptime history with data from UptimeRobot, and Mapstats. Metabans support. Report notifications with ability to change alert sounds. Chatlog searching where you can search by multiple players and/or keywords and ability to only show from a certain date/time range. Message of the Day Quick DB Stats overview and more! Download the latest version. Once downloaded unzip it to a temporary folder on your computer. Next open the .env.php file located in the root folder in your favorite text editor. Scroll down to the database settings section and fill in your database connection information. /** * Database Settings */ 'DB_HOST' => 'localhost', 'DB_USER' => 'root', 'DB_PASS' => '', 'DB_NAME' => 'mydatabase', Next we need to create a encryption key. This is IMPORTANT! The default key provided is just a placeholder string and is insecure. I have provided a page where you can get a random 32 character string. I do NOT save these and they are random on each refresh. You can access this page here, scroll down to the CodeIgniter Encryption Keys. Once you have your key open up the file .env.php in the root folder and scroll down till you see the APP_KEY field. Replace the YourSecretKey!!! with the key that was generated. By default it will look like this. /** * Set your app key here */ 'APP_KEY' => 'YourSecretKey!!!' Once completed upload the entire application to your webserver. Once uploaded you will need to modify some file and folder permissions. Change the files and folders permissions under app/storage recursively to 0777. This application was designed to run on a subdomain and not from a folder from the TLD. Make sure to create a subdomain and if possible have domain point to the public folder that's located under the root folder. Now load up application in your web browser and it will begin the process of creating the tables. This process will take a few seconds to run on first load. When it completed you should see the dashboard. Default login Username: admin Password: password You can change the default username and password by clicking on Site Management > Users > Admin Installing from the command line This method is only for those who have shell access to their web server or VPS. This will download and extract the files to your current directory. Make sure it's an empty directory. If you have git installed you can just run the following command to install it. You must have composer and php command line installed. Composer Method (preferred) composer create-project --prefer-dist --no-scripts --keep-vcs adkgamers/bfadmincp . Git Method git clone https://github.com/Prophet731/BFAdminCP.git . composer install --no-scripts This will clone and install the dependencies need for the BFACP to work. This will checkout the master branch which is the stable version. If you would like to run the develop version you will need to run git checkout develop before you issue the composer command. To update it all you will need to do is run git pull and it will pull the latest version on the current branch (master or develop). To make this an automated process you can create a cron job for it. * * * * * cd /path/to/bfacp; git pull >/dev/null 2>&1
  14. Version 2.0.9.0

    18 downloads

    Overview All infantry and vehicle loadouts/equipment in Battlefield 4 can be denied on-spawn using this plugin, with customizable messages for each item. Vehicle loadouts and equipment can be enforced on spawn for everyone, or on kill with specific vehicles. Settings allow for enforcement of problem players only, or all players, with per-item gradation of that severity. Basic Enforce every infantry item (any primary, secondary, attachments for either, gadgets, knifes, and grenades) in the game on-spawn. Enforce every vehicle item (primaries, secondaries, countermeasures, optics, and gunner options) in the game, on-spawn. Map/Mode specific enforcement options for mixed-mode servers are available. Any update made to the game's weapons are automatically imported and made available, so if DICE changes or adds weapons, they are immediately enforceable. Players notified and thanked when they fix their loadouts after being killed. Customizable kill messages for each denied item, with combined messages and details if more than one is spawned in the same loadout. Statistics on enforcement, including percent of players enforced, percent killed for enforcement, percent who fixed their loadouts after kill, and percent who quit the server without fixing their loadouts after kill. With AdKats Two levels of enforcement, allowing multiple levels of severity for each item. In-game commands to call more strict loadout enforcement on specific players. Using the reputation system, reputable players are optionally not forced to change their loadouts, as we know they are not going to use them. Admins are optionally whitelisted from spawn enforcement, but still fall under trigger enforcement if marked or punished. Other plugins can call loadout checks and enforcement, so it can enhance your current autoadmin. Development by Daniel J. Gradinjan (ColColonCleaner) If you find any bugs, please inform me about them on the MyRCON forums and they will be fixed ASAP. Procon, and optionally AdKats. Basic functions only require Procon, however, for advanced functions, it requires AdKats 6.9.0.0 or later to be installed and running. Separated Layer IPs. This is a battlelog intensive plugin, do not run it on more than one battlefield server from the same Procon layer IP address. If you have multiple servers to enforce, you must run the plugin from different Procon layer IP addresses. If you do not heed this warning, your layers run the risk of being temporarily IP banned from battlelog. Optionally Install AdKats. AdKatsLRT can run independently from the AdKats base plugin, but certain advanced functions cannot be used as a result. To install the latest version of AdKats, view the AdKats Install Instructions. After install make sure you are running version 6.9.0.0 or later. Download and install AdKatsLRT. The plugin is installed like any other procon plugin. Enable AdKatsLRT. AdKatsLRT will start and fetch required information, then wait for the first player list response from either AdKats or the server. Once that comes through, it will complete startup and loadout enforcement will be online. Enjoy your new admin tool! If you have any problems installing AdKatsLRT please let me know on the MyRCON forums and I'll respond promptly. All instances of AdKatsLRT are tracked once installed. Item Library Every infantry/Vehicle item in the game (about 3500 items), can be enforced here. The settings are split into several sections; Weapons, Weapon Accessories, Gadgets, and Vehicle Weapons/Unlocks, in that order. Loadout Processing Deciding Enforcement Type The gist of it for infantry: Deny on trigger denies that weapon/accessory for problem players and players you've manually marked, deny on spawn denies that weapon for everyone except admins and reputable players. The gist of it for vehicles: By default, enforcement is on kill with specific vehicles. This is important because not everyone uses vehicles, so only those players using restricted vehicles should have their loadouts enforced for those vehicles. Optionally you can enforce on spawn for vehicle loadouts, regardless, which is not advised but is available as an option. Details for infantry: Loadouts have several reasons for being checked; A player spawns, gets reported, gets punished, gets marked, or has more than X (configurable) infraction points. Any of these instances will call a loadout check, and the reason for checking them changes the way the enforcement works. When running loadout enforcement for a specific player, the reason, and action if invalid, is first decided. The following are results for specific reasons, in order of priority: If a player was marked they are set under trigger enforcement and will be slain for invalid loadout of any kind. If a player is punished they are set under trigger enforcement and will be slain for invalid loadout of any kind. If a player was reported and their reputation is non-positive they are set under trigger enforcement and will be slain for invalid loadout of any kind. If they are slain due to a report that report is automatically accepted. If a player has more than X (configurable) infraction points they are set under trigger enforcement and will be slain for invalid loadout of any kind. If none of the above checks are hit, are not reputable, and are not an admin, they are set under spawn enforcement. Secondary checks are customizable. Informing and Acting If a player is about to be slain for loadout enforcement, regardless of enforcement type, they are shown two messages. The first is a generic message containing all denied weapons they have in their loadout "playername please remove [denied weapons] from your loadout". This messages is sent using private SAY. After that, the specific messages written by the admin for each denied item is displayed. These customizable messages are found in setting sections 8A and 8B, once denied items are selected. These messages are sent using private TELL. Immediately after informing the player of denied items in their loadout, they are admin killed. If they are under manual trigger enforcement, admins are notified of their demise, all other messages are private. Thank you messages are given to players who fix their loadouts. If a player is under trigger enforcement, admins are notified that they fixed their loadout. Debug Messages Setting your debug level to at least 2 will display statistics in the console when stats change. The stats available are percent under loadout enforcement (should be nearly 100%), percent killed for loadout enforcement, percent who fixed their loadouts after kill, and percent who quit the server without fixing after being killed. Certain commands in AdKats are modified by this plugin. The changes to those commands are listed below. Command Default Text Changes Punish Player punish Punish works as normal, but also initiates trigger level enforcement on the target player for the duration the plugin is online. Mark Player mark Instead of marking a player for leave notification only, it also initiates trigger level enforcement on the target player for the duration the plugin is online. Report Player report Reports initiate trigger level enforcement on targeted players with non-positive reputation. If the reported player has invalid items in their loadout, the report is automatically accepted, and admins notified of such. Call Admin admin Same changes as Report Player. 0. Instance Settings: 'Integrate with AdKats' - Whether to integrate functions with AdKats. When enabled this unlocks more setting options. 'Spawn Enforce Admins' - Viewable when integrating with AdKats. Adds admins to spawn enforcement. 'Spawn Enforce Reputable Players' - Viewable when integrating with AdKats. Adds reputable players (> 15 rep) to spawn enforcement. 'Trigger Enforce Minimum Infraction Points' - Viewable when integrating with AdKats. Sets the minimum infraction point count to automatically add problem players to trigger level enforcement. 1. Display Settings: 'Display Preset Settings' - When enabled, the 'Preset Settings' section will be displayed. 'Display Map/Mode Settings' - When enabled, the 'Map/Mode Settings' section will be displayed. 'Display Weapon Settings' - When enabled, the 'Weapons' section will be displayed. 'Display Weapon Accessory Settings' - When enabled, the 'Weapon Accessories' section will be displayed. 'Display Gadget Settings' - When enabled, the 'Gadgets' section will be displayed. 'Display Vehicle Settings' - When enabled, the 'Vehicle Weapons/Unlocks' section will be displayed. 2. Preset Settings: 'Coming Soon' - This setting block will soon contain settings for presets, like 'No Frag Rounds', or 'No Explosives'. 3. Map/Mode Settings: 'Enforce on Specific Maps/Modes Only' - When enabled, the Map/Mode selection settings are displayed. Loadout enforcement will only be enabled on the selected maps. '*MapModeIdentifier Enforce?' - When enabled, the selected Map/Mode will be included in loadout enforcement. 4. Weapons: '*WeaponIdentifier Allow on trigger?' - Viewable when integrating with AdKats. Whether this item should be allowed/denied when a player is under trigger level enforcement. '*WeaponIdentifier Allow on spawn?' - Appears when a weapon is denied under trigger enforcement, or not using AdKats integration. Whether this item should be allowed/denied when a player is under spawn level enforcement. 5. Weapon Accessories: '*AccessoryIdentifier Allow on trigger?' - Viewable when integrating with AdKats. Whether this item should be allowed/denied when a player is under trigger level enforcement. '*AccessoryIdentifier Allow on spawn?' - Appears when a weapon is denied under trigger enforcement, or not using AdKats integration. Whether this item should be allowed/denied when a player is under spawn level enforcement. 6. Gadgets: '*GadgetIdentifier Allow on trigger?' - Viewable when integrating with AdKats. Whether this item should be allowed/denied when a player is under trigger level enforcement. '*GadgetIdentifier Allow on spawn?' - Appears when a weapon is denied under trigger enforcement, or not using AdKats integration. Whether this item should be allowed/denied when a player is under spawn level enforcement. 7. Vehicle Weapons/Unlocks: 'Spawn Enforce all Vehicles' - When enabled, if any player spawns with a vehicle loadout that is invalid it will slay them. When disabled, it will wait for them to use the vehicle before slaying them. '*VehicleIdentifier Allow on kill?' - Whether this item should be allowed/denied when a player kills with the specified vehicle. '*VehicleIdentifier Allow on spawn?' - Appears when the 'Spawn Enforce all Vehicles' setting is enabled. Whether this item should be allowed/denied when a player spawns, regardless of where they are. 8A. Denied Item Kill Messages: '*ItemIdentifier Kill Message' - The specific message sent to players when they are slain for having this item in their loadout. 8B. Denied Item Accessory Kill Messages: '*AccessoryIdentifier Kill Message' - The specific message sent to players when they are slain for having this accessory in their current loadout. 8C. Denied Vehicle Item Kill Messages: '*VehicleItemIdentifier Kill Message' - The specific message sent to players when they are slain for having this item in their vehicle loadout. D99. Debug Settings: 'Debug level' - Indicates how much debug-output is printed to the plugin-console. 0 turns off debug messages (just shows important warnings/exceptions/success), 1 includes kill notifications, 2 includes stats, 3 includes queue information, 4 includes each player's full loadout, and 5 is overly detailed.
  15. skulls

    BF4DB

    BF4DB View File Installation There are a few steps to complete before this plugin will be operational. You must first have created an account with us and then claim a server. Once you have a server claimed you will be given an API key. Once you have placed the plugin in your Procon layer, the last step is to set up the plugin with the API key and change any settings you might need. Each of these steps will be outlined below. Claiming Server To claim a server please log in and click Server Tools under the user menu. On the Server Tools page, you can claim new servers and manage existing ones. You will then see a box that contains a unique code each time this page is visited and an input for your server Battlelog GUID. You must have admin access to your servers to claim them. The next step is to use whatever tool you use to manage your server to include the unique code in your server name. This is just temporary and can be changed once you have claimed the server. You do not need to change the entire server name to just the unique code, it only has to be in it somewhere. Once the name has been changed with the correct code, then place your server Battlelog GUID in the field and press Claim. If everything was correct you will have successfully claimed a server. Repeat this process for any or all servers you need to set up the plugin for! Get API Key Once you have a server claimed you will be given an API key to be used with our plugin. To get this key visit your Server page under Settings and click on the API Key button next to the server. A box will pop-up with your API key. This key will never expire and can always be accessed here as long as you have the server claimed. This key will only work for the server it was claimed with. Copy the API key for the next step. BF4DB reserves the right to revoke any API key generated for any server at any time. If a server is deemed to be a "hacked" server or is openly harboring hackers (abusing the whitelist function), then it's API key will be revoked and account owners will be unable to claim additional servers in the future. Setup Plugin You must already have a Procon layer setup and running either hosted remotely or locally. Download the plugin using the links below. It will come in a .zip file and contain two files within. Unzip this and place both the included files in the Plugins\BF4 folder on your Procon layer filesystem. Please refer to the Procon manual or your layer provided for file access. After the files are in place restart your layer. Configuration You will then need to open Procon to enable and configure the plugin. Before enabling please input the given API key and change any settings you may want. When the correct API key for that server is included you may then enable the plugin. Settings API Key: You must claim the server on BF4DB.com to receive an API key for this server. Enable Auto Bans: When set to Yes, any players banned on BF4DB will be removed from your server. Defaults to Yes. Enable Announcements: When set to Yes, player status during verification will be announced in chat. Defaults to Yes. Player Whitelist: Place any player names(one per line) to be excluded from BF4DB checks and server removal. Debug Level: Mainly for BF4DB developers. If you encounter an issue please set to one of the following levels before submitting a bug report. 0: Disabled. Not debugging in the console will occur. 1: Only player information will be logged. 2: Player and server information will be logged. 3: Player, server, and PunkBuster information will be logged. Development For any support or bug reports please visit our forums or use #plugin-support in our discord server. Please include as much information or debugging as you can. Notes If your procon layer host does not allow uploads of .dll files: Rename BF4DB_API.dll to BF4DB_API.cs, then open BF4DB.cs and edit lines 103 and 105 from BF4DB_API.dll to BF4DB_API.cs, save, then proceed to upload the plugin. If you're not sure which line to edit (if your editor doesn't show line numbers), simply search (Ctrl+F) for .dll and change it to .cs. After you upload the plugin, you will need to reboot your Procon layer. License BF4DB Server Protection by skulls is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License. Permissions beyond the scope of this license may be available at https://bf4db.com/tos. Submitter Prophet731 Submitted 12/24/19 Category Plugins  
  16. Hello guys can someone help me at first thank you i need setting for auto nuke , i have server Metro + locker ticket 3000 . so , i have problem base rape i make so many setting but it not work i hope some one give me good setting thank you !
  17. 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. Submitter Prophet731 Submitted 12/24/19 Category Procon  
  18. Hello guys , i use insane-limits i need help about explosives limted first kill only warning second kill player The third time kick player is there code for this ? thank you
  19. Hello i install adkats and run it but adkats kick some player why ? how u can stop it ? please i need help if anyone know how stop it
  20. So as i said i need help with AdKads.When you will help me and it will work as i want i can send you 5 Eur Steam Gift Card Contact:Discord name-TheTomik #0478 :Or here in comments(chat) I will appreciate every help!
  21. Originally Posted by ty_ger07*: The full featured stats webpage! BF4 Stats Web Page Overview web_stats_index.jpg web_stats_demo.jpg web_stats_banner.jpg Features: - Easy setup. - Individual server or combined server stats. - Country stats. - Map stats. - Player stats. - Weapon stats. - Dog tag stats. - Game server stats. - Live scoreboard. - Top players list / leaderboard. - Player name search. - Top players of the Week. - Suspicious players search. - Server chat log. - Stats signature images. - Gametracker-style server banners. - Battlelog theme. Demo https://egc-la.evga.com/battlefield/index.php Prerequisites This webpage code requires the use of a stats database which is created by XpKiller's BF4 Chat, GUID, Stats and Mapstats Logger Plugin* version 1.0.0.2 or newer. If you need help with XpKiller's stats logging plugin, you must seek assistance in XpKiller's thread. For best compatibility with this code, use the following settings in XpKiller's PRoCon logging plugin: "Enable Statslogging_" : Yes "Enable Weaponstats_" : Yes "Enable Livescoreboard in DB_" : Yes "tableSuffix" : None (empty) "MapStats ON_" : Yes "Session ON_" : Yes "Save Sessiondata to DB_" : Yes "Log playerdata only (no playerstats)_" : No This webpage code also requires that you have access to a web server running a modern version of PHP and that you have permission to modify files on the web server. Additional Info GitHub: http://tyger07.github.io/BF4-Server-Stats Installation Steps: Download the following file: https://github.com/tyger07/BF4-Serve...zipball/master Extract the files. You may change the appearance of the page by modifying the stats.css file in the common folder. Fill in the required parameters before using this code. You must place the necessary data between the the following single quotation marks (''). Note: You may not include single quotation marks (') in the following fields. For instance, you may not call your clan 'Ty_ger07's Clan' as it will create a PHP compilation error. For example, this would not work: You must use a PHP delimiter if you wish to use single quotes within the following fields.For example, this would work: You must fill in the following information in the config.php file found in the config folder 1) Input your stats database host, stats database user name, stats database password, and stats database name. Code: // DATABASE INFORMATION DEFINE('HOST', ''); // database host address DEFINE('PORT', '3306'); // database port - default is 3306 DEFINE('NAME', ''); // database name DEFINE('USER', ''); // database user name - sometimes the same as the database name DEFINE('PASS', ''); // database passwordFor example: Note: Some web server providers (such as GoDaddy) use the same value for database name and database user name. 2) Input your clan name as you would like it to appear in the stats pages. Code: // CLAN NAME $clan_name = ''; // your gaming clan or organization nameFor example: 3) Input your desired banner image URL if you want one other than the default to be displayed. Code: // PAGE BANNER $banner_image = './images/bf4-logo.png'; // your desired page banner 4) Enter the URL which you would like users to redirect to if they click your banner image. Code: // BANNER LINK $banner_url = 'http://tyger07.github.io/BF4-Server-Stats/'; // where clicking the banner will take youEnjoy! (if you want to donate, ask me how) Changelog: Refer to: https://github.com/tyger07/BF4-Serve...commits/master
  22. Hello guys i need some code please ( !killme only for admin ) (!moveme only for admin ) change game ticket game mood only QC sorry for bad english
  23. Hallo, ich habe über Nitrado einen Battlefield 4 Server und nutze eigl. den Procon- Layer um die Maps zu wechseln usw.. Seit einiger Zeit bekomme ich allerdings keine Verbindung mehr.. der Nitrado Support hat auch keine Ahnung warum.. Kann mir hier vielleicht jemand helfen? ich nutze die neuste version von Procon die 1.5.1.1
  24. Hello Community, is there a plugin with includes the !assist command excluding AdKarts. I wont use 99% of the things that AdKarts offer, I only need the !assist command. Is there any alternative to it? Thanks for your help. Odiin
×
×
  • 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.