-
Notifications
You must be signed in to change notification settings - Fork 3
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
Export directly to *.jar
s
#30
Comments
This will probably cause licensing issues because of distribution. There would have to be proper credits for each individual mod. |
Hm. You mean proper credits as in a modlist.txt,or proper credits as lookup the license on how each mod can/should be distributed? How does Curseforge handle this with server packs then? Imo for now I would just offload that responsibility to the users themselves, since they are the ones distributing the mods. |
I agree that offloading it to the authors is the best option. As far as I know, CurseForge is including that in their ToS. The serverpack is hosted on CurseForge. Therefor you are only allowed to include CurseForge hosted mods in it which solves the licensing problem. |
Exporting the |
PAX is currently only able to export Curseforge-compatible modpacks with the
manifest.json
. Exporting to a .zip that contains the*.jar
s directly would also be very nice.The text was updated successfully, but these errors were encountered: