Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency management system #34

Open
picklejar76 opened this issue Jun 4, 2019 · 0 comments
Open

Dependency management system #34

picklejar76 opened this issue Jun 4, 2019 · 0 comments

Comments

@picklejar76
Copy link

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".

TurBoss pushed a commit that referenced this issue Jul 25, 2021
Fix also minor bug happening while backupping/restoring the FFNx.toml file through the FFNxConfigManager class.
TurBoss pushed a commit that referenced this issue Dec 31, 2022
Fix also minor bug happening while backupping/restoring the FFNx.toml file through the FFNxConfigManager class.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant