MiniaczQ 6d0b7504a2 Add more granular system sets for state transition schedule ordering (#13763) ... # Objective Fixes #13711 ## Solution Introduce smaller, generic system sets for each schedule variant, which are ordered against other generic variants: - `ExitSchedules<S>` - For `OnExit` schedules, runs from leaf states to root states. - `TransitionSchedules<S>` - For `OnTransition` schedules, runs in arbitrary order. - `EnterSchedules<S>` - For `OnEnter` schedules, runs from root states to leaf states. Also unified `ApplyStateTransition<S>` schedule which works in basically the same way, just for internals. ## Testing - One test that tests schedule execution order --------- Co-authored-by: Lee-Orr <lee-orr@users.noreply.github.com>		2024-06-10 13:13:58 +00:00
..
computed_states.rs	Move utilities from examples to bevy_state and add concept of state-scoped entities (#13649)	2024-06-04 11:44:34 +00:00
custom_transitions.rs	Add more granular system sets for state transition schedule ordering (#13763)	2024-06-10 13:13:58 +00:00
states.rs	Generalize StateTransitionEvent<S> to allow identity transitions (#13579)	2024-06-04 14:23:24 +00:00
sub_states.rs	Move utilities from examples to bevy_state and add concept of state-scoped entities (#13649)	2024-06-04 11:44:34 +00:00