pink_panther wrote: »
Yea but this gamebreaking bugs were reported during PTS. Reported multiple times....
No excuses stop defending ZoS. They did a bad job. [snip]
Even alcast complained in a video when he tested it on PTS and they still released it like this...
JhonathanD wrote: »
JhonathanD wrote: »The fact that you so quickly fixed the moments with the non-working Crown Store (in the first place) showed everything.
JhonathanD wrote: »The fact that you so quickly fixed the moments with the non-working Crown Store (in the first place) showed everything.now this?
this gets on my nerves.
are you just being crass on purpose, or do you legitimately think that the nature of crown store issues is in any way comparable to real gameplay bugs? or that the same team is responsible for both? and their boss trudges over, put his hands on their shoulders and whispers suavely: "you better fix the crown store right *** now. i don't care if players crash the moment they step in a dungeon. i want that crown store up and running pronto!"
so of course, the poor sods, all dozens of coders, sob on their keyboards as they work overtime, just to fix that damn crown store.
is that what you think happens?
or are you just bashing on ZOS (which are, in my opinion as well, monetizing aggressively)?
and you know that, in reality, the nature of these issues is vastly different, and different people work on them, therefore the crown store being fixed first is not because they prioritized it agaist everything else... but frankly, most likely because it was disabled due to one of these reasons:
-an exploit
-an issue with billing
-an issue with item delivery
none of these are meatballs stuck in the spaghetti code.
most of these can be fixed by any coder with decent experience.
so please, put two braincells together before you cry into the sky "oh but of course they fixed the crown store first!"
IT'S EASIER!
JhonathanD wrote: »JhonathanD wrote: »The fact that you so quickly fixed the moments with the non-working Crown Store (in the first place) showed everything.now this?
this gets on my nerves.
are you just being crass on purpose, or do you legitimately think that the nature of crown store issues is in any way comparable to real gameplay bugs? or that the same team is responsible for both? and their boss trudges over, put his hands on their shoulders and whispers suavely: "you better fix the crown store right *** now. i don't care if players crash the moment they step in a dungeon. i want that crown store up and running pronto!"
so of course, the poor sods, all dozens of coders, sob on their keyboards as they work overtime, just to fix that damn crown store.
is that what you think happens?
or are you just bashing on ZOS (which are, in my opinion as well, monetizing aggressively)?
and you know that, in reality, the nature of these issues is vastly different, and different people work on them, therefore the crown store being fixed first is not because they prioritized it agaist everything else... but frankly, most likely because it was disabled due to one of these reasons:
-an exploit
-an issue with billing
-an issue with item delivery
none of these are meatballs stuck in the spaghetti code.
most of these can be fixed by any coder with decent experience.
so please, put two braincells together before you cry into the sky "oh but of course they fixed the crown store first!"
IT'S EASIER!
This does not change the essence of the topic, I do not want to wait two weeks until the errors are corrected, I do not care what problems they have and how many people are responsible for certain aspects. I am a customer who has spent enough money on this product, and I demand quality, not a forced vacation.
JhonathanD wrote: »JhonathanD wrote: »The fact that you so quickly fixed the moments with the non-working Crown Store (in the first place) showed everything.now this?
this gets on my nerves.
are you just being crass on purpose, or do you legitimately think that the nature of crown store issues is in any way comparable to real gameplay bugs? or that the same team is responsible for both? and their boss trudges over, put his hands on their shoulders and whispers suavely: "you better fix the crown store right *** now. i don't care if players crash the moment they step in a dungeon. i want that crown store up and running pronto!"
so of course, the poor sods, all dozens of coders, sob on their keyboards as they work overtime, just to fix that damn crown store.
is that what you think happens?
or are you just bashing on ZOS (which are, in my opinion as well, monetizing aggressively)?
and you know that, in reality, the nature of these issues is vastly different, and different people work on them, therefore the crown store being fixed first is not because they prioritized it agaist everything else... but frankly, most likely because it was disabled due to one of these reasons:
-an exploit
-an issue with billing
-an issue with item delivery
none of these are meatballs stuck in the spaghetti code.
most of these can be fixed by any coder with decent experience.
so please, put two braincells together before you cry into the sky "oh but of course they fixed the crown store first!"
IT'S EASIER!
This does not change the essence of the topic, I do not want to wait two weeks until the errors are corrected, I do not care what problems they have and how many people are responsible for certain aspects. I am a customer who has spent enough money on this product, and I demand quality, not a forced vacation.
yeah, that part i agree with, that's why i didn't say anything regarding that.
it is unacceptable that the product they sell be broken so deeply for so long.
however, again, like all things, it has a cause beyond just "ZOS is spiteful" or anything like that.
that cause may be incompetence, bureaucracy, or poor management. who knows.
nobody wants to sell a broken product. nobody wants to have a broken game.
let's not forget that ESO is probably the largest, most complex MMO on the market.
whatever happens to it, be it good or bad, is the result of a very intricate, complex system.
i do not think the buggy launch or the two weeks to fix it are acceptable.
but let's not get so riled up over it, and understand that it has a cause beyond "ZOS bad".
we've got other things to do in the meantime.
vote with your time & your wallet.
if nov revenue dips (and it will),
that's hard data for ZOS.
that they can't ignore.
EdmondDontes wrote: »How many of the lag and other performance issues are the result of moving so many calculations server side to accommodate Stadia and other hardware weak platforms?
JhonathanD wrote: »JhonathanD wrote: »The fact that you so quickly fixed the moments with the non-working Crown Store (in the first place) showed everything.now this?
this gets on my nerves.
are you just being crass on purpose, or do you legitimately think that the nature of crown store issues is in any way comparable to real gameplay bugs? or that the same team is responsible for both? and their boss trudges over, put his hands on their shoulders and whispers suavely: "you better fix the crown store right *** now. i don't care if players crash the moment they step in a dungeon. i want that crown store up and running pronto!"
so of course, the poor sods, all dozens of coders, sob on their keyboards as they work overtime, just to fix that damn crown store.
is that what you think happens?
or are you just bashing on ZOS (which are, in my opinion as well, monetizing aggressively)?
and you know that, in reality, the nature of these issues is vastly different, and different people work on them, therefore the crown store being fixed first is not because they prioritized it agaist everything else... but frankly, most likely because it was disabled due to one of these reasons:
-an exploit
-an issue with billing
-an issue with item delivery
none of these are meatballs stuck in the spaghetti code.
most of these can be fixed by any coder with decent experience.
so please, put two braincells together before you cry into the sky "oh but of course they fixed the crown store first!"
IT'S EASIER!
This does not change the essence of the topic, I do not want to wait two weeks until the errors are corrected, I do not care what problems they have and how many people are responsible for certain aspects. I am a customer who has spent enough money on this product, and I demand quality, not a forced vacation.
yeah, that part i agree with, that's why i didn't say anything regarding that.
it is unacceptable that the product they sell be broken so deeply for so long.
however, again, like all things, it has a cause beyond just "ZOS is spiteful" or anything like that.
that cause may be incompetence, bureaucracy, or poor management. who knows.
nobody wants to sell a broken product. nobody wants to have a broken game.
let's not forget that ESO is probably the largest, most complex MMO on the market.
whatever happens to it, be it good or bad, is the result of a very intricate, complex system.
i do not think the buggy launch or the two weeks to fix it are acceptable.
but let's not get so riled up over it, and understand that it has a cause beyond "ZOS bad".
we've got other things to do in the meantime.
vote with your time & your wallet.
if nov revenue dips (and it will),
that's hard data for ZOS.
that they can't ignore.
JhonathanD wrote: »It looks like it's worth giving up the game for a month or two. The fact that you so quickly fixed the moments with the non-working Crown Store (in the first place) showed everything.
MasterSpatula wrote: »Said it before and I'll say it again: Anyone with the slightest regard for their customers would have told Google to take a flying f*** when they demanded the two-week update schedule. Such a person would have had no choice.
ZOS_GinaBruno wrote: »If an emergency arises, we’ll of course work with Stadia to get a patch published ASAP. So in general, PC incrementals will now occur bi-weekly, but if needed, we can update quickly.
MasterSpatula wrote: »Said it before and I'll say it again: Anyone with the slightest regard for their customers would have told Google to take a flying f*** when they demanded the two-week update schedule. Such a person would have had no choice.ZOS_GinaBruno wrote: »If an emergency arises, we’ll of course work with Stadia to get a patch published ASAP. So in general, PC incrementals will now occur bi-weekly, but if needed, we can update quickly.
They could fix it right away.... it's just not important enough to them.
https://forums.elderscrollsonline.com/en/discussion/530103/changes-to-pc-incremental-patch-cadence#latest
You can't just push code without permission or whatever policies imposed on them. Either way things got more complex over at ZOS.
You can't just push code without permission or whatever policies imposed on them. Either way things got more complex over at ZOS.
pink_panther wrote: »
Yea but this gamebreaking bugs were reported during PTS. Reported multiple times....
No excuses stop defending ZoS. They did a bad job. [snip]
Even alcast complained in a video when he tested it on PTS and they still released it like this...
[Edited to remove Bashing]
Unsubscribed my Eso+
Won't be giving my money to a company that displays this kind of attitude to it's loyal customer base. I have said this previously and i will say it again, i have NEVER played an MMO that encounters the sheer amount of broken content that ESO does at EVERY single patch.
BrownChicken wrote: »There is a positive side. My ping now, even in trials, rarely rises above the minimum values (116-130ms) and fps rarely stays below 60. I have not been to Cyrodiil yet, but all pve works fine. I'm afraid that after fixing light attacks everything will become worse as it was. Perhaps ZOS should pay more attention to the code at this point.