Install OMSI Mods Without Cluttering the Game Folder? This Manager Uses Symlinks!

The approach is quite different from traditional OMSI modding. Instead of copying every mod directly into the game directory, the OMSI 2 Mod Manager stores unpacked files inside a separate mod library. When a mod is enabled, symbolic links are created inside the OMSI folder. The game sees what look like ordinary files, while the actual data remains in the external library.

First-time setup therefore requires two locations: the OMSI 2 root folder containing Omsi.exe and an empty folder for the mod library. The developer recommends keeping that library on the same drive where possible. Most importantly, do not delete it later, because it contains the real mod files. If it disappears, the links stop working.

ZIP, RAR and 7Z archives can be imported. The manager analyses their structure before the mod is added to the library and activated separately.

The Conflict Solver becomes especially useful when multiple mods change the same texture or script. A load order determines which one wins, with the mod at the top taking the highest priority.

The project also describes a backup system. If a mod replaces an existing game file, the original is backed up automatically, and the manager attempts to restore it when the mod is disabled or removed. That is useful, although we would still keep a separate backup of any heavily modified OMSI installation.

The built-in HOF Manager is another practical addition. HOF files can be assigned to several buses at once, with the program creating symlinks instead of repeatedly copying the same files into individual vehicle folders. A Reset All option can later remove those links again.

The project remains publicly available and is not archived. GitHub currently marks Version 1.1.4 as the Latest release, with additional commits already present on the master branch afterwards.

One detail needs careful wording on Windows. Microsoft treats the creation of symbolic links as a specific user privilege. However, the current OMSI 2 Mod Manager instructions do not state that Developer Mode or “Run as Administrator” is always mandatory. We therefore would not present either requirement as universal unless a specific system actually encounters permission problems.

Projekt-/Downloadlink

OMSI 2 Mod Manager – GitHub

The core idea is simple: keep mods separate from the actual OMSI installation, while still allowing the game to access them and making conflicts visible instead of silently overwriting files. For a very old and heavily modified installation, backing everything up and testing with only a few mods first would still be sensible.

How chaotic is your OMSI folder by now? Do you still install mods entirely by copy and paste? Would you prefer a separate mod library?