UNINSTALL ANY VERSION BEFORE 1.8.5 THAN RUN THE ModDiver Laboratory.exe​

Shortcut will be made on desktop. All versions post 1.8.5 auto-update so no need to re-download.

ModDiver Laboratory v1.8.5 AUTO-UPDATE introduced — Detailed Description​

ModDiver Laboratory is a free, open-source Windows application for managing and editing Helldivers 2 game data. It brings a mod library, an offline mod merger, built-in editing tools, deployment and recovery controls, and game launching into one portable application.

The app includes its own Python runtime, so you do not need to install Python separately. It works with game files on disk and does not inject code into or hook the running game. Compatible Lua mods run through a selected in-game loader, not through the Laboratory itself.

Supported Mods and Formats​

ModDiver can import mods from ZIP files or folders. It supports:

• Generated game-data files (.dl_bin): The Laboratory compares each mod’s file with a captured copy of the original game file, then merges compatible changes.
• YAO and QET .stream descriptors: These contain information used to apply a matching game-data file. The Laboratory recognizes both descriptor types.
• Arsenal patch files (.patch_N): Patch indices are reassigned during deployment so multiple patches can coexist.
• GPU resource files: Companion .gpu_resources files are deployed with their patches.
• General game-data files and assets: Files such as textures, audio and other assets can be backed up and deployed.
• Manifests and options: The Laboratory reads manifest.json, hellforge-mod.json and mod.json. Supported Options and SubOptions are shown as choices when adding a mod.
• Mixed mods: A single ZIP or folder can contain both mergeable .dl_bin files and ordinary assets.

New in 1.8.3: Chef-compatible Lua mods. Lua files are placed under the mod/ folder for the loader. The Laboratory includes Chef’s Shared Loader and Boot Mod Loader; only one can be deployed at a time. Lua compatibility depends on the mod and loader. DLL, EXE and ASI files are detected but not deployed.

Merge Engine​

The Merge Engine combines enabled mods offline using a captured stock copy of the game files as its baseline.

1. It compares each mod’s game-data file with the stock file and identifies the changed byte ranges.
2. It combines changes that can be applied together and logs conflicts with the affected offsets and mod names.
3. Mods higher in the enabled list take priority when changes overlap.
4. For five known game-data tables, it can also flag changes to different fields within the same fixed-size record as a possible conflict.
5. If a candidate changes the file length, the Laboratory avoids merging by byte offsets and uses the highest-priority candidate for that file.
6. The merged data is hash-corrected, sealed again, checked, and then written to the game.

The engine operates on file differences; it does not interpret every field in the game’s undocumented data formats. Its conflict report is intended to help identify collisions, not guarantee that every combination of mods will work in-game.

Editors and Mod Creation​

Three in-app editing tools cover passive bonuses, weapon handling and damage settings. The Laboratory also includes:

• SHODAN Stat Editor Offline v4.1.0
• Combined Community Mods v2.0.13, including Armory Forge, Vanilla+ and Hellpod tools

Edits and presets can be exported. The Laboratory can also capture game changes as a library mod, a portable ZIP, and an Arsenal data pack. Captured mods can be deployed directly from the Laboratory. Buttons in Mod Creator open the captured-mod and editor preset folders, and Armory Forge preset imports are saved in persistent storage.

The Arsenal data pack contains a YAO loader and patch files. Arsenal, HD2 Mod Manager and DDMM can deploy those patches. The pack checks that the target file matches the expected original, so it may not apply to a different game build. Its first installation requires launching the game, exiting normally, and launching it again. Do not enable another boot-replacement loader at the same time.

Deployment, Recovery and Safety​

• Install All deploys enabled mods and captures the stock baseline automatically if one does not exist.
• Purge restores files the Laboratory backed up and removes files it added.
• Verify Steam Files can restore game files through Steam.
• Writes use a temporary file and an atomic replacement, reducing the chance of leaving a partially written game file.
• Imported archives are checked for unsafe paths and size limits. Malformed or truncated sealed files are skipped with a log message.
• The Laboratory does not deploy DLL, EXE or ASI injectors and does not bypass anti-cheat.

For a game update, purge the Laboratory’s deployed changes, verify the game files through Steam, launch the game once, and capture a new stock baseline before deploying mods again. A baseline from an older build may not be suitable for the updated game.

Other Features​

• NoMoFOMO + Hidden Content Unlocker: A built-in on/off feature in Mod Creator.
• Game launcher: Launch Helldivers 2 from the Laboratory.
• Versioned application files: Separate versioned folders help avoid locked-DLL conflicts when launching updated copies.

Setup​

1. Extract the release ZIP.
2. Run ModDiver Laboratory.exe.
3. If Windows warns that the app is unsigned, select More info → Run anyway, or unblock the file in its Properties.
4. Use the About tab for feature guides.

The first Install All captures the stock baseline automatically. Do this while the game is clean and unmodded. Capture Stock clears the previous stock snapshot before creating a new one.

Credits​

• SHODAN — Stat Editor and game-data hash correction and sealing components
• Chef chfb — Chef Shared Loader
• VeganSquid — Boot Mod Loader
• Medic 3048 — File Mod Merger, whose merging model inspired this implementation
• Cowboy Bingus — Bingus Shared Loader and Vanilla+ Megapack
• huffdesigns — NoMoFOMO
• Yao — ModDiver Laboratory and Merge Engine

See LICENSES.md in the release for third-party component licenses.