- After several months behind closed doors, the latest source code has been uploaded to Launchpad. See important notes below.
- Bugfixing is progressing well, with little left to do before the launch.
- The first player model is also progressing well. Screenshots of that should appear here soon.
- A demo map is in the works. Screenshots of that should also appear here soon.
- A new logo is being designed (this time by a professional, as opposed to me).
- The main website has been updated and now contains a page about the Intensity Engine, which includes some new info on technical features as well as licensing.
Regarding the abovementioned 'new info', the main points are
- A brand new asset management system has been developed. It's written in Python, supports nice features like dependencies, zipped assets, and mutability, and should make life much easier in general, both for those creating content and those interacting with it.
- The Intensity Engine's license is (as before) the AGPL, but with some important qualifications (primarily accepting Apache 2.0 code and not requiring copyright assignment - see the Intensity Engine page for details). We're trying out a new approach to licensing here (or at least I'm not aware of any project doing this sort of thing), and it'll be interesting to see how it goes.
Important notes about the code:
- This is alpha-stage code, so crashes etc. are to be expected - use at your own risk.
- There are no binary downloads yet, only the raw code. We'll build binaries and provide them when we launch alpha testing, but even then, rapid changes might make it impractical. So steady releases of binaries might wait for beta testing.
- If you do compile the code, note that both the client and the server require interaction with the master server (www.syntensity.com). Without an account on the master server you won't be able to do much. Contact us (contact -at- syntensity.com, or on IRC, #intensityengine on FreeNode) if you want an account, and we'll set you up.
- The current version number is 0.9, reflecting the fact that almost all of the features intended for 1.0 have been completed. The 1.0 release is expected to occur during the summer. Minor API changes are expected until then, but nothing major.