Hero 1 fails, probably 0 too haven't checked though. Hero 2 is fine.
Haven't tested 3.

Also, levels now inherit a level object

Hero 0 speeds up especially quickly!

Currently it just switches up by one hero.

To change, I had to change the set_status rpc protocol to include
rotation (that way switching heroes isn't jarring); so they're combined
here.

Also add variation in spawn point, so that all spawns are not on top of
each other

At this point I've pretty much deleted all of Calinou's code. Oh well,
it DID get me started.

In multiplayer, if there is only one hero 1, it is ok, but with more
than one, one hero 1 cannot place walls.

This reverts commit 22cf954991.

While on wall, if you press jump, you leap up and away from the wall

If you do so immediately after leaving the wall (<tolerance=.150s), it
still works

Unfortunately, apply_impulse seems to have no effect right now. More
research is needed.

There however were some bugs that came with this, so I'm switching to
master to explore this.

This gives greater flexibility and stops some of those especially
annoying bugs

This helps make sure that missed packets don't cause jitter or waste CPU

This is the real initial commit with all the code I have until now.

Networking: A server and 2 clients connect and then control their
players. This is still buggy. For example, every client controls the
/same/ player.

FPS controls: WSAD, Jump, and Look with mouse are all implemented (Taken
from Caliou's demo). This includes collisions.