What sync does
When you click Sync, BD2 Mod Manager:- Reads the list of all currently enabled mods from the staging directory.
- Creates the target folder in the game directory if it does not already exist:
- Transfers each enabled mod into that folder using the configured sync method (Copy, Symlink, or Hardlink).
- Writes a manifest file at
<game_dir>/.bd2mm.jsonrecording which mods were synced and their state. - Removes any previously synced mods that are no longer enabled.
Only mods that are enabled are synced. Disabled mods are never written to the game directory.
Sync methods
You can choose how files are transferred in Settings → Sync method.- Copy
- Symlink
- Hardlink
Each enabled mod folder is copied into the game directory. This is the safest option and works without elevated permissions.
- No administrator rights required.
- Uses extra disk space equal to the total size of all enabled mods.
- Changes to mods in staging are not reflected until you sync again.
Unsync
Unsync removes all BD2MM-managed mods from the game directory. The manifest at<game_dir>/.bd2mm.json is also removed.
Use unsync to:
- Temporarily run the game without any mods.
- Clean up the game directory before uninstalling BD2 Mod Manager.
- Fix a broken sync state.
When is sync needed?
BD2 Mod Manager tracks whether the current enabled/disabled state matches what was last synced. The is sync needed check compares the current mod list against the manifest. A sync is needed when:- You have enabled or disabled one or more mods since the last sync.
- You have installed a new mod and enabled it.
- You have deleted a mod that was previously synced.
- You have changed the sync method in settings.
Game directory layout after sync
Sync errors
| Error | Cause | Resolution |
|---|---|---|
SymlinkAdminRequired | Symlink sync attempted without administrator rights. | Run BD2 Mod Manager as administrator, or switch to Copy or Hardlink sync method. |
ModPathNotFound | A mod’s staging folder was moved or deleted before sync completed. | Re-install the missing mod or disable it before syncing. |
CopyFailed | File copy failed due to a permissions or disk error. | Check disk space and folder permissions on the game directory. |
SymlinkFailed | Symbolic link creation failed. | Verify administrator rights or switch sync method. |
HardlinkFailed | Hard link creation failed, likely because staging and game are on different drives. | Move staging to the same drive as the game, or use Copy sync method. |
DirectoryCreationFailed | Could not create the BD2MM/ folder in the game directory. | Check write permissions for the game’s BepInEx/plugins/BrownDustX/mods/ path. |
RemovalFailed | Could not remove a previously synced mod during unsync or re-sync. | Check for file locks (is the game running?) and folder permissions. |
Close the game before syncing or unsyncing. Open game files can cause
CopyFailed or RemovalFailed errors.