This release contains most the stuff that came in during GCI 2017 and then some. Immediately after this we're beginning to merge things into the engine for v2.0.0 that areguaranteed to be backwards compatible: our first new major release (for about two years?) since we adopted SemVer . That includes the two large GSOC 2017 projects Sectors and the Behavior Tree overhaul , along with some smaller but breaking changes that needed a major release.For all the details on Alpha 9 see the Release page on GitHub There is also a GitHub project board covering "known issues" and other recent or otherwise relevant seeming things as of the Alpha 9 release . Been trying to confirm and get updates on some of those.: As the engine (and embedded modules) get incremented to v2.0.0 things that previously depended on v1.x.y. This is because some places only consider the very latest available dependency from Artifactory, and v2.0.0 will be too "new" to be acceptable. I'll be bulk-submitting a pile of dependency tweaks to module.txts all over the place soon, so many workspaces will need updates. It may not even be something sticking to the engine master branch will keep you safe from (it's Alpha and we need to finish some more release management and related automation!)To better do that I've created a fresh new module mega-workspace with a grand 137 added modules and did so using a neat new way to do so thanks to the work on the new Groovy-based utility scripts (with more coming!). Simply copy paste the values from the Omega distro prop file and bulk replace the commas with single spaces. Then paste that after "groovyw module get" and hit enter! Maybe we can add another utility command for that.Note that the Groovy utility is still "incubating" so to say and may change in a major way, bugs are also likely. It would be nice with a few more people keeping mega-workspaces for testing engine PRs (to see if modules are impacted) until the build system goes supercharged. I suggest keeping it separate and purely for testing/merging PRs. And to look up the "update-all" utility commandIn the near future I may also try to submit the next stage of the Gradle overhaul plus we may tweak library dependencies and all sorts of things while we're outside of the API freeze so to say. For the next 2-3 months I expect we'll be stabilizing the develop branch and firming up the v2 API. Many things will break and then they'll be fixed! It will be glorious, but prepare to update workspaces a bit more than usualKeep track of the v2.0.0 milestone on GitHub and probably a project board or twoIn other random news Mike K found us in a book ! It is kinda old and mainly about Minecraft, but hey, cool