This reverts commit f41676c672.

I misunderstood the way the camera projections work, and I'm better off
using the original raycasting strategy.

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

And Camera.project_ray_normal. This is much better

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.

I didn't know you can do this. It's really, really nice! I can change
properties, hide, and add, to the player scene.

https://github.com/godotengine/godot/issues/3352

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

Changing the weight of the objective fixes the weird destroy-the-player
physics.

Also, count how long the objective has been tilted to the right or left,
and put counters there. Slow the game down and display who won when the
count exceeds 100% on either side. Like in overwatch, but with tilting.

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.

The camera setting got changed to default-enabled, when it should be
default-disabled.

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

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.