Legacy Dep Warning/Repo

[KeystrokeCascade]

Is your feature request related to a problem? Please describe.
Since the update to Deli that caused a split between legacy mods and the new 3.0 mods, I was having a bunch of trouble with my mod install where some were updated and some where not, which is understandable. To remedy this, I basically just deleted all the mods, re-installed the Mod Installer and started downloading them again.

The problem I ran into was that there is no way to tell which mods use legacy deps, and which use the new ones, meaning if you download a mod with them it downloads the legacy dependencies and then everything conflicts and it's very annoying.

Describe the solution you'd like
The ideal solutions would be to either have a tag or column added that tells you if a mod has any legacy dependencies, or perhaps a separate repository entirely.

While I only know a little bit of C programming and not enough to help by adding a column, I do know that a repository can be defined in the json settings file for Mod Installer (as seen below).

A separate fork or project could be created for a legacy repository, of which the contents are what the current Mod Installer Database was right before Deli 3.0 dropped and it never needs to be updated again. Then you could remove any mods that require the legacy version of Deli from the Mod Installer Database, and any legacy mods that get updated can be moved over.

Additional context

[Frityet]

Apologies for late reply, but we would rather phase out legacy mods all together rather than support them

[KeystrokeCascade]

That's also fine, it's just this intermediate period where everything is getting switched over. Will there be a cut-off date where you remove dead mods that won't be updated anymore then?

[Frityet]

Most likely not, we may add a warning that the mod is very old, but id rather not remove mods