I love git bisect! The problem was due to me accidentally deleting a
crucial condition `is_network_master` when checking for hero_switch
input.

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

This will make testing MUCH better, I do believe.

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.

Hero 0: Remove cursor, allow wallriding (enable collision detection)

Hero 2: Move RepelHUD to center, ignore self with Area (gravity)

Accidentally put it in the wrong place before

Within radius 8, attracts heroes with gravity.

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.

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