I've just added a section at the end of the design docs on committing code,
so you should read that before committing anything. Up untill now it's just
been me committing code so all that wasn't necesarry, but it seems like a
good proceedure with multiple people writing code.
We also should really come up with some coding standards, which I really
should have done before now, but haven't.
I also need to put all that stuff about team sizes, ranking, game setup, etc
that we discussed before in the design docs, but if anyone beats me to it,
that'd be cool too.
Um, ok yea last thing is, we really need the physics plugin in CS finished
before developement on gameplay stuff in Balder can continue. Anyone who's
been monitoring the CS main mailing list will have noticed that this should
be done fairly soon *if* someone fixes collision detection so that it gives
the right kind of information to ODE (the physics plugin). So if anyone has
the skills, that would be something worth doing. Here's what Anders (the guy
working on the physics plugin) says about it:
"Basically, what I need is a collision system which based on
collider meshes (with movement) returns one of the following upon
- How far one mesh has penetrated into the other one
- Exactly how far the time can be "stepped" until the collision
occurs. (The "exact" time of the impact.) The latter would be better,
since this gives a bit more accurate simulation.
With that, finishing the plugin shouldn't be much problem for me."
Course there might be ppl already on this, hard to tell.