Follow the author’s setup
The v1.1.0 description directs users to extract the manager into a writable folder, run it and check the detected Steam game folder. Use File → Set game folder if detection fails. Its stated prerequisite is Windows’ .NET Framework 4.x.
The download page currently labels its virus scan “Some suspicious files.” We have not downloaded or executed the manager. Review the current author files and source before deciding to run it. Author’s Nexus page.
The author also publishes source code with a Windows build command. GZModManager source repository.
Choose a format and apply changes
The author lists support for Pak, UE4SS and blueprint mods. Add the chosen archive or folder, enable the desired entries and inspect conflicts and load order before Deploy. Extract unsupported archive formats into a folder first.
Use a small, documented change for the first run. Keep the downloaded mod’s own game-version and dependency requirements alongside your setup. A manager supporting a file format does not establish that a particular mod works with your current game build.
Return to your previous setup
The author describes Purge as removing deployed files and restoring replaced files from its backups. Keep a record of anything installed manually, since a manager’s deployment history only accounts for changes it manages. Its description also instructs users to switch UE4SS off before online play. Deployment and Purge documentation.
This guide summarizes the author’s workflow and the decisions to check before deploying. Installation, rollback and multiplayer compatibility have not been tested by this site. For native all-monster local access, first check Tournament Mode. For normal save progression, use the Lab planner.