Installing and Managing Mods

Anomaly mods are MelonLoader DLLs built against the Anomaly public API. The Launcher can install approved public repository mods into a loadout, or you can place trusted DLLs in a loadout’s local/Mods/ folder.

Public Repository

Open the Public Repository tab to browse mods from the Anomaly mod platform. Repository entries show their name, author, version, supported game versions, downloads, and install state.

Available actions:

• Install mod downloads the selected mod and any declared client dependencies.
• Update replaces an installed repository mod with the current compatible version.
• Uninstall removes files that belong to that repository install when no other installed mod still needs them.

Repository downloads are verified before being committed to the mod cache. Public mods are reviewed and scanned for malware before release, but you should still use normal caution with any third-party code.

The Launcher also supports anomaly-launcher://install?mod=<id> links from the mod platform.

Manual installs

Put manual mod DLLs in the active loadout’s local mods folder:

GameRoot/
`-- loadouts/<loadout-name>/
    `-- local/
        |-- Mods/
        |   |-- YourMod.dll
        |   `-- SomeOtherMod.dll.DISABLED
        `-- UserLibs/

Do not put mod DLLs in UserLibs/. That folder is for shared libraries that mods reference, not mods that MelonLoader should load directly.

Local files are layered after catalog packages when the loadout starts. If local/Mods/YourMod.dll has the same filename as a catalog package file, the local copy wins for that loadout.

Only install trusted mods

A mod is code running inside your game. It can read and write files, use the network, and affect your game session. Prefer repository mods or releases from authors you trust, and scan unfamiliar manual downloads with your antivirus before installing them.

The Installed tab

The Installed tab lists the mods in the selected loadout, including catalog entries and local DLLs the Launcher can inspect. For each mod, the Launcher shows:

• Display name.
• Version.
• Target game version, if the mod declares one.
• Enabled or disabled state.
• Missing dependency warnings.

Repository-installed and manually installed mods both appear here where possible.

Enabling and disabling

Use the checkbox on a mod card to toggle it.

• Enabled: YourMod.dll.
• Disabled: YourMod.dll.DISABLED.

Toggling does not delete the file. Changes take effect the next time the loadout starts; MelonLoader does not unload mods from a running game.

Missing dependencies

If the Launcher shows MISSING DEPENDENCIES, the mod references one or more libraries that are not available in Mods/, UserLibs/, or MelonLoader’s runtime folders after the loadout materializes.

To fix it:

1. Check the mod’s install instructions.
2. Install the missing dependency through the Public Repository if available.
3. For manual mods, place required shared libraries where the mod author tells you, usually local/UserLibs/.
4. Restart the Launcher after adding dependency files.

Do not ignore missing dependencies. The game may fail to launch or the mod may crash during startup.

Choosing mods

When evaluating a mod, look for:

• A supported game version.
• A clear author and changelog.
• Repository approval or a source-code repository you can inspect.
• Installation instructions that list dependencies.

Next

Troubleshooting and Logs.