Everyone noticed it because it’s the only fix for the problem— the issue the community has with this ‘fix’ is that it’s a manually applied attribute you have to search the dev forum to learn about instead of keeping an exposed bool flag on workspace.
It’s not a big ask to just expose LegacyAnimationBlending so it’s more accessible if they’re not going to rip the functionality away entirely. I, probably like many others, have no intention to learn the new system as it does not make sense to me why I would strictly rely on priorities when the legacy blending is more intuitive.
The ability to have the old animation logic as a workspace property would still be highly appreciated, even if it’s just copying the logic of the legacy animation attribute.