It was actually the result of another bug fix (not the Eldar Exarch bug, if that's the one you're thinking of). Briefly, there was a problem with how the functions were being called in our C++ code, that I fixed in v3.2. Unfortunately this exposed another bug, because I had to change the order they were called in, so I fixed that - which exposed this totally different bug. Each bug was more subtle than the last, so none of it was noticeable except under extremely specific circumstances that I didn't run into in the testing that I did.
