Save Loadout V2

Save Loadout V2 gives mission makers and server owners precise control over Arma Reforger's custom loadout system while preserving the game's native arsenal, faction, blacklist, rank and supply systems.

Drop & Play

Add Save Loadout V2 and its dependencies and start playing. No configuration entity needs to be placed in the world.

By default, players can save custom loadouts, saved loadouts require only PRIVATE rank, and Player Supply Allocation will not prevent players from spawning with their saved equipment.

Want more control? Add the optional Save Loadout V2 configuration component to the FiF_Core configuration entity and customize the rules directly in World Editor.

Your Loadout. Your Rules.

Save Loadout V2 provides independent control over the systems that determine whether a custom loadout can be saved and subsequently used:

• Master Save Loadout permission
• Arsenal save type
• Faction custom-loadout support
• Native blacklist validation
• Arsenal inventory membership
• Faction/catalog membership
• Item-rank restrictions
• Military Supply Allocation while saving
• Player Supply Allocation while spawning
• Required rank for saved loadouts
• Save Loadout action visibility
• Save Loadout action availability

Most controls use FiF_Core's DEFAULT / DENY / ALLOW policy model, allowing individual restrictions to be preserved, explicitly enforced, or bypassed without turning the entire system into an all-or-nothing switch.

Native Blacklist Support

Save Loadout V2 works directly with Reforger's native loadout blacklist system, including both category/type-based blacklist rules and individually blacklisted prefabs.

Blacklist validation can be preserved or bypassed independently from faction, rank, inventory and supply validation. Blacklisted items encountered during saving are also recorded through the dedicated SLPV2 blacklist logger for troubleshooting.

Saving Is Only Half the Job

Allowing a player to save a loadout isn't very useful if Reforger refuses to let them spawn with it.

Save Loadout V2 therefore includes narrowly targeted spawn-side controls for saved loadouts. Player Supply Allocation restrictions can be independently controlled, and the required rank for a saved loadout can be configured or returned to Reforger's native calculated requirement.

These changes are deliberately scoped to the custom-loadout workflow. Save Loadout V2 does not globally disable unrelated rank, faction, arsenal or supply mechanics just to make saved loadouts work.

Flexible Configuration

Use the defaults for a simple Drop & Play experience, or configure Save Loadout V2 for scenarios such as:

• Allowing players to save equipment obtained outside an arsenal
• Allowing non-faction equipment while retaining other restrictions
• Enforcing blacklists while bypassing item-rank requirements
• Preserving native save validation while allowing saved loadouts through Player Supply Allocation
• Requiring a specific rank to use custom loadouts
• Hiding or disabling the Save Loadout interaction
• Selecting a different arsenal save type for loadout validation

Built on FiF_Core

Save Loadout V2 uses FiF_Core's shared runtime configuration system and ScriptLoggerV2 logging infrastructure. Configuration is registered once during initialization and resolved values are reused at runtime.

Designed to Play Nicely

Rather than broadly overriding entire game systems, Save Loadout V2 targets the specific decisions involved in saving and using custom loadouts. Other systems continue using Reforger's normal behavior.

Dependencies

• FiF_Core
• ScriptLoggerV2 (through FiF_Core)

IMPORTANT NOTE:
Save Loadout V2 is not a loadout persistence system. It will not make saved loadouts available across server or game-mode restarts. Loadout persistence for the ForgedInFire ecosystem is planned for a future FiF_Persistence mod.

Developed by ForgedInFire
[email protected]
Forged in Fire Developer's Guide - Save Loadout V2: https://www.drawingonhumanity.com/forgedinfire/#module/save-loadout-v2