Skip to Content
Mod ManagementDeployment

Deployment

Deployment is the process of installing your enabled mods into the Helldivers 2 game directory. This guide covers the deployment workflow, status indicators, and troubleshooting.

Deployment Overview

Arsenal Deploy Button

When you click Deploy:

  1. Arsenal reads your enabled mods in order
  2. Mod files are processed according to options
  3. Files are copied to the game’s data directory
  4. Conflicts are resolved by load order
  5. The game is ready to launch with mods

Deploy Button

The Deploy button (download icon) in the toolbar initiates deployment.

Pre-Deployment Check

Before deploying, ensure:

  • Desired mods are enabled
  • Mods are in the correct order
  • Options are configured as wanted
  • Game is not running

Deployment Status

Icon Indicators

Mod icons show deployment status through border colors:

BorderStatusMeaning
GreenDeployedMod is installed, no changes
YellowChangedMod was modified since deploy
RedNot DeployedMod is not in the game

When to Redeploy

Redeploy when you’ve made changes:

  • Enabled or disabled mods
  • Changed mod order
  • Modified mod options
  • Added new mods
  • Updated existing mods

The yellow border reminds you that changes haven’t been applied yet.

Purge

The Purge action removes all deployed mods from the game directory.

Arsenal Purge Button

When to Purge

  • Before completely changing your mod setup
  • If experiencing game issues
  • To verify vanilla game behavior
  • Before game updates (recommended)

Purge Process

  1. Click the Purge button (warning icon)
  2. Read the warning dialog
  3. Click Confirm Purge
  4. All mod files are removed from the game directory

Note: Purge does NOT delete your mods from Arsenal. They remain in your library and profiles.

After Purging

  • Game will run vanilla
  • Deploy again to restore mods
  • Your configuration remains intact

Conflict Resolution

How Conflicts Work

When multiple mods modify the same file, load order determines the winner:

Load Order Example with low priority:
  
Position 1: Mod A (texture.patch_0)
Position 2: Mod B (other.patch_0)
Position 3: Mod C (texture.patch_0)

Result: texture.patch_0 = Mod C's version
        (Mod A's changes are overwritten)

Strategic Ordering

Place mods intentionally:

  • Base/foundation mods - Top (loaded first)
  • Override mods - Below what they override
  • Priority mods - Bottom (loaded last, always wins)

Conflict Warnings

Use the conflict detection feature to identify issues:

  1. Look for warning icons on mods
  2. Click to see which mods conflict
  3. Decide which should take priority
  4. Reorder or disable as needed
Arsenal Conflict Warnings

Note: Conflict warnings are informational only. If two or more mods conflict, it doesn’t necessarily mean they won’t work together. Many mods are designed to work alongside each other, and conflicts may be intentional or harmless. Use these warnings as a guide to understand load order, but don’t assume conflicts will cause problems.

Troubleshooting

Mods Not Working In-Game

  1. Verify mods are enabled
  2. Check deployment status (green border)
  3. Ensure you deployed after changes
  4. Verify game path in settings

”Game directory not found”

  1. Go to Settings
  2. Update the Helldivers 2 game path
  3. Select the folder containing bin and data directories

Deployment Takes Too Long

Large mod collections take longer. This is normal for:

  • First-time deployments
  • Many high-resolution texture mods
  • Mods with large file counts

Game Crashes After Deploy

  1. Purge all mods
  2. Verify game works vanilla
  3. Enable mods in small batches
  4. Deploy and test after each batch
  5. Identify the problematic mod

Conflicting Mods Causing Issues

  1. Check conflict warnings
  2. Disable conflicting mods one at a time
  3. Test to find the issue
  4. Adjust load order or remove incompatible mods
ActionsOverview