NOTE: I wish I could say that these were still obsolete, but some players are currently unable to merge Legion with other mods due to a bug in CMM, so I am temporarily reviving these. Three of these mods are temporarily in CMM now, which means they don't need to be installed manually.
Unless using the Merge Mod feature of a mod like Community Mods, multiple unit-adding mods cannot be used together unless one of the following is true:
- One mod requires another to work (so the last-to-load mod is aware of the mod it requires)
- A compatibility patch is used to make the mods aware of each other
Such a compatibility patch should:
- Be a server mod
- Have a lower priority value (so it loads last)
- Include the union of the values in
unit_list.json
andcommander_list.json
files if relevant
The DAEDALUS ComPatches aim to accomplish this in a simple, consistent way.
The DAEDALUS ComPatches aim to support any combination of:
Note that CMM's merge feature still works fine for all players if they are using Second Wave with Section 17, but without Legion; this ComPatch is still available for download, but it is obsolete.
Any combination of mods requires a specific ComPatch, head over to the Releases section and look for the ComPatch which fits your desired setup.
- Install the ComPatches like any other mod.
- I recommend installing only the Legion + 2W patch or the Legion + S17 patch; if you want to use all three mods together, either 2W or S17 will merge in fine with the other ComPatch.
- If the ComPatch covers the full range of mods you're using, don't worry if you don't see a "Merge Mods" button appear. Clicking on it if it does appear should not be an issue.
- If the "Merge Mods" button is enabled, it doesn't matter if you have multiple ComPatches enabled or not, but try to avoid having one that is too large.
CMM is temporarily unable to merge Legion and/or Bugs with other unit addition mods, which means that these compatibility patches will be relevant once more until this bug is fixed. Since many users of CMM are not familiar with manual mod installations, here is a basic tutorial:
- Navigate to where your
server_mods
folder should be. For most Windows users, this is probablyC:/Users/[username]/AppData/Local/Uber Entertainment/Planetary Annihilation
- If you do not see a folder called
server_mods
at this location, make a folder calledserver_mods
. - Extract any desired ComPatches into this folder. Make sure that each ComPatch has its own folder and that each of these folders has a file called
modinfo.json
in them. Ifmodinfo.json
is instead inside a folder nested within a folder inserver_mods
, this mod will not be identified.modinfo.json
MUST BE at the top level of the mod's folder. - Make sure that mod folders do not have any capital letters in their names. This broke old CMM. I haven't been able to test with new CMM yet, but it's likely to still break new CMM.
- The mod is installed now. Go to CMM and click on the "Installed" tab; look for the ComPatch in your list of installed mods. It should probably be "installed" but not "activated". Click on the mod and click the "Activate" button.
- Make sure to only have ONE ComPatch active at a time. Multiple active ComPatches may lead to undefined behavior.
- Unlike the normal approach to merging mods, do NOT enable the "Merge (experimental)" feature in CMM when a ComPatch is on. Enabling it while using a ComPatch may lead to undefined behavior.
- If you deactivate or activate a new unit-adding mod, make sure to deactivate the current ComPatch and activate a new one (if necessary).
- Bugs
- Union
- Assimilation