StripItem

This is compatible with custom loadouts and enables servers to remove items from play that are included within the loadout. These will still be able to be selected from the loadout, but they will be removed on spawn. This can be used to remove unwanted weapons, explosives, fire support, or keep the main part of a custom loadout like ISMC, while removing unwanted aspects. You can choose to strip AI or humans or both.

Mutator=StripItem

Mutator=StripItem1

<table class="table is-bordered is-hoverable"> <tbody> <tr> <td>

Config

</td> <td>

Description

</td> </tr> <tr> <td>RemoveItems</td> <td>A comma separated string of keywords to remove from player on spawn or resupply</td> </tr> <tr> <td>bStripAI</td> <td>If set to true, then bots will have the item removed. Default is True</td> </tr> <tr> <td>bStripHuman</td> <td>If set to true, then players will have the item removed. Default is True</td> </tr> <tr> <td>debug</td> <td>If set to true, then players will have all their equipped items printed to the chat window. Set this to true if you are unsure of the keywords to use for certain items and then set RemoveItems appropriately</td> </tr> </tbody> </table>

Default config is below. StripItem removes fire support from all bots/players and StripItem1 removes all launchers/plantables from bots/players.

<pre>[/StripItem/Mutators/StripItem.StripItem_C] RemoveItems=binocs,radio bStripAI=True bStripHuman=True

[/StripItem/Mutators/StripItem1.StripItem1_C] RemoveItems=explosive bStripAI=True bStripHuman=True</pre>

Some examples of how NWI formats their items:

BP_Explosive_Panzerfaust
BP_Explosive_C4
BP_Grenade_Molotov
BP_Grenade_M84
BP_Firearm_Welrod
BP_Firearm_DesertEagle
BP_Firearm_Galil
BP_Firearm_M1Garand
BP_Gear_SEC_Carrier_Grenade
BP_Gear_SEC_Carrier_LongGun
BP_Gear_SEC_Carrier_Pistol
BP_Gear_INS_Carrier_Heavy
BP_Gear_SEC_Armour_Light
BP_Gear_INS_Armour_Heavy
BP_MILSPEC_NVG
BP_Civilian_NVG
BP_Gear_INSGasMask
BP_Melee_CombatKnife
BP_Gear_Radio
BP_Utility_INSBinoculars

Links for FullyLoaded's list of Items: https://jpst.it/2TZKl

Note on implementation: Since this requires the server to check every item given to player and bot for a number of keywords, less is better than more. Using "explosive" or "grenade" instead of listing each launcher and grenade will be a great increase in performance.

---

---

ForceUpgrade

The forceUpgrade option is to give control of upgrades specifically. Config supports class specific upgrades and forcing or stripping the upgrades.

Mutator=ForceUpgrade

Mutator=ForceUpgrade1

<table class="table is-bordered is-hoverable"> <tbody> <tr> <td>

Config

</td> <td>

Description

</td> </tr> <tr> <td>bOnlyForBots</td> <td>If set to true, then the adjustment will only be applied to bots as opposed to bots and players.</td> </tr> <tr> <td>Keyword</td> <td>This is the keyword that can be used for the specific upgrade that should be added/removed.</td> </tr> <tr> <td>Slot</td> <td>This sets the slot the upgrade falls in. i.e. Barrel, Siderail, etc.</td> </tr> <tr> <td>bJustRemove</td> <td>If set to true, then the upgrade will only be removed. Nothing put in its place.</td> </tr> <tr> <td>bClassSpecific</td> <td>If set to true, then the upgrade will only be adjusted for playerclass names that contain the keyword set below. (i.e. Command, Observ)</td> </tr> <tr> <td>PlayerClassKeyword</td> <td>This can be any string that will be contained within a playerclass name. Only used if bClassSpecific is set to True.</td> </tr> </tbody> </table>

Default config is below. ForceUpgrade:

<pre>[/StripItem/Mutators/ForceUpgrade.ForceUpgrade_C] bOnlyForBots=True Keyword=sup Slot=Barrel bJustRemove=False bClassSpecific=False PlayerClassKeyword=

[/StripItem/Mutators/ForceUpgrade1.ForceUpgrade1_C]</pre>

Appreciate my work and want to donate or have a mod made? See my profile for link. If leaving a comment regarding bugs or feedback go ahead and tag me so I get a notification.