Quote:
Originally Posted by fyreflyte
I haven't looked at that fix specifically, but much of what Aeralik does is code-based, which has the potential to affect other areas of the game (whereas fixing the stats on an item really only modifies that 1 item). Because of this, QA needs more time to run negative test cases, and we like to run the changes through the Test server as well, to be certain everything is running smoothly. So in short, if Aeralik says the fix is done, it means the code is there but it's still being tested.
Hope that addresses your concerns =)
|
I appreciate your continued feedback on issues, but this is a bullshit run-around to protect Aeralik's decision. How would a unique proc's effect affect other areas of the game?
The proc was broken because it didn't account for debuffs which was an overlook by the developer who coded it and just took the literal /weaponstats max damage values.
I can understand how this can happen but I can't understand why it wouldn't be pushed into a hotfix and waited for a GU. You can't use the "we need to run it through QA" excuse either because QA had their chance and it went into the game broken.
I honestly feel sorry for the developers sometimes, because the QA team fucking blows.
Edit: This is a flame at Aeralik not you.