Repository navigation
Releases
ZCOM Mod Manager v0.6.5
See CHANGELOG.md for release notes. Community builds are unsigned.
ZCOM Mod Manager v0.6.2
See CHANGELOG.md for release notes. Community builds are unsigned.
ZCOM Mod Manager v0.6.1
See CHANGELOG.md for release notes. Community builds are unsigned.
ZCOM Mod Manager v0.6.0
See CHANGELOG.md for release notes. Community builds are unsigned.
ZCOM Mod Manager v0.5.3
See CHANGELOG.md for release notes. Community builds are unsigned.
ZCOM Mod Manager v0.5.0
See CHANGELOG.md for release notes. Community builds are unsigned.
ZCOM Mod Manager v0.4.1
See CHANGELOG.md for release notes. Community builds are unsigned.
ZCOM Mod Manager v0.4.0
See CHANGELOG.md for release notes. Community builds are unsigned.
ZCOM Mod Manager v0.3.0
ZCOM Mod Manager 0.3.0
This release is about mods the manager previously could not handle, and about
managing the ones it could.
Mods that now install
- UE4SS DLL mods. A mod folder is recognized by
Scripts/main.luaor
dlls/*.dll, so native mods install like any other. - Archives with several mods. Each mod folder becomes its own entry, so
mods that shipped together can be enabled, ordered, and removed separately. - Windows-packed archives. ZIPs written with
\separators extracted as
files with backslashes in their names, so the mod layout never appeared and
the archive looked unrecognized. Both separators now work everywhere. - Game-folder mods. ReShade and other loader shims, replacement movies and
audio, andLogicModsblueprint packs. This is the only kind that replaces
a file the game shipped: the original is kept and restored when the mod is
disabled or removed, and a file another mod owns is never overwritten. - UE4SS runtime packages dropped on the installer are recognized as the
runtime instead of being taken apart into the mods they ship.
Names you recognize
Mods are named from the download rather than from the first file inside it,
with Nexus publishing metadata removed — ZCUnlocked 34 1.3 2026-08-30T07-32Z i9WZfkaQ7.zip installs as ZC Unlocked, version 1.3. Names are editable
before installing and can be changed at any time from the library.
Updating a mod
Installing a newer build of a mod you already have is recognized during
inspection: the preview offers to replace the installed version instead of
reporting a deployment conflict. The previous version's files are moved aside
rather than deleted, so a failed upgrade puts them back and leaves the old
version installed, and the replacement keeps its position in the load order.
UE4SS start order
Mods → Load order now manages UE4SS start order by rewriting the managed
entries of mods.txt; comments and the runtime's own entries keep their place
and no deployed file is renamed. UE4SS starts mods in two passes — every DLL
mod as the runtime initializes, the Lua mods once the scripting runtime exists
— so the editor sets order within each pass rather than across them. Mods
installed before this release keep the order your file already has.
Also
- The UE4SS mod count on Home and in diagnostics includes DLL mods.
- The load-order tab says where the mods it does not list are ordered instead.
- Fixed doubled event subscriptions: one dropped archive was inspected twice,
and onenxm://link would have downloaded twice. - Library row actions are laid out as two rows of three.
See KNOWN_LIMITATIONS.md for what is still out of scope, including
BPModLoader's separate blueprint load order. Community builds are unsigned.
ZCOM Mod Manager v0.2.0
See CHANGELOG.md for release notes. Community builds are unsigned.