Open
Description
The action manager and scheduler are very closely related classes and there is some very similar code shared between the two (or at least there was). It probably makes sense to just merge the two into the same entity. This would simplify a lot of code.
The other thing to consider is that we need to make actions work well with fixed updates and physics. Combining the scheduler and action manager will make this easier to do effectively since the fixed update and all information about it is encapsulated by the scheduler. I definitely feel like it would be easier to achieve better action/physics integration if the scheduler and action manager were combined.