Quote Originally Posted by TaleraRistain View Post
I wouldn't say it's necessarily they didn't prioritize it. It's probably more complicated. Something people on the outside may not realize is that the release of bug fixes isn't entirely based on how severe they are. They probably have a couple team members working on some other bugs while other devs puzzle this one out and those were faster to get ready to go than this more complex issue.
This. The P10 bug had been known about for a little under two weeks, it's easy for them to have R&D'd the solution to it for the hotfix. Comparatively, the Caloric bug has been known about for roughly a week, in which part of the time it was only affecting the most hardcore groups that were even on P12s at all giving a small sample size, on top of the fact certain strategies for Caloric Theory 1 put the fire groups very close together, giving false positives for people that think the fire groups just clipped or something. On top of that, the solution might not be as obvious as the P10 one is (Which to be fair, the P10 one isn't necessarily a solution in itself, it's just disabling the offending actions until a more concrete solution is found). Especially for a bug that's primary factor is that it's contingent on server stress load, coupled with RNG on top of it - not exactly the most easy test conditions for consistency in replication, and also a set of conditions that can quite easily dodge internal QA.

They've already acknowledged it and are working on a solution - complaining won't speed them up, it's just a waste of your energy you can better spend doing something productive in your life.