Can you also pass along that while well intentioned, this thing is actually a total disaster as it is? It accesses arbitrary uobjects and calls arbitrary ufunctions from the anim worker thread in parallel with no safety checks whatsoever. Most game code is NOT thread safe. No one expects it to have to be. No one expects to have to worry about multi threading race conditions when working on an animation blueprint in the editor.
We’ve wasted whole days trying to determine why our animations were subtly wrong and completely exploding in some edge cases, and it was just because of that. This is going to create the most cursed bugs people have ever encountered, if it isn’t changed to collect the values on the game thread and cache them.