If ZOS didn’t see it coming that this would happen again
If ZOS didn’t see it coming that this would happen again
didn't see what coming? you make it sound like every time zenimax have had to take the server down for any reason, it's always the exact same literal reason
networking architecture is unbelievably complex, and i can guarantee you that every day at the office revolves around an entirely new issue that the devs have never seen before, requiring them to re-invent the wheel every update, so to speak
you can't just try and simplify it to "how did you not expect server issues and prepare in advance zenizos" because they have no way of predicting every single specific issue that will inevitably arise each update
yes it sucks you can't play the game for a few hours, but it would suck a lot more if something catastrophic happened like trying to play with 9999999999 ping for hours on end or worst case scenario your character data being rolled back suddenly
If ZOS didn’t see it coming that this would happen again
didn't see what coming? you make it sound like every time zenimax have had to take the server down for any reason, it's always the exact same literal reason
networking architecture is unbelievably complex, and i can guarantee you that every day at the office revolves around an entirely new issue that the devs have never seen before, requiring them to re-invent the wheel every update, so to speak
you can't just try and simplify it to "how did you not expect server issues and prepare in advance zenizos" because they have no way of predicting every single specific issue that will inevitably arise each update
yes it sucks you can't play the game for a few hours, but it would suck a lot more if something catastrophic happened like trying to play with 9999999999 ping for hours on end or worst case scenario your character data being rolled back suddenly
Didn’t see coming that something would go wrong. Anything. Every single chapter release there is additional, unplanned, extended maintenance. Perhaps they could try incorporating that into their timelines instead of communicating unrealistic ones, giving players expectations and then, as usual, not meeting them.
If ZOS didn’t see it coming that this would happen again
didn't see what coming? you make it sound like every time zenimax have had to take the server down for any reason, it's always the exact same literal reason
networking architecture is unbelievably complex, and i can guarantee you that every day at the office revolves around an entirely new issue that the devs have never seen before, requiring them to re-invent the wheel every update, so to speak
you can't just try and simplify it to "how did you not expect server issues and prepare in advance zenizos" because they have no way of predicting every single specific issue that will inevitably arise each update
yes it sucks you can't play the game for a few hours, but it would suck a lot more if something catastrophic happened like trying to play with 9999999999 ping for hours on end or worst case scenario your character data being rolled back suddenly
Didn’t see coming that something would go wrong. Anything. Every single chapter release there is additional, unplanned, extended maintenance. Perhaps they could try incorporating that into their timelines instead of communicating unrealistic ones, giving players expectations and then, as usual, not meeting them.
as sainguin above said, zos's testing environment is very different to the large numbers of players that interact with the live servers. sometimes the best way to test if something is working properly is to put it under the realistic amount of stress it will experience day to day
you might find that is the case today. zos did testing on their own internal server + the pts (bear in mind the pts sees comparatively little traffic when compared to the live server) to try and iron out any obvious or immediately dangerous issues, and a "stress-test" with the live server (so to speak) will inevitably bring more issues to light
i of course am not an employee at zos, which leads me into my point and main gripe, that i'm not an employee at zenimax online studios i mean that this is a pretty realistic example of what may actually go down when they push updates, but i can't speak for how accurate it is in this specific situation
If ZOS didn’t see it coming that this would happen again
didn't see what coming? you make it sound like every time zenimax have had to take the server down for any reason, it's always the exact same literal reason
networking architecture is unbelievably complex, and i can guarantee you that every day at the office revolves around an entirely new issue that the devs have never seen before, requiring them to re-invent the wheel every update, so to speak
you can't just try and simplify it to "how did you not expect server issues and prepare in advance zenizos" because they have no way of predicting every single specific issue that will inevitably arise each update
yes it sucks you can't play the game for a few hours, but it would suck a lot more if something catastrophic happened like trying to play with 9999999999 ping for hours on end or worst case scenario your character data being rolled back suddenly
Didn’t see coming that something would go wrong. Anything. Every single chapter release there is additional, unplanned, extended maintenance. Perhaps they could try incorporating that into their timelines instead of communicating unrealistic ones, giving players expectations and then, as usual, not meeting them.
as sainguin above said, zos's testing environment is very different to the large numbers of players that interact with the live servers. sometimes the best way to test if something is working properly is to put it under the realistic amount of stress it will experience day to day
you might find that is the case today. zos did testing on their own internal server + the pts (bear in mind the pts sees comparatively little traffic when compared to the live server) to try and iron out any obvious or immediately dangerous issues, and a "stress-test" with the live server (so to speak) will inevitably bring more issues to light
i of course am not an employee at zos, which leads me into my point and main gripe, that i'm not an employee at zenimax online studios i mean that this is a pretty realistic example of what may actually go down when they push updates, but i can't speak for how accurate it is in this specific situation
And what I am saying is that if the stress test fails every time (as it has with all chapter releases that I’ve experienced), perhaps they should allocate time for that in the timeline instead of communicating something that has so far been unrealistic.
Then again, it’s most likely a management decision what times are communicated and not up to people who do the actual work.
but i'd argue it would look even worse if they said "hi guys we're expecting everything to be a massive flop that we'll need to scramble to fix so just a heads up on that one"
If ZOS didn’t see it coming that this would happen again
didn't see what coming? you make it sound like every time zenimax have had to take the server down for any reason, it's always the exact same literal reason
networking architecture is unbelievably complex, and i can guarantee you that every day at the office revolves around an entirely new issue that the devs have never seen before, requiring them to re-invent the wheel every update, so to speak
you can't just try and simplify it to "how did you not expect server issues and prepare in advance zenizos" because they have no way of predicting every single specific issue that will inevitably arise each update
yes it sucks you can't play the game for a few hours, but it would suck a lot more if something catastrophic happened like trying to play with 9999999999 ping for hours on end or worst case scenario your character data being rolled back suddenly
Didn’t see coming that something would go wrong. Anything. Every single chapter release there is additional, unplanned, extended maintenance. Perhaps they could try incorporating that into their timelines instead of communicating unrealistic ones, giving players expectations and then, as usual, not meeting them.
as sainguin above said, zos's testing environment is very different to the large numbers of players that interact with the live servers. sometimes the best way to test if something is working properly is to put it under the realistic amount of stress it will experience day to day
you might find that is the case today. zos did testing on their own internal server + the pts (bear in mind the pts sees comparatively little traffic when compared to the live server) to try and iron out any obvious or immediately dangerous issues, and a "stress-test" with the live server (so to speak) will inevitably bring more issues to light
i of course am not an employee at zos, which leads me into my point and main gripe, that i'm not an employee at zenimax online studios i mean that this is a pretty realistic example of what may actually go down when they push updates, but i can't speak for how accurate it is in this specific situation
And what I am saying is that if the stress test fails every time (as it has with all chapter releases that I’ve experienced), perhaps they should allocate time for that in the timeline instead of communicating something that has so far been unrealistic.
Then again, it’s most likely a management decision what times are communicated and not up to people who do the actual work.
that just kinda goes back to the all important word
unexpected
i get that its not a great look when they need to extend maintenance while all the players were expecting to be able to play, but i'd argue it would look even worse if they said "hi guys we're expecting everything to be a massive flop that we'll need to scramble to fix so just a heads up on that one"
joerginger wrote: »but i'd argue it would look even worse if they said "hi guys we're expecting everything to be a massive flop that we'll need to scramble to fix so just a heads up on that one"
But by now every single person at the studio should be aware that this happens every single time, so it's really amazing to see it's still "unexpected" for them.
If ZOS didn’t see it coming that this would happen again
didn't see what coming? you make it sound like every time zenimax have had to take the server down for any reason, it's always the exact same literal reason
networking architecture is unbelievably complex, and i can guarantee you that every day at the office revolves around an entirely new issue that the devs have never seen before, requiring them to re-invent the wheel every update, so to speak
you can't just try and simplify it to "how did you not expect server issues and prepare in advance zenizos" because they have no way of predicting every single specific issue that will inevitably arise each update
yes it sucks you can't play the game for a few hours, but it would suck a lot more if something catastrophic happened like trying to play with 9999999999 ping for hours on end or worst case scenario your character data being rolled back suddenly
Didn’t see coming that something would go wrong. Anything. Every single chapter release there is additional, unplanned, extended maintenance. Perhaps they could try incorporating that into their timelines instead of communicating unrealistic ones, giving players expectations and then, as usual, not meeting them.
as sainguin above said, zos's testing environment is very different to the large numbers of players that interact with the live servers. sometimes the best way to test if something is working properly is to put it under the realistic amount of stress it will experience day to day
you might find that is the case today. zos did testing on their own internal server + the pts (bear in mind the pts sees comparatively little traffic when compared to the live server) to try and iron out any obvious or immediately dangerous issues, and a "stress-test" with the live server (so to speak) will inevitably bring more issues to light
i of course am not an employee at zos, which leads me into my point and main gripe, that i'm not an employee at zenimax online studios i mean that this is a pretty realistic example of what may actually go down when they push updates, but i can't speak for how accurate it is in this specific situation
And what I am saying is that if the stress test fails every time (as it has with all chapter releases that I’ve experienced), perhaps they should allocate time for that in the timeline instead of communicating something that has so far been unrealistic.
Then again, it’s most likely a management decision what times are communicated and not up to people who do the actual work.
SainguinKrist wrote: »I think you're not giving enough understanding to the fact that they can't possibly foresee every issue with a major patch release.
They try to get as much as they can with the PTS, but the truth is the PTS isn't even a tiny fraction of the games Live server population.
When patches go live there are exponentially more people connecting, interacting with, and exposing what could be issues.
ZOS did their best, and they had to take the game down for a few hours to fix a database issue.
I'm sure they want us ingame just as bad as we want to be ingame.
If ZOS didn’t see it coming that this would happen again
didn't see what coming? you make it sound like every time zenimax have had to take the server down for any reason, it's always the exact same literal reason
networking architecture is unbelievably complex, and i can guarantee you that every day at the office revolves around an entirely new issue that the devs have never seen before, requiring them to re-invent the wheel every update, so to speak
you can't just try and simplify it to "how did you not expect server issues and prepare in advance zenizos" because they have no way of predicting every single specific issue that will inevitably arise each update
yes it sucks you can't play the game for a few hours, but it would suck a lot more if something catastrophic happened like trying to play with 9999999999 ping for hours on end or worst case scenario your character data being rolled back suddenly