Hi!
I just stumbled around the same issue, would be great to see if there's anything being done on it? Or a set of 'best practices' to work around it?
Regarding the combined state, seems like a great suggestions, what's the best way to do that? Maybe a 'States Monitor' where we listen to states and set a third concurrent state with the names appended: i.e. if Crouch and Aim are happening we SetState "CrouchAim" in concurrent mode?
What would be great, if it were possible built-in, to name a state preset with a naming convention such as "Crouch Aim" (no matter the order) and it would detect it as crouch and aim.
Or another separator besides white space, maybe semicolons, ampersand or pipes (';' or '&' or '|')
But don't know the performance implications of parsing text states like this.
Thanks!