Break player down into components

[ac-arcana]

The player class is pretty large, and includes a lot of concerns. Perhaps player movement, player look, and damage receiver could all be separate components.

[Phazorknight]

Yup, definitely a goal of mine to chip away into improving how this is currently set up.

[ac-arcana]

Class names on player and any components that are broken off from it too, please.

[aronand]

I've had a look at the code and at least two things that could be done come to mind:

1. Separate attribute management to its own node
2. Implement a state machine to handle movement

Out of these two, the latter would definitely have a bigger impact on the code.

The first one might be more complex than initially seems. I quickly gave it a try some days ago, but recall running into issues with some level of coupling when trying to move attributes under this new node. Initially remembered it being due to attributes being coupled to the player, but that actually isn't the case now that I checked the code.