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
Add the ploceus version to the mod jar manifest as a way to recognize the mod as built with Ornithe intermediaries.
Or at least something that will differentiate/identify Ornithe mods.
It will come in handy the day we manage to get mods built with different intermediaries running together.
The text was updated successfully, but these errors were encountered:
That's a good idea. I was thinking about this and we'll probably want to add something to our intermediary jar manifest as well, and copy that into the mod jar manifest after building.
haven't yet looked into that side of it, but does Loom provide an API for adding to the mod's jar manifest, or should Ploceus just hook into Gradle for that?
Loom doesn't seems to provide an API for it, but you can hook into AbstractRemapJarTaskdoLast and modify the jar manifest at this moment. That's what I've done in legacy-looming.
Add the ploceus version to the mod jar manifest as a way to recognize the mod as built with Ornithe intermediaries.
Or at least something that will differentiate/identify Ornithe mods.
It will come in handy the day we manage to get mods built with different intermediaries running together.
The text was updated successfully, but these errors were encountered: