Example: The Reunion "New Translation" / "Beacause" IRO could "declare" that it "depends on" the Reunion "Menu Overhaul" mod. If a user activates the first, 7H checks whether the second is also activated.
Implementation detail: In order for any "dependency management system" to work, it needs to be able to uniquely identify a mod/chunk, including it's specific version.
So, every mod's IRO should probably provide a GUID (if not done already) and a version.
If the style of the version string follows Semantic Versioning, it could support even a "range if versions", like "v6.0 or later".
Idea: Allow a mod to "depend on" another mod.
Example: The Reunion "New Translation" / "Beacause" IRO could "declare" that it "depends on" the Reunion "Menu Overhaul" mod. If a user activates the first, 7H checks whether the second is also activated.
Implementation detail: In order for any "dependency management system" to work, it needs to be able to uniquely identify a mod/chunk, including it's specific version.
So, every mod's IRO should probably provide a GUID (if not done already) and a version.
If the style of the version string follows Semantic Versioning, it could support even a "range if versions", like "v6.0 or later".