
Originally Posted by
Matt_LOTB
So, first off, I want to assure you that event bugs are really frustrating for us too.
There are a whole host of causes that underly some of the bugs that you're referring to. Some of them have had to do with process. Some of them have had to do with data and variable configuration. Some of them have had to do with our toolset. Some of them have had to do with our QA bandwidth. Some of them have had to do with how our various game environments (QA, Dev, Production) are set up, and truthfully, some of them are human error.
Along with all these various causes come a bunch of possible solutions, some of which are more feasible than others.
For instance, rebuilding our entire environment structure, or replacing our variable delivery service are significant undertakings that would potentially offline a lot of core development work while we were to undertake them.
However, concrete steps we have taken include:
- improved tooling: in recent weeks we have completed development on a number of key QA tools that will substantially increase our QA team's capacity to locate and identify issues with event data and assets. Not only does this have the benefit of making our event testing more robust, it also takes significantly less time, so QA is able to focus more of their effort on other aspects of the game.
- Double-check process: we have additionally implemented a recurring double-check process supplementary to our QA sign-off to catch and correct any human error or configuration problems long before the events go live. This should help to prevent a lot of that early jank you refer to, wherein the event behaves differently for the first couple hours than it does for the rest of the event.
One of the big takeaways I want to assert here is that our QA team are incredibly diligent and hard working. They do their absolute best to ensure that bugs are found and everything in the game is as it should be. They do so with a small team, enormous scope, limited resources, and smiles on their faces. We continue to try to build out the tools and resources they need to make their jobs more manageable, but the QA team deserves a huge amount of credit and thanks for the work they've done and continue to do.