in times like these, an egregiously large percentage of keyboard warriors gather round the forums with their flaming pitchworks, here around the ZOS virtual headquarters, all chanting the same battle hymn:
"put EVERY SINGLE man, woman, and child to work, and FIX THE BUGS!!!"
the kindest of them might realize that poor timmy, the 16 year old intern janitor, probably doesn't have the necessary skillset to contribute anything of use to the desperately needed fixes.
the smartest of them might realize that deborah from marketing isn't whipping the coders' backs raw so that they optimize every line of code that has to do with monetization.
and yet an even smaller percentage have the sensibility to realize that in practice, even if jonathan the senior coder could theoretically shove his hands in the server code spaghetti, there's already thomas and his team of veterans simultaneously playing jenga with the code in perfect synchrony. sure, they may be the same people who always have been responsible for that particular moving part of the dauntingly massive machine that is ESO, and the same people who oopsie'd the bugs into existence in the first place- but by god, would their entire jenga tower collapse were they to have to indoctrinate new team members into the way they wrangle the code; to teach them the mystic arts of "if(goingToCrashToDesktop) { dont(); }".
in reality, this is more or less how it works:
game developers have teams assigned to different aspects of the game. each team is a cohesive unit of people working together in a way in which their individual work can be brought together coherently and functionally. assigning one team's duties to another team will NOT speed up the process, because it isn't a straightforward additive equation of "the more people work on it the faster it gets done", it isn't working a field. it's working with a very complex system in which every single person has their own part to play, and multiple people will just get in each other's way.
they can, and do prioritize working on urgently needed fixes which are essential to the game working. they're working with all reasonable able-bodied, relevantly-skilled men, women, and others.
if those fixes aren't ready day 2, they haven't figured it out yet. just because the content pipeline does not come to a standstill when there are critical bugs does not mean they aren't using every single employee whose job is to address those bugs, to address those bugs. they don't pull their coders aside and tell them "hey, i know we're supposed to fix weaving, but we wanna make a new class for the next expansion, you should work on that today instead".
and those people working on fixing the bugs? they're not going to work faster if you metaphorically whip them. nothing will make them work faster except maybe coffee.
TL;DR:
you can't "divert manpower".
so let's all calm down and go shout at a PUG or something.
y'all need to stop acting with the same mental incompetence as a PUG's combat incompetence.
-
obligatory disclaimer:
this is not about "defending" zos. this is about instilling critical thinking, logic, and reasoning, in the place of frustrated "demands". this is about providing a more reasonable explanation for all this mess. for the sake of knowledge.
the current state of the game, or ZOS' buggy day one releases in general, are disrespectful towards their paying customers. they are beneath the quality they should provide. ZOS' developer teams, regardless of their appointed responsibilites, should fulfill those responsibilites better.
given the success of the game, they should have some of the best people in the industry.
maybe they do, maybe they don't- what's clear is that they mess up a lot more than is acceptable to do by their playerbase.
that doesn't mean they're not prioritizing properly. it just means they're bad at their job.
...or the game really is a hellish nightmare to code properly idk i'm not a dev.
fastolfv_ESO wrote: »the mail bug where mail isnt delivered until you zone was reported when beta was capped at lvl 25, 7 years and running zos knows and will not fix anything
fastolfv_ESO wrote: »the mail bug where mail isnt delivered until you zone was reported when beta was capped at lvl 25, 7 years and running zos knows and will not fix anything
I've often said to people imagine if you arrived in work one day and your boss told you all the staff in a totally different department were going to stop doing their work and do yours instead, you just need to show them what to do. How do you imagine that would go?
And in such a big game, where bugs are everywhere, every patch, it ain't one day. It is a policy of not having enough hands on deck to begin with. It is not about "all hands on deck fix bugs now." It is about "we don't have enough people in this department to fix all the bugs that were reported in the PTS again and again and again.
Unfortunately the trend for monetization (items/dlc packs/eso+) has truly become their point of focus and it's pretty obvious these days for a large amount of the player base. From what I've seen in some other game's reviews on the net (from Bethesda), it is also the same trend...Elder Scrolls Blades...Fallout Shelter...to name some I've seen in reviews. They invested heavily in monetization software a couple of years ago and we are paying the price I can only imagine or it was a way to make the company more attractive for sale purposes. (tin foil hat on).
I've been an ESO+ subscriber since it came out, but what you can see from my more recent posts is that I won't be subscribing again in future and one must say ESO is pretty much unplayable after a certain amount of hours played without the 'advantages' of ESO+. This all leaves us with a bitter taste for future game releases. TRUST is still the biggest seller in what ever product you sell these days and the trust well has run dry.
in times like these, an egregiously large percentage of keyboard warriors gather round the forums with their flaming pitchworks, here around the ZOS virtual headquarters, all chanting the same battle hymn:
"put EVERY SINGLE man, woman, and child to work, and FIX THE BUGS!!!"
the kindest of them might realize that poor timmy, the 16 year old intern janitor, probably doesn't have the necessary skillset to contribute anything of use to the desperately needed fixes.
the smartest of them might realize that deborah from marketing isn't whipping the coders' backs raw so that they optimize every line of code that has to do with monetization.
and yet an even smaller percentage have the sensibility to realize that in practice, even if jonathan the senior coder could theoretically shove his hands in the server code spaghetti, there's already thomas and his team of veterans simultaneously playing jenga with the code in perfect synchrony. sure, they may be the same people who always have been responsible for that particular moving part of the dauntingly massive machine that is ESO, and the same people who oopsie'd the bugs into existence in the first place- but by god, would their entire jenga tower collapse were they to have to indoctrinate new team members into the way they wrangle the code; to teach them the mystic arts of "if(goingToCrashToDesktop) { dont(); }".
in reality, this is more or less how it works:
game developers have teams assigned to different aspects of the game. each team is a cohesive unit of people working together in a way in which their individual work can be brought together coherently and functionally. assigning one team's duties to another team will NOT speed up the process, because it isn't a straightforward additive equation of "the more people work on it the faster it gets done", it isn't working a field. it's working with a very complex system in which every single person has their own part to play, and multiple people will just get in each other's way.
they can, and do prioritize working on urgently needed fixes which are essential to the game working. they're working with all reasonable able-bodied, relevantly-skilled men, women, and others.
if those fixes aren't ready day 2, they haven't figured it out yet. just because the content pipeline does not come to a standstill when there are critical bugs does not mean they aren't using every single employee whose job is to address those bugs, to address those bugs. they don't pull their coders aside and tell them "hey, i know we're supposed to fix weaving, but we wanna make a new class for the next expansion, you should work on that today instead".
and those people working on fixing the bugs? they're not going to work faster if you metaphorically whip them. nothing will make them work faster except maybe coffee.
TL;DR:
you can't "divert manpower".
so let's all calm down and go shout at a PUG or something.
y'all need to stop acting with the same mental incompetence as a PUG's combat incompetence.
-
obligatory disclaimer:
this is not about "defending" zos. this is about instilling critical thinking, logic, and reasoning, in the place of frustrated "demands". this is about providing a more reasonable explanation for all this mess. for the sake of knowledge.
the current state of the game, or ZOS' buggy day one releases in general, are disrespectful towards their paying customers. they are beneath the quality they should provide. ZOS' developer teams, regardless of their appointed responsibilites, should fulfill those responsibilites better.
given the success of the game, they should have some of the best people in the industry.
maybe they do, maybe they don't- what's clear is that they mess up a lot more than is acceptable to do by their playerbase.
that doesn't mean they're not prioritizing properly. it just means they're bad at their job.
...or the game really is a hellish nightmare to code properly idk i'm not a dev.
I sent in repair tickets during the earlier portion of this latest dlc's pts phase, directly from the pts server, indicating the presence of a number of issues i found. Guess how many of those issues went live? They had the knowledge, and they had the ability to fix the issues before they went live. Someone, somewhere, opted to ignore the data and push this dumpster fire through.
This company has behaved irresponsibly, yet again, and there is nothing you can say that can defend them. It's gross negligence and someone(s) should be ashamed of their lack of oversight.
AgaTheGreat wrote: »[snip]
They won't be able to fix it.
[Picture removed for Censor Bypass]
EvilAutoTech wrote: »Y'all know who fixed most of the bugs in Morrowind?
The community.
Y'all know who fixed most of the bugs in Oblivion?
The community.
Y'all know who fixed most of the bugs in Skyrim?
The community.
Y'all know who doesn't have access to fixing bugs in ESO?
We are witnessing more tolerance than many of us are comfortable with.
That doesn't make the producers negligent, and clearly not ashamed.
Keep thinking happy thoughts.