musicolever/-czt-mod-manager-complete-mod-solution-for-dying-light

This repository is named CZT Mod Manager Complete Mod Solution for Dying Light, but the README inside actually pitches the same tool as a mod manager for a different game called Schedule I. The text describes a Windows application that installs and uninstalls mods for the Steam version of Schedule I, with one-click install, an on or off toggle for each mod, load order control on the F2 key, and update checks through the Nexus Mods API. The README does not link to a release on GitHub. Instead the big download button points to an external page on shawonline.co.za, which is unusual for an open source project and is worth flagging before running anything from it. According to the README, the tool keeps mods in a separate folder and uses Windows symbolic links to expose them to the game at launch, so the original game files stay untouched. It claims support for .pak archives plus .asi.dll.bank.png.mp4.ogg and plain folders, and accepts .zip.rar, or .7z drops with automatic extraction through an UnRAR tool that you install during setup. Mod profiles let you save different loadouts and switch between them, and a _mod_info.json manifest lets mod authors prefill the info shown in the interface. The stated workflow is: run Setup.exe, click the SETUP button to pick a drive that will hold the mod storage root, install UnRAR, let the tool auto-detect the Steam install of Schedule I or point it at the install folder by hand, drag mod archives into the window, set the load order with F2, then press PLAY to launch the game with the chosen mods active. An optional Nexus API key turns on version checks for installed mods. The README lists Windows 10 or 11 as required, with 500 MB of free space, and says Linux, Steam Deck, the Epic Games version, and pirated copies are not supported. It recommends enabling Windows Developer Mode so the symlink calls work without extra prompts, or otherwise running the program as Administrator. No source code structure, license, or build instructions are described in the README itself.