You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
The text was updated successfully, but these errors were encountered:
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".
The text was updated successfully, but these errors were encountered: