Yes, the jump should be smaller though. AnimationState only keeps the previous and current animation. To do what you want it would need to keep n number of animations. Eg if during the mix of A->B you set C, it would need to keep the state for A, B, and C. If during that mix you set D, you'd need to keep the state of A, B, C, and D. Currently it only keeps the state for A or B (whichever the A->B mix that is being interrupted was closest to) and C. This isn't perfect but mixes are usually pretty short. The complexity of handling any number of previous animations is a lot higher. You could write something to do this, probably based on AnimationState.