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

Check for compatibility with the mod loader version #403

Closed
soup587 opened this issue Feb 21, 2024 · 5 comments
Closed

Check for compatibility with the mod loader version #403

soup587 opened this issue Feb 21, 2024 · 5 comments
Labels
enhancement Improvements to the project

Comments

@soup587
Copy link

soup587 commented Feb 21, 2024

The Problem

Not sure if there's a feature already for this and I just can't find it, but there doesn't seem to be a way of managing the specific version of an installed modloader for a profile.

This causes issues as it seems Ferium just uses the latest version at the time of making a profile, which will eventually lead to mods being incompatible as they update past the currently installed version.

Your Solution(s)

No response

@soup587 soup587 added the enhancement Improvements to the project label Feb 21, 2024
@theRookieCoder
Copy link
Collaborator

Unfortunately it would be very difficult to support this since mods only specify the mod loader version in their manifests, which can only be read after the mod file is downloaded. Ferium relies on the information provided by mod authors on websites like modrinth and curseforge, and cannot download every file to check for compatibility.

As for unintended updates, #82 plans to add the ability to lock a mod to a specific version.

@theRookieCoder theRookieCoder closed this as not planned Won't fix, can't repro, duplicate, stale Mar 14, 2024
@soup587
Copy link
Author

soup587 commented Mar 30, 2024

so i'm just stuck unable to update mods because i'm stuck on an old forge version? unless i make a new instance???

@theRookieCoder
Copy link
Collaborator

Could you explain your exact situation here? I don't quite understand since I haven't used Forge in many years.

@fenhl
Copy link

fenhl commented Jun 1, 2024

I think this is relevant for Fabric as well. Would be nice if Ferium could just update the Fabric loader to latest when there's an update available. From what I understand, this should not cause compatibility issues with mods.

@theRookieCoder theRookieCoder changed the title Ability to update modloader version Check for compatibility with the mod loader version Jun 1, 2024
@theRookieCoder
Copy link
Collaborator

I think this is relevant for Fabric as well. Would be nice if Ferium could just update the Fabric loader to latest when there's an update available. From what I understand, this should not cause compatibility issues with mods.

I think you misunderstood the title of this issue (I've edited it now to reflect what OP actually asked for). Anyways I believe updating the loader version is the responsibility of the launcher (or the user in case of the Mojang launcher). If #212 gets implemented it would make sense, but at the moment ferium deals with downloading mods and modpacks, not minecraft itself or mod loaders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvements to the project
Development

No branches or pull requests

3 participants