Verho Mod Manager

Getting started

1. Extract the download into an empty folder. Keep all extracted files together.
2. Close Verho and run Verho.ModManager.exe.
3. The manager attempts to connect to your game folder once on startup. Use Browse and Connect in App settings if the app doesn’t automatically find your Verho installation.
4. If the game already has mods or BepInEx settings, choose Import installed mods to bring them into the list.
5. Use Install BepInEx if it is not already installed.
6. Add your mod ZIPs or DLLs by dragging them into the mod list window or browsing to them via the Install mod button.
7. Review dependency warnings in the top left, if any.
8. Click Play Verho when ready. The manager deploys enabled mods, backs up saves and launches the game.

List changes are remembered automatically. Use Play Verho to apply them to the game; launching Verho elsewhere uses the last deployed mod files.

Disabling and uninstalling

Untick a mod to disable it while keeping its package in the manager. Tick it again to enable it without reinstalling.

Uninstall a mod to remove its entry and delete its stored package and README. Install its ZIP or DLL again if you want it back. Settings, original downloads and existing backups are kept. If a file is locked, deletion can be retried through Refresh checks or by restarting the manager.

Both actions take effect in the game on the next Verho launch. Neither changes an already running game.

Clear choices when game files differ

If game plugins have changed since the last deployment, the manager lists the mismatches before launching. Each file has separate Game directory and Current mod manager list details. Pending list edits and unticked mods are labelled separately from unexpected game folder changes.

• Overwrite mod manager with game files: import the game’s installed plugins and settings, replacing pending list changes.
• Overwrite game files with mod manager list: deploy your enabled mods and current settings, backing up existing game files first.
• Close window and don’t launch the game: leave both sides unchanged.

Save backups and separate playthroughs

The Saves tab manages complete save collections, including character slots and their shared indexes. You can create a named set from your current saves, start an empty set for another playthrough, or restore a backup. Restoring or switching saves creates a recovery backup first. You can also link a save set so the manager offers to switch to it when you launch.

Close Verho and let Steam Cloud finish syncing before restoring or switching saves. The manager does not edit individual characters or merge save slots.

Portable storage

Settings, stored mods and backups live in VerhoModManagerData beside the application. Game, mod and backup folders use readable names. Each fresh portable installation starts independently, with no automatic migration from older manager data. Moving the whole folder, including its data, carries that installation with it.

Installed BepInEx files and deployed mods still go into the game folder. Verho’s live character saves stay in their normal location.

Compatibility notes

Dependency checks read declarations from mod DLLs without running their code. They cannot detect undeclared requirements or every gameplay conflict, and dependency mods are not downloaded automatically. This release supports ZIP and DLL mod packages; RAR, 7z and preloader-only packages are not supported. It does not include an online mod catalogue.

The settings editor supports standard BepInEx configuration files. A mod may need to run once to generate its settings. Unsupported custom setting types remain read-only.