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)

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

Accidentally put it in the wrong place before

Within radius 8, attracts heroes with gravity.

When it's too short, the scrollbar makes it completely illegible

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.

This prevents hero 1 from permanently setting the objective to one side,
making them very OP and the game un-fun.

Any object with collision mask=2 will no longer collide with the
objective.

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