This looks awesome, if I wasn't already at the 4GB limit, I'd try it out now. However, as a fellow developer (and, full disclosure, open-source advocate), I'd like to offer some unsolicited advice on your license. It's really not a good idea to have a license like that -- it leaves open a lot of legal ambiguity, and someone could exploit that and do things you clearly don't want to do. If I can make a recommendation, if your code is to be free and open source (which I interpret from the 'used by all') bit, but you don't want commercial binary re-distribution, then I would recommend simply saying, "This code, except where noted, is free for non-profit, non-commercial, must-attribute use." This is a lot simpler and more clear. You could also use a Creative Commons BY-NC license, though these aren't often used for code, it's not inappropriate to use them, and they're relatively customizable, see: http://creativecommons.org/choose/ Finally, as a Free-culture, open source advocate, I have to say; do consider *allowing* for 'commercial' use, one of the pillars of the FOSS movement is that it doesn't restrict commercial use. This helps keep FOSS commercially valuable, and though a KSP plugin isn't likely to make-or-break the FOSS movement, it's important to remember that people who use your software to make money aren't necessarily out to exploit, often they recontribute and make everything better. If you'd like to make explicit restrictions, that's okay too, you can say, "This Code is licensed under the MIT License, except where noted in the source, and so long as it is not redistributed on pay-to-download sites similar to ad.fly, such similar sites are determined at the discretion of the author or those he empowers to make those decisions." This covers all your requirements, but also puts you on a much more solid footing in terms of clarity of licensure. It's not likely to ever be a big problem, but it's good to get this stuff right, so in the off chance it could, it won't come and bite you in the butt. NB. I originally posted this on hounddogger's blog of this post, so there's a second copy of it running around.
