Skip to content
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 *.jars #30

Open
maradotwebp opened this issue Jun 20, 2021 · 4 comments
Open

Export directly to *.jars #30

maradotwebp opened this issue Jun 20, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@maradotwebp
Copy link
Owner

PAX is currently only able to export Curseforge-compatible modpacks with the manifest.json. Exporting to a .zip that contains the *.jars directly would also be very nice.

@rlnt
Copy link

rlnt commented Jun 20, 2021

This will probably cause licensing issues because of distribution. There would have to be proper credits for each individual mod.

@maradotwebp maradotwebp added the enhancement New feature or request label Jun 20, 2021
@maradotwebp
Copy link
Owner Author

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.

@rlnt
Copy link

rlnt commented Jun 20, 2021

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.

@juraj-hrivnak
Copy link
Contributor

Exporting the *.jars to a folder without a .zip would be useful too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants