Arsenal Documentation

Deploy copies the current profile's enabled mods into the Helldivers 2 data directory. Purge removes those installed files. Neither action deletes mods from the Arsenal Library.

Deploy is only on the profile toolbar. Purge is on both Library and profile toolbars, because it operates on the game folder, not on a specific list.

Before you deploy

Open the profile you want in-game
Enable the mods you need
Set options
Order the list for the priority mode you use in Settings
Close Helldivers 2 if it is running

Click Deploy, then Confirm Deploy. A progress bar lists each enabled mod. When it finishes, launch from the skull button or from the game client.

Disabled mods and separators are skipped. Only files from enabled options (and their selected sub-options) are copied.

What deploy does

Reads the open profile in list order
Resolves each UUID against the Library (files, options)
Copies patch files into the game data folder, applying load-order priority
Marks those mods deployed and clears the "changed" flag

If the game directory is not set, Arsenal sends you to Settings > Directories so you can pick the Helldivers 2 root (the folder that contains bin and data).

Status on each icon

Ring	Meaning
Green	Deployed and unchanged. No pending profile changes.
Yellow / orange	Deployed, but the profile changed since the last deploy (needs redeploy).
Red	Not currently deployed.

Redeploy after you:

Enable or disable mods
Reorder the profile
Change options
Add, update, or remove mods that were part of the last deploy

Load-order priority

When two enabled mods include the same file, the later write wins. Settings control which end of the list is written last:

Setting	Who wins
Set first mod to highest priority	Position 1 is deployed last, so it overrides everything below it
Set last mod to highest priority (default)	The bottom enabled mod is deployed last and overrides earlier rows

Example (default: last mod wins)

#1  Mod A  texture.patch_0
#2  Mod B  other.patch_0
#3  Mod C  texture.patch_0

Mod A and Mod C both ship texture.patch_0.
With "last mod highest priority", Mod C is the file that remains in data/.
With "first mod highest priority", Mod A remains instead.

Put foundation packs toward the low-priority end and overrides toward the high-priority end. Conflict warnings (see Actions) show overlaps but do not block deploy.

Note

Conflict warnings are informational. Overlap does not always mean the mods are incompatible. Many packs are meant to stack. Treat the dialog as a map of overlapping files, then reorder, disable, or change options as you prefer.

Purge

Click Purge
Read the confirmation (this cannot un-delete files from data/)
Click Confirm Purge

Use purge when you want a vanilla data folder: before a big profile swap, while isolating a crash, or before a game update.

Note

Purge does not remove mods from Arsenal. Profiles and the Library stay as they were. Deploy again to put files back.

Arsenal also purges automatically if you remove a deployed mod from a profile (single or bulk). That keeps leftover patch files from sitting in data/ after the profile no longer includes them.

Launch

The Helldivers skull button starts the game. While Arsenal believes the process is running, the button shows a running state and ignores extra clicks. Set the game directory first if launch fails.

Under Settings > Mod Management:

Setting	Effect
Automatically Activate Mods After Upload	New imports start enabled in the target profile
Automatically Activate All Mods Options After Upload	All options start enabled on those new imports
First vs last mod highest priority	Deploy write order
Replay Tutorial	Runs the Library / profile walkthrough again

Under Settings > Directories, confirm:

Helldivers 2 install (must contain bin and data)
Arsenal mods storage folder
Temporary folder used during extract and deploy

Troubleshooting

Mods not visible in-game

Confirm the correct profile is open
Confirm each mod is enabled
Confirm the icon ring is green (deploy after yellow/orange)
Confirm the game path in Settings
Launch after deploy has finished

Purge and confirm the vanilla game starts
Enable a small batch, deploy, test
Repeat until you find the pack or option that fails
Check conflict warnings for that batch and adjust order or options

Removing a mod emptied the game mods

If that mod was deployed, Arsenal purged data/ on purpose. Deploy the profile again.

Library and game disagree

The Library is the source of files. The game folder only reflects the last successful deploy of a profile. Switching profiles in the sidebar does not change data/ until you deploy (or purge).

Deployment