Outline

Not everything is documented in Orxonox. This is bad, since we have a a lot of changes with the developers and undocumented code is shit to read. Just try it once and you will never want to do it to anybody.

Starting point

We have a nice [doxygen Doxygen-Plugin] in our Trac. There you can check out what is already documented and what needs to be better.

How to start

While working you should document your code and find parts of code which are poorly documented. While working with that other code, why not improve its documentation.

Goal

Have well documented code at the end of the semester.

Task

This task will be about testing all the code we've implemented in the last term, but couldn't use anymore. We will try to establish a client - server connection and transfer everything from the server to the client (client will see exactly, what the server does).

Task

Extend Orxonox to support multiple players and implement transmission of the input from clients to the server and synchronization between server and client.

Difficulties

The connection from network part and input system, hud, etc. has to be developed. At the moment we don't have a clean input system, so this will also depend on other tasks.