The problem I just encountered is that I have to tell the players who
are currently skirmishing that they have a game. This means either:
 1. Telling the skirmish server to move them
 2. Keeping a connection with players
 3. Running the skirmish server on the matchmaker!
Three sounds nice because the matchmaker is sitting on this godot
instance, it might as well do something with it, right? But it's
essentially equivalent to 1, it just doesn't have to think about
networking because they're the same instance. So moving from 3 to 1 if I
realize it's a bad idea is easy, but 2 becomes pretty entrenched.

You're making some pretty big decisions here, take it slow.

Also allows subsequent connections, but it's broken. Don't tell the git
gods that this commit is a lie

This will make testing MUCH better, I do believe.

Also, levels now inherit a level object

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

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

That is, even if there are less than MAX_PLAYERS

Previously, everyone thought everyone was master, and it resulted in you
controlling each player. Now you are only the master of /your/ player,
so multiplayer works as expected.

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.