Plan for Serverside Implementation

I've started doing a bit of work on the server-side implementation, however, Uni and a lack of knowledge about Lua implementation has been hindering my progress somewhat, so i've decided on a bit of a middleground-


Until i manage to gain a working knowledge of Lua, i'm going to write the main engine somewhat more rigidly for our first version (internally-defined behaviours for more of the weapons and objects, for instance), and then once i get more adept at lua implementation, i'll detach the relevent objects and expose the required areas of the code to lua.


Since i'm programming the core engine as a DLL, this isn't too big a deal, as I can just recompile the DLL with lua support and plug it in with minimal impact on other server-side components. I'll just need to sit down simetime this week and work out exactly what objects and structures need to exist for our first version (As it is, the project just has a bunch of header files of things i know will be needed and a small bit of code for the 'physobj' object). Once i've got a general engine layout, I can start actually cranking somehting out


Also, we will need to work out who is going to be programming the networking. I know that once i've gotten the engine layout done i'll have a list of all the message types that need to be sent back and forth for updating, but we need to work out the actual structure for our networking stack.


Finally, kudos go to Madmock for re-writing my vector library with SSE.

I'll be uploading some images of the interface design I had in mind once i work out exactly how to prod blogger into doing my bidding