If the fix is already developed and tested, why can't this be a quick fix? Is it too rooted into the other untested implications in the engine update so it can't be a standalone update?
I tried replying to this before you reposted, glad you did!
It's a good spot, and bad wording on my part rush typing this. Engine Updates in general are a lot more complex with a lot of testing / lead time - especially given we have to consider Mobile platform submissions.
Generally we target batch releasing Engine Updates to avoid knock on effects to our other Engine deployment timelines or creating bigger issues by rush testing. Even without rushing, this slipped through the net on our last one which shows the unintended impact any Engine Update can introduce when you have a game with 23 years of content to account for.
This fix itself has been prioritized for that next batch for April, but there isn't an intention to push it live as a standalone update earlier - at least right now - given we've been able to find a hotfix route.
EDIT: Worth mentioning the team are also looking into how this was missed and considering solutions for how we better cat...
Read more