[...] I am saying that it is down to the management part, not the QA part. They could hire 300 more QA people on top of the 300+ they already have and still produce the same quality of releases.
Ragnarok0130 wrote: »They need a core combat ability bug task force to be on top of fixing it tbh.
Or maybe just a combat team who doesn’t shake up the etchasketch every patch and actually uses scalpels over sledgehammers instead of saying they will and grabbing the hammer anyways. A vision for combat would be very helpful as well - a real vision and not that non-committal marketing nonsense they gave us in their Q&A substitution post.
Ive experienced the bug where bumper skills stop working (in pvp) and also ultimate won’t fire. I’m on XBOX NA.
There are significant bugs that make the game unenjoyable to play.
Block stops working after a minute or two in PVP.
Maybe bumpers and triggers are bugged?
TechMaybeHic wrote: »Has there been an announcement for maintenance next week yet? I haven't seen a banner.
I don't even mean to be dismissive or toxic when I say that I'm concerned they might not have the resources to address issues
QA is only supposed to find bugs, management and their developer resources have to prioritize it.
There's a few things I see as a software development manager myself.
1. It sounds like testing scope is larger than their current staffing levels can accommodate. Every organization is unique, but fundamentally a product manager or technical lead need to size that effort before giving it to the testing
2. It sounds like the technical backlog is larger than their current staffing levels or skillsets can accommodate. The persistent issues with block and other core combat mechanics tells me it's probably the latter.
3. There's a fog around the scope of their major efforts like the code reworks and server replacements. We don't have a clear list of what will be fixed by what and by when.
4. The communication around the bigger technical topics is some combination of vague and infrequent. Even on minor bugs, getting updates is proving difficult. Either they are unable to convey their efforts or don't feel like they have to for whatever reason. Hard to say which, but it feels like the latter.
AvalonRanger wrote: »Not only combat system, but also ZOS spawns new "dangerous exploit possibility" each time they release
new DLC patch. I thought those were too much careless.
why are we forced to dread every patch instead of look forward to them.
QA is only supposed to find bugs, management and their developer resources have to prioritize it.
There's a few things I see as a software development manager myself.
1. It sounds like testing scope is larger than their current staffing levels can accommodate. Every organization is unique, but fundamentally a product manager or technical lead need to size that effort before giving it to the testing
2. It sounds like the technical backlog is larger than their current staffing levels or skillsets can accommodate. The persistent issues with block and other core combat mechanics tells me it's probably the latter.
3. There's a fog around the scope of their major efforts like the code reworks and server replacements. We don't have a clear list of what will be fixed by what and by when.
4. The communication around the bigger technical topics is some combination of vague and infrequent. Even on minor bugs, getting updates is proving difficult. Either they are unable to convey their efforts or don't feel like they have to for whatever reason. Hard to say which, but it feels like the latter.
As a former mid lever developer, this has been my assessment as well. I am especially dissatisfied with #3 & #4.
Well they did state in the second half of the year would not be an another dlc and would work solely on bug fixes and quality of life improvements.
I would say that that’s a step in the right direction.
They also stated that 2020 was the year of performance.
They also stated the code rewrite would be done before the end of 2022.
They also stated (word for word) that the servers weren't part of the performance issues, and that if they were they would have replaced them years ago.
They also have been stating that they're addressing server related performance concerns since as far back as 2016.
I hope that Q3 is a step in the right direction. That said, their statements are meaningless. We need actual commitment, and examples of them doing better, like rolling back hugely damaging changes such as those that came with u37.
Sadly I don't trust they are actually refactoring. The wording keeps changing when referring to this project and my trust levels concerning this are low.
why are we forced to dread every patch instead of look forward to them.
QA is only supposed to find bugs, management and their developer resources have to prioritize it.
There's a few things I see as a software development manager myself.
1. It sounds like testing scope is larger than their current staffing levels can accommodate. Every organization is unique, but fundamentally a product manager or technical lead need to size that effort before giving it to the testing
2. It sounds like the technical backlog is larger than their current staffing levels or skillsets can accommodate. The persistent issues with block and other core combat mechanics tells me it's probably the latter.
3. There's a fog around the scope of their major efforts like the code reworks and server replacements. We don't have a clear list of what will be fixed by what and by when.
4. The communication around the bigger technical topics is some combination of vague and infrequent. Even on minor bugs, getting updates is proving difficult. Either they are unable to convey their efforts or don't feel like they have to for whatever reason. Hard to say which, but it feels like the latter.
As a former mid lever developer, this has been my assessment as well. I am especially dissatisfied with #3 & #4.
Their response about code/physical improvements has been, 'Well, we've been waiting on hardware, we don't know when it will get here, so we can't say.' The languid communication however, is probably because they know that anything they say can, and will be used against them. It's hard to get called on something you didn't say. I think the Update 35 Q&A debacle had a significant effect on communication forthcomingness.
draftwhy are we forced to dread every patch instead of look forward to them.
QA is only supposed to find bugs, management and their developer resources have to prioritize it.
There's a few things I see as a software development manager myself.
1. It sounds like testing scope is larger than their current staffing levels can accommodate. Every organization is unique, but fundamentally a product manager or technical lead need to size that effort before giving it to the testing
2. It sounds like the technical backlog is larger than their current staffing levels or skillsets can accommodate. The persistent issues with block and other core combat mechanics tells me it's probably the latter.
3. There's a fog around the scope of their major efforts like the code reworks and server replacements. We don't have a clear list of what will be fixed by what and by when.
4. The communication around the bigger technical topics is some combination of vague and infrequent. Even on minor bugs, getting updates is proving difficult. Either they are unable to convey their efforts or don't feel like they have to for whatever reason. Hard to say which, but it feels like the latter.
As a former mid lever developer, this has been my assessment as well. I am especially dissatisfied with #3 & #4.
Their response about code/physical improvements has been, 'Well, we've been waiting on hardware, we don't know when it will get here, so we can't say.' The languid communication however, is probably because they know that anything they say can, and will be used against them. It's hard to get called on something you didn't say. I think the Update 35 Q&A debacle had a significant effect on communication forthcomingness.
They could have been forthcoming with the Q&A. I’m still blown away by the lack of updates on the thread for 3+ months asking when it’s coming. IMO, that was the biggest misstep in the whole slew of communication debacles last year.
While I believe that there are people who will use anything against them, I believe there are also others who get the complexities behind things and just want to know concrete details on where things are. We don’t have a list of what their major projects will actually fix. I would rather them err on the side of too much detail. The way they’ve communicated in the past hasn’t done them any favors.
Sadly I don't trust they are actually refactoring. The wording keeps changing when referring to this project and my trust levels concerning this are low.
And TBH the current block bug is hardly non-critical