Weapon Alpha

[TheShyGuy]

Determining the absolute character state every frame is tough to manage, debug, and easily allows for bugs. Why even determine the state of the character every frame? If you begin to climb a ladder, why determine that you're doing that again every frame? Instead, I prefer tracking the current state, for example "idle", "jumpRise", "jumpFall", "walking", "running", "climbingLadder", etc. This also allows state changes and code to be relative or local to the current state instead of the character's absolute state. I believe people call this a state machine, which you can look up for more info.