Updating and Reinstalling

The Launcher keeps installed game builds and named loadouts separate. Loadouts using the official core resolve a compatible signed package for the selected build. A local development core takes precedence when present.

Compatibility window

Core v1 declares Anomaly SupportedGameVersion 14.2.7^. The caret means:

14.2.7 is accepted.
Later 14.2 patch releases are accepted.
Versions before 14.2.7 are rejected.
14.3.0 and later are rejected until a release declares support.

This is Anomaly’s compatibility contract, not MelonLoader’s required-game-version metadata.

Reinstall or sync

Use Reinstall / Sync when a game build is missing files, patch verification fails, or the loader must be regenerated. The installer restores known source bytes, reapplies required changes transactionally, and verifies the result.

GameRoot/loadouts/ and GameRoot/mods-cache/ are outside the game-version folder. Normal game reinstall does not remove them. Launcher-owned GameRoot, active-loadout selection, and the accepted official-core anti-downgrade version remain in the Launcher’s OS application-data Anomaly/launcher.json (Windows %APPDATA%; native application data on native Linux).

Identity during reinstall

The client identity is stored in the selected game’s MelonLoader UserData/Anomaly/user.json. Preserve that UserData directory when reinstalling or moving a game instance. The client reuses an existing local profile and creates a new identity when it is missing; it reads client profiles only from that instance-local directory. Protected identity fields remain bound to the original Windows user or Wine prefix.

When an update blocks launch

An official-core launch stops when the selected package is missing, unsigned, incompatible, incomplete, or modified. Do not bypass the gate. Install a compatible game build or wait for a signed Anomaly release that declares the new patch line.

Continue to Installing and Managing Mods.