-
Notifications
You must be signed in to change notification settings - Fork 1
License #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
Comments
In order to add a license I'd first have to ..... care. I picked the all rights reserved because the number of options is long, confusing, and full of legal-sounding mumbo-jumbo I couldn't be bothered to read or care about. |
Well, as it happens, I'm the head of the FTB 3rd party pack system. So I spend a lot of time check packs for distributions permissions. Since there are a number of mod authors that do care, I try to be very strict about letting people add mods to their packs unless there's a specific statement from the author saying they have permission. |
As a pack developer it is very unnerving for a mod, especially a coremod, to have such a reluctant stand on permissions. It gives me a bad first impression on your team, and I have debated on whether to keep it in my pack or to leave it out. Thank you. |
Then simply don't make mods if your too lazy to do anything. |
This is mostly a formality, but RedGearCore is technically listed as all rights reserved on curse and has no license here. I haven't been able to find a statement from you anywhere else officially saying it's okay to include in modpacks.
Would you mind adding a license?
The text was updated successfully, but these errors were encountered: