Who knew that mark 3 of the achievement system was such a mess behind the scenes. I knew mark 2 was a navigational disaster with the interface, but wow I'm surprised the backend was just as bad lol.
Believe it or not I actually called mark 2 the Charles Manson achievement system, just because it was that criminally insane.
Rs3 code cleanup in any form is good. Makes it easier to do things.
To clarify, it isn't that it was previously implemented poorly. At the time, we requested time from an engine developer to build an engine-cached solution. That resource wasn't available at the time, so we had to do it all in our scripting language.
Which had sufficed for several years, but inevitably as more achievements got added to the system, we'd exceed the processing constraints imposed by that language (eg operations limit per server cycle to process that volume of bespoke data) and need to replace the interim solution with a long-term solution.
This time around, engine resource was available, so we were able to build the solution we wanted to have the first time. It happens, and it has certain benefits. (Not least of which to the end user in getting features sooner.)