Version and compatibility first

The publisher lists 1.1.0 as the stable release and 1.2.0-nightly.20260930.52872bb6 as a pre-release. The nightly includes a 30 September update to the depot’s gameinfo.gi. That change is relevant after City Never Sleeps; neither release record guarantees that every cosmetic mod works with client 6745.

The steps below use the versioned release documentation’s Mods and My Mods interface. Main-branch documentation now describes different pages, so do not combine those labels with a stable build. Use the publisher’s actual release assets for your operating system; this guide does not establish macOS support or a blanket safety guarantee for third-party files.

Set up and install one cosmetic mod

  1. Preserve a copy of existing addons and any manually edited gameinfo.gi. Close Deadlock before testing a changed setup.
  2. Install the chosen manager release, allow Steam-directory detection, and verify the detected game path. Game Ready is the documented detection signal; Vanilla means the original game configuration.
  3. If previous manual configuration prevents a clean setup, preserve it before using Steam’s file verification. The manager documentation says it first changes gameinfo.gi when Launch Modded is used.
  4. In Mods, open a listing and check its author, requirements, files and variants. Choose Download Mod and wait for the download to finish.
  5. A downloaded mod starts disabled. Use Enable Mod, then check it in My Mods.
  6. Use Launch Modded and inspect the intended cosmetic in-game. A manager checkmark confirms its managed state, not that the replacement rendered correctly.

Manage conflicts and load order

My Mods provides Enable/Disable and Uninstall. Analyze Local Addons tries to identify existing VPKs; an unmatched custom file is not automatically known compatible. To adjust order, use the ordering control beside Analyze Local Addons, drag the entries and save. Ordering renumbers game-visible VPK files and can change which replacement wins; it cannot make every conflicting pair compatible.

Restart the game for a reliable test after changing files. The old guide says some toggles act immediately, but its troubleshooting also recommends restarting; do not infer that an already-loaded asset must update live.

Recover and judge the result

If the cosmetic does not appear, disable it and check the game without that change. If the modded launch fails, use the manager’s vanilla launch if available in your installed version, or restore the preserved gameinfo.gi and addon setup before launching through Steam. Steam verification restores managed game files; it is not a substitute for backing up custom addon files or a promise to remove every manual mod.

After a game patch, retest one mod at a time. Keep a mod disabled when its files or requirements no longer match. These are documented setup and recovery steps with current release boundaries; this site has not installed the manager or validated an individual mod in a game client.

References