Updates to the website

This morning we updated the website with a number of new features and bug fixes. Here are the release notes.

  • “Flags” enums that were previously complex numbers or ugly sets of checkboxes are now much more user-friendly. Simply pick the options you want from the list. Here’s a sample:
  • The Spells drop-down is now searchable. No more scrolling FOREVER to find the spell you want.
  • Loading certain creature weenies that were missing base attribute scores no longer crashes. Instead, they will default to 10s for any missing stats.
  • Content Magi attempting to approve changes to “new” weenies now works.
  • Emotes are now sorted appropriately on every page refresh.
  • New Emotes are now added to the end of the current list. You can re-sort by changing the sort order
  • The Weenie Finder is now used in a few more places allowing for easier searching

We’d also like to give Forge Golem a warm welcome to the team. He’ll really get started in a week or so, but we’re excited to bring him on board as a dedicated website resource. As always, if you find bugs or usability issues that aren’t on the trello board, let a staff member know and we’ll get it logged.

Thank you for all your support!

Moving ClientLib to LGPL

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.