Mod is tagged as "Unsupported" on client side on modrinth?
Einhornyordle opened this issue ยท 10 comments
When I added the mod to Modrinth "unsupported" wasn't even an option. It was either yes or no. I guess we can choose "optional" now, which is what I just set it to.
You can manage your claims with commands without the client side though.
Huh, that's weird. Cause I only noticed that after trying to install a modpack via the AT Launcher and I know that it worked before, just after the recent update the mod was gone since it doesn't download unsupported mods. Maybe Modrinth added the option in the last update they had.
Anyway, would you mind double-checking if your change (setting it to optional on the client side) went through? Because it still shows up as unsupported to me and therefore still won't download while Modrinth usually is rather quick with changes like that.
I changed it to optional again and it doesn't work. Goes right back to unsupported. Awesome stuff.
Huh, I did notice that the last Modrinth update caused some issues but I didn't know it went that bad.
Changing it to "required" worked. Changing it to "optional" after that worked too.
can confirm, it now shows required for me as well. Anyway, thank you for your time!
It also takes extremely long for it to save. Setting it to "required" seems to work for now.
No problem. Thanks for letting me know about this. Can't set server side to optional for my map mods either.