One of the biggest things I’m working on right now is cleaning up, documenting and reworking the heart of World Machine’s codebase. I have three aims in this:
- Make it easier to maintain and debug for myself and anyone else (such as plugin authors) who needs to interact with the core
- Pave the way for some new features that need some core changes to be enabled (this includes using native real-world units, allowing for having localspaces and different resolutions in the same world file)
- Make embedding World Machine into games, simulations, etc much easier. Over the years, a number of game companies and others have licensed World Machine to use internally in their game or tools. Especially with some design changes to make this more streamlined and simple, I see this as a great growth area for both the Big Guys and licensing to indie developers, as you can develop your maps in the World Machine editor and then regenerate at needed resolution on remote machines, without sending many MB of map data. This is, in fact, the original purpose that WM was developed for back in the day!
I’ll write more on all of these things, but I figured it would be useful to know what’s going on right now!