Mo2 Compatibility

[Noggog]

MO2 Virtual File System Compatibility

MO2's virtual file system (USVFS) is incompatible with .NET SDK builds. The VFS cannot properly handle the file access patterns used during compilation, frequently resulting in "Access is denied" errors.

This is annoying, but not the end of the world.

The Workaround

Synthesis supports a "build once, run safely" workflow:

1. Build outside MO2 – Run Synthesis directly (not through MO2) to download and compile your patchers
2. Run inside MO2 – Once built, launch Synthesis from within MO2 for your actual patching runs

Synthesis tracks build metadata and recognizes when patchers are already compiled. When running inside MO2, it skips the problematic build step entirely and executes the pre-built binaries directly.

Automatic Detection

Synthesis detects when it's running inside MO2's VFS and can identify Access Denied errors during builds. When this happens, the UI will prompt you with an explanation and suggest running outside MO2 to rebuild.

You can also enable "Block Building Within MO2" in Advanced Settings to proactively prevent build attempts inside the VFS, avoiding the errors entirely.