Closed Madis0 closed 1 year ago
To note:
It would be beneficial to allow mods to specify their own location, or their own maven (MineLP/HDSkins/Mson all have one) for discovering updates.
Idea, mod specifies an "update strategy" of which there are multiple builtin in their fabric.mod.json
.
Maven:
{
"custom": {
"modMenu:updateStrategy": {
"type": "maven",
"mavenGroup": "com.example",
"mavenArtifact": "mod"
}
}
}
CurseForge:
{
"custom": {
"modMenu:updateStrategy": {
"type": "curseforge",
"curseforgeSlug": "example"
}
}
}
GitHub Releases:
{
"custom": {
"modMenu:updateStrategy": {
"type": "github",
"githubRepo": "example/me"
}
}
}
versionRegExp
is an optional property in modMenu:updateStrategy
, ModMenu would determine the latest version by picking the latest version that matches this RegExp.
versionRegExp
would be useful for maven
or github
when the latest version might be for a different MC version, while curseforge
could automatically check.
This is out of scope for modmenu imo, though modmenu could provide hooks for other mods to do that.
it only makes sense for mod menu to do this
My proposal has been implemented in https://gitea.thebrokenrail.com/TheBrokenRail/ModUpdater.git and will be listed on CurseForge at https://www.curseforge.com/minecraft/mc-mods/modupdater when approved.
Btw, Modrinth exists now, so that's one more source you (probably) have to add an option/api for...
I do actually have plans to add an update checker at some point, and it will likely be Modrinth exclusive.
My proposal has been implemented in ModUpdater
There is another mod, even better than ModUpdater – ModManager (GitHub)