Activities usually don't do much more than cleanup on their last, 'null' tick. That, combined with queued activities normally only starting to tick on the next tick, would lead to visible 1-tick 'gaps' between movement activities. Non-movement activities would suffer from the same problem, only with different (presumably less noticable) symptoms. Now we start ticking any activity that was queued from OnBecomingIdle immediately, to avoid that issue.
13 KiB
13 KiB