BF 3 Rulz plugin required

[Sorock]

Hello everyone,

Rented a server and trying to make it the way I would like with my own rules.

Not sure how it works here , but long story short would like to ask if someone maybe have or could create plugin? 

Things like:

No explo (c4,nades,rpg's etc)

No shotguns 

No claymores

in a result kick 2x 3 time ban for 1 hour.

and so on.... :) 

what the price would be of course it has to work and I would give my rules I would like to be implemented.

Thanks

[Hedius]

On 12/31/2021 at 4:16 PM, Sorock said:

Hello everyone,

Rented a server and trying to make it the way I would like with my own rules.

Not sure how it works here , but long story short would like to ask if someone maybe have or could create plugin? 

Things like:

No explo (c4,nades,rpg's etc)

No shotguns 

No claymores

in a result kick 2x 3 time ban for 1 hour.

and so on....  

what the price would be of course it has to work and I would give my rules I would like to be implemented.

Thanks

You can use the AdKats explosives limiter to enforce this.

[Sorock]

thanks for your reply.

 

Is it free to download? if yes , could I get a download link for it please?

Thanks

[Hedius]

Just now, Sorock said:

thanks for your reply.

 

Is it free to download? if yes , could I get a download link for it please?

Thanks

Exactly follow the install instructions:

https://github.com/AdKats/AdKats

 

WARNINGS. Read these before install.

Running AdKats on a Linux environment is not advised or fully supported. Testing on linux environments has been limited for AdKats. Some issues have been mitigated, namely issues with connecting over HTTPS for plugin documentation, updates, and startup, but this was necessary because the plugin wouldn't start otherwise. However, beyond that there has been very little full fledged testing on linux environments for this plugin, and there are so many facets of the plugin now I cannot guarantee functionality on that platform.

DO NOT run more than one instance of AdKats on a single procon layer at the same time. Procon provides the ability to have a single layer monitor multiple servers at the same time, which is normally a good thing. However, over the years AdKats has grown larger than procon itself logic-wise and running multiple instances of AdKats on the same process can result in heavy performance issues and instability. Do not use procon's multiple-server-per-layer functionality unless only ONE of the servers on the layer has AdKats running. Each server should have its own dedicated layer when using this plugin. Splitting off AdKats into its own admin tool separate from procon has been brought up many times but the effort required at this point would not be worth the benefit.

INSTALL INSTRUCTIONS.

1. Install XpKiller's Stat logger plugin. Download and install the latest universal version of XpKiller's Procon Chat, GUID, Stats and Mapstats Logger. Make sure stat logger is running without error for a few minutes after its own installation BEFORE you attempt to do anything with AdKats installation. It needs to add an entry to the tbl_server table before AdKats can properly start up. If you are already running the BF3 only version of stat logger, that is fine, but the universal version is preferred for full functionality.
2. GO BACK TO STEP 1 AND INSTALL STAT LOGGER. Far too many people have posted issues because they refuse to follow instructions. DO NOT attempt to install AdKats until stat logger is running without issue.
3. Set up the database. Run the contents of the AdKats Database Setup Script on your database, on the same schema stat logger uses. You can do this via PHPMyAdmin or through a client such as MySQL Workbench, either will work just fine. You can use the same database/schema for all of your servers, you don't need a separate database for each server. WARNING: If you already have AdKats installed and running this script will completely wipe your existing data for the plugin and all of your settings. The script must be run by an account with permissions to create tables, triggers, and stored procedures.
4. Download the plugin. Download the Latest Stable Release of AdKats. If you want to try the latest features/fixes which aren't part of the stable release yet then just use the /pupdate command once your instance of AdKats is running, then reboot your procon layer.
5. Add the plugin to Procon. Add the plugin file (AdKats.cs) to Procon as you would any other, in either the plugins/BF3 or plugins/BF4 folder depending on which game your layer is running on. No other files are required on the layer side, only the AdKats.cs file in the proper location according to your game.
6. Enter database credentials. All database connection information must be entered in the settings tab before AdKats can run. The plugin must be able to create/modify/use tables and their data. Using the same credentials as your stat logger plugin should be sufficient.
7. Enable AdKats. AdKats will confirm all dependencies and show startup information in the console. If startup completes and says the plugin is running then all is well. AdKats will automatically update itself with new stable patches and releases. If you want to update manually just use the /pupdate command. Enjoy your new admin tool!

If you have any problems installing AdKats please let me know on the MyRCON forums or on Github as an issue and I'll respond promptly.

---

[Hedius]

FYI: AdKats is an extremely complex plugin. so has endless features.

The manual exactly describes every aspect of the plugin.

C31. Weapon Limiter Settings:

• 'Use NO EXPLOSIVES Limiter' - Whether to enable the internal no explosives limiter.
• 'NO EXPLOSIVES Weapon String' - List of weapon codes or partial weapon codes that will cause punishment for a no explosive server.
• 'NO EXPLOSIVES Exception String' - Any weapon code or partial weapon code previously matched by 'no explosive weapon string' but also matching this setting, will block action on that item. Useful for weapons like the ones ending in SHG, which in BF4 is the dart variant of the M26/M320.
• 'Use Grenade Cook Catcher' - When the no explosives limiter is enabled, having this setting also enabled will cause AdKats to monitor for grenade cookers. In battlefield when you kill someone who is holding or throwing a grenade, the grenade becomes yours. Some players will take advantage of this to get other players acted on by autoadmins on no explosive servers. This script works to mitigate that problem.

 

For the limiter.

The weapon Strings are simple REGEX expressions. (Regular expressions)

E.G.: RPG|C4 would match RPG and C4

You have to add each weapon code (refer to the Config/BF3.def file for all definitions)

 

If this is too complex for your use case then there are premade ProconRulz and InsaneLimits scripts on the forums. (Probably well hidden^^)

[Sorock]

5 hours ago, Hedius said:

You can use the AdKats explosives limiter to enforce this.

Is this how it should look like? 

On Kill;Weapon RPG-7V2;PlayerCount 2;Log %p% kicked for RPG;Kick %p% RPG Not allowed

On Kill;Weapon SMAW;PlayerCount 2;Log %p% kicked for Smaw;Kick %p% SMAW Not allowed

On Kill;Weapon C4 Explosives;PlayerCount 2;Log %p% kicked for C4;Kick %p% C4 Not allowed

On Kill;Weapon M18 Claymore;PlayerCount 2;Log %p% kicked for Claymore %p% Claymore Not allowed

On Kill;Weapon M15 AT Mine;PlayerCount 2;Log %p% kicked for Mines;Kick %p% Mines Not allowed

On Kill;Weapon M224 Mortar;PlayerCount 2;Log %p% kicked for Mortar;Kick %p% Mortar Not allowed

On Kill;Weapon M67;PlayerCount 2;Log %p% kicked for Grenade;Kick %p% Grenade Not allowed

On Kill;Weapon M320;PlayerCount 2;Log %p% kicked for Grenade Launcher;Kick %p% Grenade Launcher Not allowed

On Say;Text !rules
PlayerSay === NO EXPLOSIVE ===
PlayerSay === WILL RESULT IN KICK ===

On Kill;Weapon M67;PlayerCount 1;PlayerSay WARNING! %p%, you have now %c% kills with %w%! (%c%/2);Kick You've been Warned!

On Kill;Weapon RPG-7V2;PlayerCount 1;PlayerSay WARNING! %p%, you have now %c% kills with %w%! (%c%/2);Kick You've been Warned!

On Kill;Weapon SMAW;PlayerCount 1;PlayerSay WARNING! %p%, you have now %c% kills with %w%! (%c%/2);Kick You've been Warned!

On Kill;Weapon C4 Explosives;PlayerCount 1;PlayerSay WARNING! %p%, you have now %c% kills with %w%! (%c%/2);Kick You've been Warned!

On Kill;Weapon M18 Claymore;PlayerCount 1;PlayerSay WARNING! %p%, you have now %c% kills with %w%! (%c%/2);Kick You've been Warned!

On Kill;Weapon M15 AT Mine;PlayerCount 1;PlayerSay WARNING! %p%, you have now %c% kills with %w%! (%c%/2);Kick You've been Warned!

On Kill;Weapon M224 Mortar;PlayerCount 1;PlayerSay WARNING! %p%, you have now %c% kills with %w%! (%c%/2);Kick You've been Warned!

On Kill;Weapon M320;PlayerCount 1;PlayerSay WARNING! %p%, you have now %c% kills with %w%! (%c%/2);Kick You've been Warned!