Re: blood frenzy buff bug, it was fixed, and verified as fixed prior to the release which is why it’s mentioned in the patch notes. I don’t know why the fix didn’t work when the update was pushed live but I know the team are discussing what happened so as to improve processes in future.
Re: PvP Teams resetting, it is in our top 5 to get fixed but obviously that didn’t happen for 8.2, not due to a lack of wanting to get it done though, it is a priority for everyone.
Insight into game dev process for anyone interested
Usually if a bug that is a priority to the community or is a critical game issue in general even before you factor in how the community are feeling about it, if those bugs are not fixed asap there are usually extenuating factors. It’s not a simple case of ignoring concerns, we share the same concern over the game as everyone.
Some of these include things like:
-
Client fix vs server fix: It is often (not always) quick and easy to fix something on the server as we manage the game servers. If it is a client fix, it involves a full dev cycle with testing not only done on our side but also by every store the game is available on, so it takes more time.
-
Time was spent investigating an issue but the cause wasn’t found - at this point either we run out of time for the current release or it is blocking other fixes from being done (ie. something can be no.1 priority but if it means items 2, 3 and 4 won’t be done if more time is spent on it you start having to weigh up pros vs cons of trying to fix the one thing vs fixing 3 others). Basically there are 24 hours in the day and we have a number of people working on something and so we have a capacity to the amount of things that can be achieved. Some things must take priority over others - especially if something has had time spent on it already and is making little to no progress and has started impacting other high priority items on the to do list.
-
Alternatively, we thought we found the cause of the issue and fixed it AND QA were unable to reproduce the issue when testing the fix so marked the issue as resolved (and reasonably so), but it’s not that the bug was fixed, it’s that actually when tens of thousands of players are doing a specific thing it’s going to pop up vs a few human QA people. This is why we also run as many automated tests as we reasonably can - as these tests can run hundreds of thousans - a million instances so you would expect the automated tests to pick this up - however, creating automated testing requires time - time not spent fixing bugs or working on updates - so this has to be balanced and done in a reasonable way - not everything can be tested 1 million times.
-
The issue is a lot more complicated than it first appears - maybe the bug requires a major tech update/overhaul to get this working the way we’d all like or as intended and this tech requirement has popped up after the fact.
We’re here to make games, we’re not out here trying to be … erm trolls. There’s usually a pretty logical reason something hasn’t been done yet that has nothing to do with how we feel personally about a thing or about the community. If we could do it simply and quickly, it would be done. It’s very easy for things to appear black and white when you’re focusing on one or 2 things and not the entire picture. I’m not asking you to give us the benefit of the doubt, or making excuses I’m just shedding light on game development things and you can do what you want with it 