• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Jorlem

Field Marshal
118 Badges
May 9, 2012
4.582
4.152
  • Steel Division: Normandy 44 Deluxe Edition
  • Leviathan: Warships
  • Magicka
  • Surviving Mars
  • Europa Universalis IV: Res Publica
  • Victoria: Revolutions
  • Rome Gold
  • Semper Fi
  • Sword of the Stars
  • The Showdown Effect
  • Prison Architect
  • Rome: Vae Victis
  • War of the Roses
  • Knights of Pen and Paper +1 Edition
  • Cities: Skylines Deluxe Edition
  • Europa Universalis IV: El Dorado
  • Steel Division: Normandy 44
  • Hearts of Iron IV: Field Marshal
  • Europa Universalis IV: Common Sense
  • Hearts of Iron IV: Colonel
  • Cities: Skylines - After Dark
  • Knights of Pen and Paper 2
  • Europa Universalis IV: Cossacks
  • Hearts of Iron IV: Cadet
  • Stellaris
  • Crusader Kings III
  • Dungeonland
  • Arsenal of Democracy
  • Cities in Motion
  • Hearts of Iron IV: Expansion Pass
  • Victoria 3 Sign Up
  • Shadowrun Returns
  • Stellaris: Distant Stars
  • Cities: Skylines - Parklife
  • Hearts of Iron IV: Expansion Pass
  • Crusader Kings II: Jade Dragon
  • Tyranny - Bastards Wound
  • Tyranny - Tales from the Tiers
  • Darkest Hour
  • Ancient Space
  • Europa Universalis III
  • Europa Universalis III: Chronicles
  • Divine Wind
  • Stellaris: Lithoids
  • Europa Universalis IV: Art of War
  • Europa Universalis IV: Conquest of Paradise
  • Europa Universalis IV: Wealth of Nations
  • For the Motherland
  • Hearts of Iron III: Their Finest Hour
  • Heir to the Throne
I would like to suggest an additional function for the various launchers used by Paradox games: the ability to check for incompatibilities between mods.

The way I envision this, there would be an additional button on the Mod tab of a given launcher, that when pressed would "load" all of the mods selected as active without loading the actual game. This process would record any event of files with the same name and path being "loaded", and on completion would report these to the user either through a pop-up, or by creating a log file (or a pop up with an option to create said log file.) The way I'm think of it, it would look something like this:

The mods
[Mod A]
[Mod B]
[Mod C]​
all change the file(s)
[...\events\FILENAME.txt]​
and are therefore potentially incompatible with each other.

The mods
[Mod B]
[Mod D]​
all change the file(s)
[...\events\FILENAME_2.txt]
[...\common\on_actions\FILENAME_3.txt]​
and are therefore potentially incompatible with each other.
and so on.

This would make it far easier to determine which mods conflict with each other, something that has become rather more difficult thanks to how the Steam Workshop handles subscribed mods. (The workshop mods end up buried behind random ID numbers, and are often in zip files as well, making the sort of checking needed to find conflicts much harder to do manually than for non-Workshop mods.)