-
Notifications
You must be signed in to change notification settings - Fork 44
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
Feedback on why the version was considered incompatible #76
Comments
smth like |
The problem currently is that the checks are done by a single for loop and if statement (e.g curseforge checking) so this would probably require a completely different method to be used. But yeah this will definitely be a much better user experience |
And yeah for some reason Ars Creo is not adding even with the proper game version and mod loader |
I also found that |
Yes because the version is not mentioned in the actual asset name. Sigh we really have to overhaul the GitHub releases checking |
This hit my radar again so I checked the API myself. I checked all three of With my own API key and the file's there, but |
I don't know how the CF website works, but it probably uses a different internal API or somehow caches responses? This is an issue with CF, and I've contacted them on the discord CF Dev server and they just didn't reply at all. There's nothing I can do about this :( I suggest you download the mod and place it in the user folder for now |
Indeed not. Hence the actual request. |
At present, when a curseforge project is not considered compatible, that's all the user is told:
Could the error message be expanded to explain what filter(s) were not met among the files in the project?
In the above case, it turned out to be something governed by
--dont-check-game-version
but that was not at all obvious, especially as the mod in question does declare that it works for 1.18.2As of this writing, the newest file for Ars Creo is https://www.curseforge.com/minecraft/mc-mods/ars-creo/files/3776248
Which is flagged for
1.18.2
andForge
The text was updated successfully, but these errors were encountered: