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
May not be related, but it's currently not possible to omit the "loaders" field when publishing resource packs to modrinth, even though the web form doesn't support that field.
Oh, wow, it's already been a year. To be quite frankly honest with you, I don't have anything new to add compared to #52 (comment):
mc-publish doesn't support resource packs, modpacks, etc., only in the sense that it doesn't currently perform automagic value resolution for certain properties like it does for mods.
You can still use mc-publish if you provide those values manually, as in this case, mc-publish merely serves as a unified wrapper over the GitHub/CurseForge/Modrinth APIs.
I'm wrapping up work on full-featured support for different project types.
In your case, the Modrinth API is complaining about loaders.length being 0(because whatever you specify in the loaders field will be automatically filtered out if your project type doesn't support it). Labrinth always requires this field to be populated, even though this may be hidden from you in their web interface. So, let's go back to Modrinth's /tag/loader endpoint. If you inspect its response, you'll see that the value Modrinth expects from you is minecraft. It's as simple as that:
loaders: minecraft
Once full support for more project types is upstreamed from my local efforts, mc-publish will be able to supply that value for you automatically. Unfortunately, it doesn't know how to handle that just yet.
Current Behavior
Publishing a resource pack to Modrinth fails
Desired Behavior
May not be related, but it's currently not possible to omit the "loaders" field when publishing resource packs to modrinth, even though the web form doesn't support that field.
Alternative Solutions
No response
Other Information
returning from shaders support: #52
The text was updated successfully, but these errors were encountered: