Add same mod with different versions as required/recomended/optional
Posted: Fri Jun 26, 2026 12:53 pm
So this doesn't work right now, but with the introduction of the "recommended mod" dependency category coming in 2.1, I would love to see this.
When you make a mod, you can list other mods as required, incompatible, or optional (or recommended in 2.1+)
But you can't set different versions of the same mod in those different categories.
For example, I have a mod that is compatible with version 2.0.0+ of LTN.
But due to some changes in LTN (fixing errors in API output), I would recommend that version 2.8.1+ is used, since that gives a better experience.
If it is still functionally usable with the older versions, but would really recommend using a more up-to-date version since that works better or allows more features, that currently can't be indicated.
I can only go "required 2.8.0+" in newer updates and not let people have the fixes in newer version that I made, if for whatever reason they want to use for example 2.6.2, even though my updated mod would still function with that version of LTN.
When you make a mod, you can list other mods as required, incompatible, or optional (or recommended in 2.1+)
But you can't set different versions of the same mod in those different categories.
For example, I have a mod that is compatible with version 2.0.0+ of LTN.
But due to some changes in LTN (fixing errors in API output), I would recommend that version 2.8.1+ is used, since that gives a better experience.
If it is still functionally usable with the older versions, but would really recommend using a more up-to-date version since that works better or allows more features, that currently can't be indicated.
I can only go "required 2.8.0+" in newer updates and not let people have the fixes in newer version that I made, if for whatever reason they want to use for example 2.6.2, even though my updated mod would still function with that version of LTN.