Yet Another Zombie Survivors mods currently form a small third-party Nexus ecosystem rather than a mature Steam Workshop catalog. The collected setup uses BepInEx 6 IL2CPP build 725 for Windows 64-bit and places Easy Mode in BepInEx/plugins, but compatibility with version 1.0 and later hotfixes must be checked before installation. Back up saves, use original Nexus or author pages, install one component at a time, and remove the plugin when the game behaves unexpectedly.
What mods are actually available
The current Nexus page contains only a small number of files in the collected search results. Easy Mode is the main named quality-of-life option supported by an original Nexus listing and a public source repository. Do not describe the game as having a large content-mod ecosystem when the evidence only supports a limited toolset.
The public code makes Easy Mode more reviewable than an unknown packaged executable. Its cheat-like configuration options are disabled by default according to the collected author information. That design choice does not prove compatibility with every 1.0 hotfix or remove the need for backups.
Check BepInEx compatibility first
The collected installation material names BepInEx 6 IL2CPP build 725 for Windows 64-bit as the common prerequisite. 待确认：check the current mod page and author repository before assuming that build still matches the installed game version. A loader built for another architecture, game build, or runtime can fail before the plugin itself is evaluated.
Record the game version, store platform, loader version, and mod version before changing files. Those four fields make later troubleshooting specific instead of reducing every failure to “the mod is broken.” Keep the original download archives only from the named source so the installed files can be compared reliably.
Install Easy Mode in a controlled order
Install the compatible BepInEx package, extract Easy Mode, and place its files in the game's BepInEx/plugins directory. Start the game once and exit so the plugin can create its configuration, then edit the matching file under BepInEx/config. Restart the game after saving the configuration and verify one intended change at a time.
Do not install several plugins during the same first launch. A single-plugin baseline tells you whether the loader, Easy Mode, or another component caused an error. Keep all options at their defaults until the unmodified plugin is shown to load on the current version.
Back up and isolate the test
Copy the save and relevant configuration before installing a loader or plugin. Use a separate test save when a mod can alter progression, achievements, resources, or run behavior. This keeps a failed experiment from becoming the only available save state.
Install from Nexus or the author's public repository rather than a mirror or repack. Review the update date, version notes, source, and recent user reports before executing third-party files. Do not disable all security protections merely because an unknown archive requests it.
Update after a game patch
Version 1.0 and its 1.0.0a and 1.0.0b hotfixes demonstrate why compatibility can change quickly. After a game update, check the loader and plugin pages before launching the modified setup. Wait for author confirmation when the current versions are not listed as compatible.
Update one layer at a time and retain the previous known files outside the active game folder. Start with the loader baseline, then add Easy Mode, then add any other plugin. This order identifies the component that reintroduces the failure without guessing.
Disable or remove a mod
Exit the game completely before moving the relevant plugin DLL out of BepInEx/plugins. Keep the file in a clearly named inactive folder outside the live plugin directory if you may need it for comparison. Restart the game and check whether the problem disappears with the plugin absent.
Removing a DLL may not reverse progression or configuration changes already saved. Restore the backup only when necessary and after preserving the current files for diagnosis. Do not delete the only copy of a save during troubleshooting.
Troubleshoot one layer at a time
Confirm the game version and mod version, remove every optional plugin, and test BepInEx alone. Add Easy Mode back by itself, retain the generated logs, and verify the game files if the unmodified game also fails. A log and a one-change test provide stronger evidence than repeatedly reinstalling unrelated packages.
If the plugin stops loading after a hotfix, remove it and wait for an author update rather than downloading an unknown “fixed” executable. Continue to the trainer safety guide or Cheat Engine guide only when the question concerns those distinct modification methods. Trainer, Cheat Engine, and BepInEx compatibility problems should not be treated as interchangeable.