Player Namespace Reference

Namespaces
namespace	Generated

Classes
class	InputReader
	Uses the New Input 'Controls'(name you choose) which causes dot net generation of controls for the scenes OnMovement is generated to connect to the Movement action(in unity) Input Actions object The Controls.IPlayerActions is then an interface that this class implments and will be called when the action takes place. More...
class	OnScreenPlayerUpdate
	Player records input states and player action stage for update in PlayerMovement. More...
class	PlayerInputState
class	UpdatePlayerForces
	Moves the player by adding force in the required direction TODO: Remove the projection system in favour of a subscription model so if available it will react correctly The _mainCamera is needed to help direct the movement so its not confusing to the player, as it swings around to focus on the next waypoint. TODO: When we get to more than IOS, mobileMultiplier will need extending for other devices during test probably. More...

Detailed Description

How Enimies input and movement work

The unity object is attached to the player and that is what the 'player' will move via some input controls This sets up the input controls (using the new input system in unity) and actions taken As appropriate inputs are processed and then the Actions class is used to broadcast changes to interested consumers Currently just the player object but could easily be an intelligent enemy as another consumer of change