Connect Open Mod Manager to the Operation Mountain Sentinel repository
Open Mod Manager (OMM) is an open-source mod manager. This site hosts two HTTP-accessible package trees for Operation Mountain Sentinel: one for Saved Games content (per-user DCS data) and one for Root content (files that belong under the DCS installation). You register each tree in OMM as its own repository so installs and updates stay in the correct place on disk.
Use these exact HTTPS URLs and display names when adding sources in OMM. Trailing slashes match how the server lists directories.
User-level mods, scripts, and configs that live under your Windows Saved Games\DCS (or equivalent) hierarchy.
Display name in OMM:
Installation-level packages intended for the DCS program folder (core install path), not under Saved Games.
Display name in OMM:
repo.opmtnsen.com.The screenshots below match Open Mod Manager’s typical flow for DCS. Menu labels can vary slightly by version; use this sequence together with the repository URLs above. Click any image to open it full size in a new tab.
Download the latest OMM release from GitHub:
OMM is a generic mod manager: it can track multiple games. For squadron DCS mods, you will create a Mod Hub dedicated to DCS.
After installing OMM, create a hub for DCS:
Name the hub DCS and choose where downloaded packages should be stored on disk.
When asked to create a channel immediately, choose No for now (channels are configured in the next steps).
Optionally set OMM to open your new hub on startup:
With that enabled, OMM will load the DCS hub automatically when you start the application.
Next, add modding channels for Saved Games and Root (either order is fine; Saved Games first below):
Name the first channel Saved Games and set its path to your DCS Saved Games folder, for example:
C:\Users\[YourName]\Saved Games\DCSContinue with Next.
Confirm Saved Games appears in the channel list.
Add Root the same way, pointing at your DCS installation folder, for example:
C:\Program Files\Eagle Dynamics\DCS WorldYour install path may differ (Steam, standalone, etc.).
When both channels exist, the overview should resemble the following (Saved Games and Root side by side in the workflow).
Attach the squadron network repository to the Saved Games channel first:
https://repo.opmtnsen.com/mods/savedgames/For Name, enter OMSSG:
OMSSGClick Next. OMM should validate the repository and report it as valid. Then click Finish.
After the network repo appears in the list, open it (for example by double-clicking) to see available packages. Download what you need; downloading is separate from installing to the channel.
Repeat the network setup for Root: select the Root channel, open Network Library, add a source, and use the Root URL and name:
https://repo.opacity.com/mods/root/Name: OMSRoot
OMSRootComplete Next / Finish as with Saved Games. The dialogs match the earlier screenshots.
Download any required mods from each network library, then switch to Local Library to install. Double-click mods there to activate; a green check indicates they are installed for that channel.
Spot-check the correct on-disk folder (Saved Games vs install root) if you are unsure a package applied to the intended channel.
DCS loads content from two major locations: per-user data (missions, some mods, configs) under your profile’s Saved Games\DCS tree, and application files under the DCS install directory. Squadron tooling is split so packages land where the game expects them. Using the wrong repository for a given mod can mean files are ignored at runtime or overwrite the wrong subtree.