CountZero

Additionally, I'm not really all that interested in Atavisim providing a GUI/UI, really at all. I plan on building a completely custom UI, leveraging Daikon Forge. What I need is documentation for the server call back functions that my client/UI will need to implement to interact with the back-end.

While I think it's great that you guys are working on Quests and Combat etc, I fully expect to have to implement my own plugins for that sort of functionality due to the differences between how my game will work vs more traditional RPGs. I'd really like to have the documented ability to develop my own base plugins sooner rather than later. I can understand why you feel that quests and combat plugins should be done first, as most of your clients will likely be writing plugins that sit on top of what you provide and given the interaction between those core systems and pretty much anything else in a game, having those completed makes some sense. However, I'm assuming there is a more fundamental API for plugins that could be documented earlier for those of us who want go a pure custom route for game-logic code. I want Atavisim to provide the network glue, terrain and collision, object positioning, data backend, core platform type functionality, but all the 'rules' of the game, the sort of stuff that makes GURPS different from DnD, I'd like to build myself. Are there plans to provide low level documentation to support that, preferably sooner rather than later?