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
The user is running version 2.6.11 (marked as Fabric) on Quilt. By giving the hash of that file to Modrinth's update route filtering for quilt mods, it will return version 2.6.10 because that is the latest version marked as Quilt on Modrinth. Modrinth should see that the given version is more recent than the latest Quilt version and return nothing for that, instead of suggesting an older version just because it fits the mod loader.
Perhaps a query param could be added to bypass this, but I think this should be the default as it would be the intended result in any case I can think of. An "update" route should never downgrade you.
Steps to reproduce
No response
Expected behavior
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I think by default should the route ignore loaders (or maybe make fabric include quilt?) and have a loader query param to define the loaders to respect here...
pretty sure you just described the current behavior? The problem is that when you're requesting a Quilt mod but you're running a more recent version that isn't listed as supporting Quilt, it can suggest an old version trying to match the loader when it should just never return an older version no matter what loader the provided one is for.
Describe the bug
Edit: The example below is no longer the case because the author updated it, but at the time it was true.
For example, this mod: https://modrinth.com/mod/fastload/versions
The user is running version 2.6.11 (marked as Fabric) on Quilt. By giving the hash of that file to Modrinth's update route filtering for quilt mods, it will return version 2.6.10 because that is the latest version marked as Quilt on Modrinth. Modrinth should see that the given version is more recent than the latest Quilt version and return nothing for that, instead of suggesting an older version just because it fits the mod loader.
Perhaps a query param could be added to bypass this, but I think this should be the default as it would be the intended result in any case I can think of. An "update" route should never downgrade you.
Steps to reproduce
No response
Expected behavior
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: