We’re excited to announce that we will be moving our ClientLib project to an LGPL license in the next couple days. For those of you that don’t care about the differences in Open Source licensing (and if you’re not a developer, you probably don’t), you can be confident this is a good thing. If you don’t want to take our word for it, I suggest you go read up on the differences, come back, and keep reading.
What is our “ClientLib” project? Glad you asked. Long story short, it’s all the dat content extraction and reverse engineered client code. Notably, this includes our physics code. It contains a lot of the basic functionality you would want to write meaningful AC websites and perhaps Decal plugins.
What this means for the community is that anybody that uses our ClientLib won’t be required to publish source code as long as no modifications are made to it. So if someone wanted to write decal plugins that pulled data out of the dat files (like, oh, a content editor), they could use our ClientLib. If somebody wanted to write a website and use our ClientLib to help them render stuff with WebGL or ThreeJS, they could use our ClientLib. If people started making mods to our ClientLib, though, they would still be subject to the same restrictions as they would under GPL. In this regard, the licensing is comparable. However, under GPL as it is today, the ClientLib carries with it all the viral aspects of GPL – merely using it or referencing it means your project now carries the GPL license whether you like it or not.
Disclaimer: none of us are lawyers. Our assertions of licensing implications do not constitute any promise or warranty of any sort.