**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options
Just a thank you
This discussion has been closed.
Comments
For a game that's 4 years old, that gets regular montly updates, and probably only has a testing cycle that lasts about a month, I'd give Kabam devs more credit for being able to sustain what they're doing without the whole thing imploding into itself. The reason that I personally believe some people are acting entitled, is because they expect devs to be working every single day and fixing everyones individual issues as if it were top priority.
I'll give you a rundown of how a bug, when submitted, goes through proper processing for most gaming companies, as I used to be a former Functionality Quality Assurance (QA) tester for several LARGE publishers and developers.
Step 1: The bug is found, whether it be from a Tester, or the Community forums.
Step 2: If the bug is community found, the bug is passed onto the QA Lead, who will assign a member of the QA team to attempt to reproduce the said bug.
Step 3: The QA Tester will then load the specific build, on a similar or exact device, and begin testing how to trigger the said bug. The tester will then do this between 5 - 10 times to get a reproduction rate.
Step 4: The Tester will then usually be asked to do this again on several different devices, with different OS, to see if this is a universal or a device/os specific issue.
Step 5: The Tester will then have to write a bug report into a bug database, such as Jira or DevSuite. They note the build, the device, the OS, the reproduction rate, the steps to reproduce, the type of bug (visual/mechanical/functionality), the area of the game effected, and the bug severity. Bug severity usually comes in 4 classifications. (A) being the worst, in which is inhibits game progress, whether that's a hardlock of the game that requires a device to be completely restarted, a freeze which prevents the user from putting in any input or returning to a menu, a crash etc. (B) being severe, while it effects gameplay, it does not stop the game from being played, but it does require more urgent investigation from the Dev team, this can be in the form of 6.1 issue, where rewards are not being handed out properly, it effects the user experience to a larger degree. (C) is a minor bug, an audio issue, a visual glitch, a text issue. Something that won't directly impact the user experience and will mostly go unnoticed, but still needs fixing. (D) are extremely minor issues, usually only used for potential suggestions, these are the lowest possible priority and will rarely ever see a fix.
Step 6: After the Tester submits the bug report, it will then be looked over by the QA Lead. Once they are satisfied that enough information is there, and that it is easy to understand what the issue is and how to reproduce it, they will pass it onto the Dev team.
Step 7: The Dev team will look at the issue, and begin to test the issue and find out what they can do to fix it, depending on the severity of the bug it can take a few days for a proper fix to be made. Once they've found and fixed the issue, they will send an updated build back to the QA team.
Step 8: The Tester who sent the bug report will usually be the one to test the new fix. Again this Tester will go through and do all the same things they did before, testing on different devices on different OS, to make sure that the bug has been fixed. They will then close the bug if it has been fixed, or update the report if it hasn't.
Step 9: Once the bug has been fixed, it will then eventually be pushed out to the users.
As you can see, the process is a lot longer than you would think, now add in the fact that there are literally dozens of issues, some are known as blanket bugs which are all similar, that all need fixing. The other problem is, that once a game is released as a full release, and not a Beta, the company that publishes the game have to pay for every update that they release (this is why it's very common for games on Steam to stay as a Beta because they can push out as many updates as they please without having to pay this fee), and these updates are not cheap to put out on any platform, especially Google Play and the Apple App Store.
By the way, this isn't a post trying to attack anyone here. I just want people to understand that the process of game development is a long one, and that while issues are annoying (I'm looking at you Razer Phone FPS issues.....), there's nothing you can do but wait. Creating 10s of topics all about the same thing doesn't get issues resolved faster. Trust me when I say, they are doing all the can to fix these problems, at the end of the day this is their livelihood, and while we may not see what they are doing all the time, they have our best interests at heart, as it directly impacts their own interests too.
I hope that this helps some people appreciate all the work and effort that truly goes into this.