Jump to content

On-Spawn Loadout Enforcer for Infantry/Vehicles - AdKatsLRT


ColColonCleaner

Recommended Posts

  • 2 months later...
Just now, FLParzival said:

Hey all, im obviously doing some wrong. But this is all that shows up when I install the plugin, all the weapons and vehicles are not showing up, also when I try to start it fails. Ive reviewed the setup guide but cant find what Im missing.

Capture.PNG

Posting the error would be helpful. Your post contains 0 information about the problem.

Link to post
  • Administrators
Just now, FLParzival said:

Wow, great job dude you were an asshole in support forums. Feel big? I posted a photo of the issue and all.

Actually, he's not wrong. That's not anything to go off of. You didn't post any of the errors that the procon console outputs. Only thing I can tell you is that the plugin isn't enabled. Nothing further. Post the error that it outputs when you enable it.

The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

ezscale_banner.jpg

Link to post
15 minutes ago, FLParzival said:

Wow, great job dude you were an asshole in support forums. Feel big? I posted a photo of the issue and all.

Yeah. The picture does not contain an error. It is the default state of the plugin.

Thanks for insulting me. I only asked for the error msg you get when enabling it.

Which you refuse to provide.

Link to post
1 hour ago, FLParzival said:

Hey all, im obviously doing some wrong. But this is all that shows up when I install the plugin, all the weapons and vehicles are not showing up, also when I try to start it fails. Ive reviewed the setup guide but cant find what Im missing.

Capture.PNG

You need to enable it. Select "true" on Display Weapon Accessory Settings and, the options will appear.

 

image.png.5b7365df6525b68662fb6c5133e23441.png

Link to post
  • 6 months later...
On 2020. 1. 5. at 오전 12시 41분, ColColonCleaner said:

현재로서는 방법이 없습니다. 제한 사항이 특정 맵에서만 활성화되도록 설정할 수 있지만 제한 사항 자체는 맵 간에 변경할 수 없습니다.

Is it still impossible?

I want to change the settings according to the map in rush mode.

Link to post
  • 2 weeks later...
On 1/22/2015 at 6:03 PM, ImportBot said:

On-Spawn Loadout Enforcer for Infantry/Vehicles - AdKatsLRT


AdKatsLRT - On-Spawn Loadout Enforcer

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.

 


 

 

AdKats User Manual

 

AdKats User Manual

  • 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.

AdKats User Manual

  1. 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.
  2. Download and install AdKatsLRT. The plugin is installed like any other procon plugin.
  3. 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.


AdKats User Manual

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.


AdKats User Manual

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.

AdKats User Manual

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.

 


I'm having 2 problems:

- VIP and ADM are not punished.
- I'm getting this error:ERROR-2091: [Unable to fetch victim camper44 on kill.]

 

Can anyone help?

Edited by BruceLeeSoldier
Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • Game Server Hosting:

      We're happy to announce that EZRCON will branch out into the game server provider scene. This is a big step for us so please having patience if something doesn't go right in this area. Now, what makes us different compared to other providers? Well, we're going with the idea of having a scaleable server hosting and providing more control in how you set up your server. For example, in Minecraft, you have the ability to control how many CPU cores you wish your server to have access to, how much RAM you want to use, how much disk space you want to use. This type of control can't be offered in a single service package so you're able to configure a custom package the way you want it.

      You can see all the available games here. Currently, we have the following games available.

      Valheim (From $1.50 USD)


      Rust (From $3.20 USD)


      Minecraft (Basic) (From $4.00 USD)


      Call of Duty 4X (From $7.00 USD)


      OpenTTD (From $4.00 USD)


      Squad (From $9.00 USD)


      Insurgency: Sandstorm (From $6.40 USD)


      Changes to US-East:

      Starting in January 2022, we will be moving to a different provider that has better support, better infrastructure, and better connectivity. We've noticed that the connection/routes to this location are not ideal and it's been hard getting support to correct this. Our contract for our two servers ends in March/April respectively. If you currently have servers in this location you will be migrated over to the new provider. We'll have more details when the time comes closer to January. The new location for this change will be based out of Atlanta, GA. If you have any questions/concerns please open a ticket and we'll do our best to answer them.
      • 5 replies
    • Hello All,

      I wanted to give an update to how EZRCON is doing. As of today we have 56 active customers using the services offered. I'm glad its doing so well and it hasn't been 1 year yet. To those that have services with EZRCON, I hope the service is doing well and if not please let us know so that we can improve it where possible. We've done quite a few changes behind the scenes to improve the performance hopefully. 

      We'll be launching a new location for hosting procon layers in either Los Angeles, USA or Chicago, IL. Still being decided on where the placement should be but these two locations are not set in stone yet. We would like to get feedback on where we should have a new location for hosting the Procon Layers, which you can do by replying to this topic. A poll will be created where people can vote on which location they would like to see.

      We're also looking for some suggestions on what else you would like to see for hosting provider options. So please let us know your thoughts on this matter.
      • 4 replies
    • Added ability to disable the new API check for player country info


      Updated GeoIP database file


      Removed usage sending stats


      Added EZRCON ad banner



      If you are upgrading then you may need to add these two lines to your existing installation in the file procon.cfg. To enable these options just change False to True.

      procon.private.options.UseGeoIpFileOnly False
      procon.private.options.BlockRssFeedNews False



       
      • 2 replies
    • I wanted I let you know that I am starting to build out the foundation for the hosting services that I talked about here. The pricing model I was originally going for wasn't going to be suitable for how I want to build it. So instead I decided to offer each service as it's own product instead of a package deal. In the future, hopefully, I will be able to do this and offer discounts to those that choose it.

      Here is how the pricing is laid out for each service as well as information about each. This is as of 7/12/2020.

      Single MySQL database (up to 30 GB) is $10 USD per month.



      If you go over the 30 GB usage for the database then each additional gigabyte is charged at $0.10 USD each billing cycle. If you're under 30GB you don't need to worry about this.


      Databases are replicated across 3 zones (regions) for redundancy. One (1) on the east coast of the USA, One (1) in Frankfurt, and One (1) in Singapore. Depending on the demand, this would grow to more regions.


      Databases will also be backed up daily and retained for 7 days.




      Procon Layer will be $2 USD per month.


      Each layer will only allow one (1) game server connection. The reason behind this is for performance.


      Each layer will also come with all available plugins installed by default. This is to help facilitate faster deployments and get you up and running quickly.


      Each layer will automatically restart if Procon crashes. 


      Each layer will also automatically restart daily at midnight to make sure it stays in tip-top shape.


      Custom plugins can be installed by submitting a support ticket.




      Battlefield Admin Control Panel (BFACP) will be $5 USD per month


      As I am still working on building version 3 of the software, I will be installing the last version I did. Once I complete version 3 it will automatically be upgraded for you.





      All these services will be managed by me so you don't have to worry about the technical side of things to get up and going.

      If you would like to see how much it would cost for the services, I made a calculator that you can use. It can be found here https://ezrcon.com/calculator.html

       
      • 11 replies
    • I have pushed out a new minor release which updates the geodata pull (flags in the playerlisting). This should be way more accurate now. As always, please let me know if any problems show up.

       
      • 9 replies
×
×
  • 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.