Yeah for sure. State Machines can get a bit complicated at first when you are setting them up, but it can help immensely when handling multiple different actions. So, one way is to create a node structure with Nodes. The first would be the StateController this would handle transitioning to different states and handling all that. You would then have Unique states as children of this node. Idle, on_ground (I don’t understand difference between this and idle), run, jump, fall, hit, dead, attack. Within each of these states you would handle the logic for that action. You could easily add a variable has_sword, which would let each action know which animation to play. You would also have variable in your StateController previous_state, this woild then be used by each state to know if it is a chained action, thus if there is a unique action to play. For attack if previous_state == ground: do ground attacks. For jump if previous_state == run: play run_jump animation. So each state would handle all of the checks for which animation/action to do. Maybe tonight if I have time I can mock up a basic state machine as an example. You could create a state for ladder, or you could just depending on what you need create a var on_ladder then in your move and idle states control ladder interaction. It really is more of a structure design issue.