4.11 MoveComponentTo rotation bug

I have managed to workaround this problem, WHAT IS STILL a really dumb step from Epic. I have created an Actor, that is able to manage some delayed actions which are stored in Objects. I was forced to do it all by myself, implement a interpolation, delayed action and fair interface. This is really annoying, that when new update comes up things get broken. ALSO Sean Flint… you know what the interpolation by shortest path is? It have ABSOLUTELY nothing to the Gimbal Lock. It was just getting rid of another problematic question. I feel bad for every user that is treated like that. Gimbal Lock? Psh! Can you explain me - how can an actor fall into gimbal lock when its rotation is 0 except Yaw? This is ridiculous. Node is broken and that is the fact, not any gimbal lock avoiding. Don’t rotate at all if you want to avoid it this way.