On-Spawn Loadout Enforcer for Infantry/Vehicles - AdKatsLRT

[ColColonCleaner]

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.

---

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. Download the plugin from here: https://github.com/AdKats/AdKats-LRT/archive/master.zip. 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.

---

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
  Prophet731
• Submitted
  12/24/19
• Category
  Plugins

 

[ImportBot]

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.

---

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.

---

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

 

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Hi,

 

i get some weird results on one of my servers, i have disabled Snipers/DMR, and when we spawn i get yells that i have to remove all snipers/DMR from loadout.

That message display issue was injected last night with the vehicle updates, fixed in 2.0.0.1.

[ImportBot]

Originally Posted by TMiland*:

 

That message display issue was injected last night with the vehicle updates, fixed in 2.0.0.1.

Okay, i'll update asap!

[ImportBot]

Originally Posted by virusdead*:

 

I just put a days the procon indicates only the version 2.0.0.0

 

[imgur](http://i.imgur.com/nNcJbQK.png)

[ImportBot]

Originally Posted by ColColonCleaner*:

 

I just put a days the procon indicates only the version 2.0.0.0

 

[imgur](http://i.imgur.com/nNcJbQK.png)

You are running 2.0.0.1:

 

If you reboot a procon layer without rebooting your procon client it doesn't show updated plugin version numbers. Just reboot your procon client and you'll see the updated version number.

[ImportBot]

Originally Posted by virusdead*:

 

You are running 2.0.0.1:

 

If you reboot a procon layer without rebooting your procon client it doesn't show updated plugin version numbers. Just reboot your procon client and you'll see the updated version number.

This is perfect thanks for your help beings

[ImportBot]

Originally Posted by ColColonCleaner*:

 

A couple messaging updates in 2.0.0.2.

[ImportBot]

Originally Posted by PapaCharlie9*:

 

Back to $25? Is that an early-adopter discount or the final price?

[ImportBot]

Originally Posted by EBassie*:

 

Any chance you will be adding settings per map or 'only enable on certain maps' to this plugin?

 

I might be interested using it, but since I run ALL CQ maps I don't want to force the loadout on other maps than Metro / Lockers.

 

I just want to reduce the explosive, flashbang and flare spam on those two maps, don't care about the loadout on other maps.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Back to $25? Is that an early-adopter discount or the final price?

Early adopter is a good way to put it.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Any chance you will be adding settings per map or 'only enable on certain maps' to this plugin?

 

I might be interested using it, but since I run ALL CQ maps I don't want to force the loadout on other maps than Metro / Lockers.

 

I just want to reduce the explosive, flashbang and flare spam on those two maps, don't care about the loadout on other maps.

I'll add that feature tomorrow.

[ImportBot]

Originally Posted by EBassie*:

 

I'll add that feature tomorrow.

OK, nice.

 

I have not made up my mind yet about using this plugin.

Want to see what my clan and regulars think of the idea before purchasing.

 

Too bad I cannot test to see how the players react on it without doing the $25...

[ImportBot]

Originally Posted by LumPenPacK*:

 

OK, nice.

 

I have not made up my mind yet about using this plugin.

Want to see what my clan and regulars think of the idea before purchasing.

 

Too bad I cannot test to see how the players react on it without doing the $25...

The same goes for me. I'm really interested to see how players would accept this plugin compared to my Insane Limits weapons restrictions.

 

But I'm not sure if it would really improve players game experience on the server or make the things even more complicated to the players.

 

Is it possible to enable/disable certain restrictions not only based on maps but also based on game mode?

 

Some kind of API that allows other plugins to control the restrictions would be amazing.

 

EDIT: I've just noticed there's already something like this.

 

Other plugins can call loadout checks and enforcement, so it can enhance your current auto-admin.

Can you give us some additional information about this? How can I integrate your plugin into IL for example?

[ImportBot]

Originally Posted by virusdead*:

 

I agree with @Ebassi the ideal is added more maps, my server is constantly rush and some maps mode on vehicles, if I remove some weapons, players wallpaper that insult the server and me but uncomfortable.

Ideally the maps with prohibited weapon or weapons that corresponds to the maps

 

for an if say I paid this product but I do not used here all of it's function

[ImportBot]

Originally Posted by ColColonCleaner*:

 

OK, nice.

 

I have not made up my mind yet about using this plugin.

Want to see what my clan and regulars think of the idea before purchasing.

 

Too bad I cannot test to see how the players react on it without doing the $25...

There is a reason I made statistics available at level 2 debug, it shows percentages of people affected and how it affected them. Those enforced, those killed for invalid loadout, the ones who fixed their loadout after being killed, and those who left the server without fixing their loadout. Modify your settings until you see the affected levels you like.

 

It all depends on your server rules. Our no explosive server is basically bullets only, so all grenade slot items are banned. Flares/smoke/flash/incendiary are on spawn enforcement, and v40/rgo are on trigger enforcement. Basically we placed anything that bypasses autoadmin on spawn enforcement, like shooting C4 or throwing smoke for example, and put all other banned items under trigger enforcement, like RPGs or EOD bots.

 

You will notice some players annoyed off the bat, but we found after a week or so your main player base starts defending it as a great move, surprised we hadn't done it sooner. Little do they know it wasn't possible not long ago.

 

EDIT: (502/511) 98% processed. (197/511) 39% killed. (168/197) 85% fixed. (27/197) 14% quit.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

The same goes for me. I'm really interested to see how players would accept this plugin compared to my Insane Limits weapons restrictions.

 

But I'm not sure if it would really improve players game experience on the server or make the things even more complicated to the players.

 

Is it possible to enable/disable certain restrictions not only based on maps but also based on game mode?

 

Some kind of API that allows other plugins to control the restrictions would be amazing.

 

EDIT: I've just noticed there's already something like this.

 

 

 

Can you give us some additional information about this? How can I integrate your plugin into IL for example?

When integrated with AdKats this plugin reacts to the mark, punish, and report commands. When a player is marked or punished they are immediately raised from spawn level enforcement to trigger level enforcement and loadout checked. When a player is reported, any invalid items they are carrying are reported to online admins. You can mark/punish players from any current autoadmin.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

I agree with @Ebassi the ideal is added more maps, my server is constantly rush and some maps mode on vehicles

Yes, map/mode selection is being added.

[ImportBot]

Originally Posted by aduh*:

 

Can we block becon with this and stop ppls flying to the roof on Kharg (BF3) ?

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Can we block becon with this and stop ppls flying to the roof on Kharg (BF3) ?

Sorry, this plugin can only be used on BF4 servers. Yes it can block spawn beacons.

[ImportBot]

Originally Posted by aduh*:

 

Sorry, this plugin can only be used on BF4 servers. Yes it can block spawn beacons.

that's a pity, its just what we need on our BF3 server

[ImportBot]

Originally Posted by LumPenPacK*:

 

When integrated with AdKats this plugin reacts to the mark, punish, and report commands. When a player is marked or punished they are immediately raised from spawn level enforcement to trigger level enforcement and loadout checked. When a player is reported, any invalid items they are carrying are reported to online admins. You can mark/punish players from any current autoadmin.

But this means it can only be used with AdKats features and I don't have something like a interface to use it with other plugins or even with the ProCon API?

 

If it could be used with Insane Limits, it would be really amazing.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

But this means it can only be used with AdKats features and I don't have something like a interface to use it with other plugins or even with the ProCon API?

 

If it could be used with Insane Limits, it would be really amazing.

What would you want to be able to send from IL?

[ImportBot]

Originally Posted by LumPenPacK*:

 

What would you want to be able to send from IL?

At the moment I'm using different weapon limitations based on game mode (basically on Rush and Obliteration Competitive)

Okay, this could be done with Loadout Enforcer itself since you may add gamemode/map based settings.

 

The other thing: I'm using some kind of adaptive explosive spam limitation that is based on map, gamemode and on players kills in the current round. ("Only 'x' explosive kill every 'y' kills. But you start with 'z' kills a round")

 

Additional there could be much more nice things possible in the feature that could be enabled/disabled based on different events and not only on gamemode and map.

 

* Allow only one spawn beacon per Squad

* Allow only low and mid range scopes on Rush (might already be possible)

* ...

[ImportBot]

Originally Posted by ColColonCleaner*:

 

At the moment I'm using different weapon limitations based on game mode (basically on Rush and Obliteration Competitive)

Okay, this could be done with Loadout Enforcer itself since you may add gamemode/map based settings.

 

The other thing: I'm using some kind of adaptive explosive spam limitation that is based on map, gamemode and on players kills in the current round. ("Only 'x' explosive kill every 'y' kills. But you start with 'z' kills a round")

 

Additional there could be much more nice things possible in the feature that could be enabled/disabled based on different events and not only on gamemode and map.

 

* Allow only one spawn beacon per Squad

* Allow only low and mid range scopes on Rush (might already be possible)

* ...

So you basically want access to a players loadout in IL whenever it's fetched to do whatever processing you want with it? I already send that info to AdKats, but I'm not sure how i would send it to IL.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Map/Mode options added in 2.0.1.0, with quick selection settings.

 

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Two people who purchased the plugin today have not contacted me about acquiring it. Please contact me ASAP about your purchase, thanks.

[ImportBot]

Originally Posted by LumPenPacK*:

 

Map/Mode options added in 2.0.1.0, with quick selection settings.

 

You're damn fast. Thanks for that update.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Several people who have purchased this are not using it to control public servers, instead they are using it as a scrim loadout manager. This is very interesting. I know there are certain official "types" of scrims, each type with a specific set of rules, so perhaps if someone running these scrims sends me the official rule list for their preferred type I can set up a preset for it.

[ImportBot]

Originally Posted by LumPenPacK*:

 

Several people who have purchased this are not using it to control public servers, instead they are using it as a scrim loadout manager. This is very interesting. I know there are certain official "types" of scrims, each type with a specific set of rules, so perhaps if someone running these scrims sends me the official rule list for their preferred type I can set up a preset for it.

They might use ESL rules

 

http://www.esl.eu/eu/bf4/cup/dominat...20Restrictions