MO2
PCA's own MO2 integration was removed. PCA no longer scans your mods folder, and the mo2 instance setting does nothing.
Run PCA through MO2 instead — see below. If the option is still enabled in your settings, PCA shows a warning; turn it off.
Why it was removed
The integration rebuilt the merged Data folder by hand and passed every mod folder to the compiler.
It broke in two ways that could not be fixed from PCA:
- the command line grew with the number of mods and hit the Windows limit — see Command line is too long;
- when several mods shipped a script with the same name, the wrong one could be compiled.
Running PCA as an MO2 executable gives it the real virtual file system, which does both correctly.
Using Vortex instead? It needs nothing of the sort, see Vortex.
Run PCA through MO2
- Open MO2, then the executables dialog (the gears icon).
- Add a new executable.
- Title:
PCA - Binary: the path to
PCA.exe - Start in: the folder holding
PCA.exe
- Title:
- Confirm, then start
PCAfrom the MO2 launcher dropdown.
PCA now sees Data the way the game does, mods included, and no configuration is needed on its side beyond the usual one.
You can create one entry per instance and pass the configuration on the command line, so each one opens on the right game. Refer to Application Parameters.