Kerbin 2x With Clouds (OPM 2X)

[Kevin Vandy]

...

Edited November 20, 2016 by Kevin Vandy
Removed links

[Streetwind]

Recommendation: You might want to get your thread moved to Add-On Releases, where all the other mod threads are.

Additionally, you must follow the Add-On Posting Rules. Specifically, you must include your license in the download, as well as in the place you advertise your mod for download (AKA this thread).

Finally, if you package other mods, as you have done, you must honor the terms of their licenses. All the terms, of all of their licenses. This may mean that you must select a different license for your own mod than you originally intended, because some mods have a license that stipulates that any redistribution must happen under the exact same license as the original. Which may be different from the license you might want. And it may result in two or more of the mods you wish to bundle having incompatible licenses, which results in you being unable to legally offer them in the same download. If you need help figuring things out, try asking in the License Selection Guide thread.

You can get around this problem in several ways:

1.) Offer a CKAN bundle file for download instead of a bundle of the actual mods. Users import this file into CKAN, which will automatically download all the required mods.

2.) Ask the mod authors of the conflicting mods for permission to redistribute their mods in your bundle with your chosen license. If they agree, you can link to that permission in your thread, and are absolved of having to mash incompatible licenses together. (Of course, you must also be prepared to receive 'no' for an answer.)

3.) The easiest and most common solution: Just write an install instructions section in your post, linking to the threads of the mods you consider required, and tell people to download them separately.

Regardless of which solution you pick: it is considered common courtesy to include in your forum thread and your download a link and a license statement for every mod that ends up bundled in your download, even if it is perfectly legal and license-compatible for you to do so. In case of mods with licenses that specifically require attribution, this is doubly a good idea, because that is literally what 'attribution' means.

 

(This whole license hullaballoo is why 'modpacks' like yours are extremely rare in the KSP community. As individual mods are so easily downloaded and installed, it's usually not worth the trouble.)

Edited November 18, 2016 by Streetwind

[stibbons]

The spacedock thread 

1 hour ago, Streetwind said:

Finally, if you package other mods, as you have done, you must honor the terms of their licenses. All the terms, of all of their licenses. This may mean that you must select a different license for your own mod than you originally intended, because some mods have a license that stipulates that any redistribution must happen under the exact same license as the original. Which may be different from the license you might want. And it may result in two or more of the mods you wish to bundle having incompatible licenses, which results in you being unable to legally offer them in the same download. If you need help figuring things out, try asking in the License Selection Guide thread.

The problem right now is that at least one of the mods currently included here is distributed under an All Rights Reserved clause. Redistribution, especially in a package that claims to be MIT-licensed as the spacedock entry for this pack does, is only allowed with the express permission of the author. This really does need to be fixed immediately.

[Red Iron Crown]

2 hours ago, Streetwind said:

Recommendation: You might want to get your thread moved to Add-On Releases, where all the other mod threads are.

Additionally, you must follow the Add-On Posting Rules. Specifically, you must include your license in the download, as well as in the place you advertise your mod for download (AKA this thread).

Finally, if you package other mods, as you have done, you must honor the terms of their licenses. All the terms, of all of their licenses. This may mean that you must select a different license for your own mod than you originally intended, because some mods have a license that stipulates that any redistribution must happen under the exact same license as the original. Which may be different from the license you might want. And it may result in two or more of the mods you wish to bundle having incompatible licenses, which results in you being unable to legally offer them in the same download. If you need help figuring things out, try asking in the License Selection Guide thread.

You can get around this problem in several ways:

1.) Offer a CKAN bundle file for download instead of a bundle of the actual mods. Users import this file into CKAN, which will automatically download all the required mods.

2.) Ask the mod authors of the conflicting mods for permission to redistribute their mods in your bundle with your chosen license. If they agree, you can link to that permission in your thread, and are absolved of having to mash incompatible licenses together. (Of course, you must also be prepared to receive 'no' for an answer.)

3.) The easiest and most common solution: Just write an install instructions section in your post, linking to the threads of the mods you consider required, and tell people to download them separately.

Regardless of which solution you pick: it is considered common courtesy to include in your forum thread and your download a link and a license statement for every mod that ends up bundled in your download, even if it is perfectly legal and license-compatible for you to do so. In case of mods with licenses that specifically require attribution, this is doubly a good idea, because that is literally what 'attribution' means.

 

(This whole license hullaballoo is why 'modpacks' like yours are extremely rare in the KSP community. As individual mods are so easily downloaded and installed, it's usually not worth the trouble.)

@Kevin Vandy Please read the above, we take mod licensing very seriously here as it protects both modders and users. The links in your post have been removed until you can resolve the licensing issues.

[Sigma88]

I notice that nobody mentioned this specifically, so I'm going to point it out so you are aware of it.

SigmaDimensions is released under All Rights Reserved, which means you can't redistribute the mod without my permission.

And I rather my mods aren't redistributed since in the past this caused me all sorts of issues.

 

what you are supposed to do is use MM patches to edit the settings (or apply planet specific changes directly as described in my forum thread) and then tell people to install SigmaDimensions alongside your mod, as a requirement.

if you need help with the syntax and stuff feel free to ask me via PM or in the SD thread.

[Streetwind]

That's kind of what I meant with "honor all the terms of all the licenses", yeah. Honoring a license that denies redistribution rights can only lead to not distributing that mod.