ZOS_GinaBruno wrote: »Hi everyone,
To follow up on this, we are working on a fix for this issue. Unfortunately due to the nature and complexity of the fix, the soonest we'll have it rolled out is the next incremental patch on PC.
Regrettably, console players will see this issue as well once the console incremental patch is released (likely later this month). We are in the middle of sending this patch to cert, and our intention was to have the original fix for Battle Spirit as listed in the patch notes included. We are unable to get the fix for today's issue included in that patch, so you will see the fix discussed above in the next major update.
Again, we apologize for this. It's certainly not our intention to publish fixes that end up breaking something in-game, and want to get everything remedied as soon as possible for everyone. Thanks for understanding, all.
@ZOS_GinaBruno When is the next major update? You do know you are allowed to give us estimations? Keeping us completely in the dark is hell of a lot worse than a wrong estimation.
First we have *** conditions like lag and horrid fps drops. This largely makes cyrodiil unplayable. Now this? Do you know why we are so critical? Because this type of *** has been happening since beta and nothing has changed. Wait let me rephrase that, a paid beta test without transparency from the dev team. What a joke.
ZOS_GinaBruno wrote: »Hi everyone,
To follow up on this, we are working on a fix for this issue. Unfortunately due to the nature and complexity of the fix, the soonest we'll have it rolled out is the next incremental patch on PC.
Regrettably, console players will see this issue as well once the console incremental patch is released (likely later this month). We are in the middle of sending this patch to cert, and our intention was to have the original fix for Battle Spirit as listed in the patch notes included. We are unable to get the fix for today's issue included in that patch, so you will see the fix discussed above in the next major update.
Again, we apologize for this. It's certainly not our intention to publish fixes that end up breaking something in-game, and want to get everything remedied as soon as possible for everyone. Thanks for understanding, all.
@ZOS_GinaBruno When is the next major update? You do know you are allowed to give us estimations? Keeping us completely in the dark is hell of a lot worse than a wrong estimation.
First we have *** conditions like lag and horrid fps drops. This largely makes cyrodiil unplayable. Now this? Do you know why we are so critical? Because this type of *** has been happening since beta and nothing has changed. Wait let me rephrase that, a paid beta test without transparency from the dev team. What a joke.
Even better than schedule estimations on this specific problem would be if they told us what concrete measures are being taken at ZOS company to prevent such stuff from happening with every patch like it is now.
ZOS_GinaBruno wrote: »Hi everyone,
To follow up on this, we are working on a fix for this issue. Unfortunately due to the nature and complexity of the fix, the soonest we'll have it rolled out is the next incremental patch on PC.
Regrettably, console players will see this issue as well once the console incremental patch is released (likely later this month). We are in the middle of sending this patch to cert, and our intention was to have the original fix for Battle Spirit as listed in the patch notes included. We are unable to get the fix for today's issue included in that patch, so you will see the fix discussed above in the next major update.
Again, we apologize for this. It's certainly not our intention to publish fixes that end up breaking something in-game, and want to get everything remedied as soon as possible for everyone. Thanks for understanding, all.
ZOS_GinaBruno wrote: »Hi everyone,
To follow up on this, we are working on a fix for this issue. Unfortunately due to the nature and complexity of the fix, the soonest we'll have it rolled out is the next incremental patch on PC.
Regrettably, console players will see this issue as well once the console incremental patch is released (likely later this month). We are in the middle of sending this patch to cert, and our intention was to have the original fix for Battle Spirit as listed in the patch notes included. We are unable to get the fix for today's issue included in that patch, so you will see the fix discussed above in the next major update.
Again, we apologize for this. It's certainly not our intention to publish fixes that end up breaking something in-game, and want to get everything remedied as soon as possible for everyone. Thanks for understanding, all.
@ZOS_GinaBruno When is the next major update? You do know you are allowed to give us estimations? Keeping us completely in the dark is hell of a lot worse than a wrong estimation.
First we have *** conditions like lag and horrid fps drops. This largely makes cyrodiil unplayable. Now this? Do you know why we are so critical? Because this type of *** has been happening since beta and nothing has changed. Wait let me rephrase that, a paid beta test without transparency from the dev team. What a joke.
Even better than schedule estimations on this specific problem would be if they told us what concrete measures are being taken at ZOS company to prevent such stuff from happening with every patch like it is now.
LegendaryChef wrote: »ZOS_GinaBruno wrote: »Hi everyone,
To follow up on this, we are working on a fix for this issue. Unfortunately due to the nature and complexity of the fix, the soonest we'll have it rolled out is the next incremental patch on PC.
Regrettably, console players will see this issue as well once the console incremental patch is released (likely later this month). We are in the middle of sending this patch to cert, and our intention was to have the original fix for Battle Spirit as listed in the patch notes included. We are unable to get the fix for today's issue included in that patch, so you will see the fix discussed above in the next major update.
Again, we apologize for this. It's certainly not our intention to publish fixes that end up breaking something in-game, and want to get everything remedied as soon as possible for everyone. Thanks for understanding, all.
If it is not your intention to publish fixes that end up breaking something then why on earth would you go ahead with the console update when the "fix" is already known to break the game?
Teargrants wrote: »Dynasty Warriors Online, been out since 2006, they only have JP, TW, CN servers though.MisterBigglesworth wrote: »@Teargrants Which game? I may have to check it out...https://www.youtube.com/watch?v=R6jBKXePVts
MormondPayne_EP wrote: »From the Patch Notes:
Combat & Gameplay
General
Fixed an issue where Battle Spirit would occasionally fail to apply when you entered Cyrodiil or Imperial City.
Note: The Battle Spirit buff will no longer show up in your Active Effect window or in the buff trackers of various player-created addons. This is a temporary change, and will be fixed in Update 9 (our next major update).
Guild
Fighters Guild
Camouflaged Hunter: Fixed an issue where the stealth damage proc would occur multiple times in specific circumstances.
BOTH of these have not been fixed...
I'm searching for more.
Teargrants wrote: »You know, in the last F2P mmo (not even B2P) I played, we had monthly content update & rebalances. But, the most important thing was, whenever a bug was introduced in one of those updates, there would be a server rollback w/in 24 hrs to the last patch version. Then typically the fixed patch would be release w/in a week.
Must seem cray cray to ZOS to prioritize bug prevention over 'content' updates...
I think their biggest issue is that they do literally not know how to fix certain things + they do not have enough ressources.
So it will take them like 4x the time to fix smth because they aint got no darn clue wtf is going on.
RAGUNAnoOne wrote: »LegendaryChef wrote: »ZOS_GinaBruno wrote: »Hi everyone,
To follow up on this, we are working on a fix for this issue. Unfortunately due to the nature and complexity of the fix, the soonest we'll have it rolled out is the next incremental patch on PC.
Regrettably, console players will see this issue as well once the console incremental patch is released (likely later this month). We are in the middle of sending this patch to cert, and our intention was to have the original fix for Battle Spirit as listed in the patch notes included. We are unable to get the fix for today's issue included in that patch, so you will see the fix discussed above in the next major update.
Again, we apologize for this. It's certainly not our intention to publish fixes that end up breaking something in-game, and want to get everything remedied as soon as possible for everyone. Thanks for understanding, all.
If it is not your intention to publish fixes that end up breaking something then why on earth would you go ahead with the console update when the "fix" is already known to break the game?
THIS call it back or something and submit a new one then
In my own work office, our development team and workflow systems are ran incompetently, but this is on a whole new level.
An apology in this case does not suffice, you need a development structure that allows for rollbacks before they are pushed live. The PTS seems to be more like a staging server, I don't think I have seen 10% of the issues brought up in PTS testing ever get fixed before they go to the live server.
Every development process involves mistakes, but the way they are handled in this game is nothing but amateur.
ZoS clearly has some of the most intelligent developers around, but the way management deals with certain aspects of the game development completely ruin it for the guys who are actually great at their job.
I'm not white knighting them lol but it's getting old to mindlessly write how much you hate them when they clearly don't read your nonconstructive insults.the battle spirit is hardly an issue, barely anyone is worrying about it since it affects everyone, theres really not too much to fret about here honestly. i didn't even know till people talked about it. didnt make a difference eitherjohan.danielsson1994b16_ESO wrote: »LegendaryChef wrote: »ZOS_GinaBruno wrote: »Hi everyone,
To follow up on this, we are working on a fix for this issue. Unfortunately due to the nature and complexity of the fix, the soonest we'll have it rolled out is the next incremental patch on PC.
Regrettably, console players will see this issue as well once the console incremental patch is released (likely later this month). We are in the middle of sending this patch to cert, and our intention was to have the original fix for Battle Spirit as listed in the patch notes included. We are unable to get the fix for today's issue included in that patch, so you will see the fix discussed above in the next major update.
Again, we apologize for this. It's certainly not our intention to publish fixes that end up breaking something in-game, and want to get everything remedied as soon as possible for everyone. Thanks for understanding, all.
If it is not your intention to publish fixes that end up breaking something then why on earth would you go ahead with the console update when the "fix" is already known to break the game?
Cause they have to pay for every update they make on console systems, and probably already paid for it...
So? if they have to "hot"fix this issues they have to pay anyway a other time. so wouldnt matter if they retread the current patch for consols
would you rather have all the current broken things left in console to avoid a minuscule bug? people are just jumping the hate zos bangwagon because they are bored and it's always fun to insult zos over something so minor
Stop trying to white knight ZOS.
People don't give a *** about the bug itself, so much as the fact that ZOS couldn't catch something so simple as OP who noticed it 3 minutes into the game. This is how ZOS handles themselves on the daily for the past year, that doesn't sit well with most sane people.
GreenSoup2HoT wrote: »@FENGRUSH
Me and you both know screen-shot's from any player's character sheet can be easily exploited to show ridiculous number's for "show and tell".
Back to the thread's topic... it's absolutely outrageous how Zos fail's to maintain and implement new content without even polishing it first. What's the point of Zos even having a PTS? Half the *** implemented in IC was not wanted by the entire community and still went threw to live.
So know as a console player i have to deal with even less health because Zos can push this fix into the next "Incremental"... the worst part is i need to wait possibly month's for this fix?
How long do we have to wait for the gap closer stun's to be addressed?
How long do we have to wait for the performance to be addressed?
The list goes on and on. I watch your stream, you see me around. I've heard your rant's and i've also had my own. There's nothing we can do and it's a shame the community doesn't have a voice. Even when are voice is heard it's misunderstood.
GreenSoup2HoT wrote: »WOW ZOS ..... as a console player im furious. this is b.s!
get your **** together!! im on the edge...im going to throw this bug infested game in the trash
GreenSoup2HoT wrote: »WOW ZOS ..... as a console player im furious. this is b.s!
get your **** together!! im on the edge...im going to throw this bug infested game in the trash
I don't think I've ever experienced an in-game bug that's ABOUT to be implemented lmao. This is unprecedented.
Teargrants wrote: »I request we officially change the name of Patch Notes to Bug Notes.
I love you Teargrants, will you have my babies?Teargrants wrote: »I request we officially change the name of Patch Notes to Bug Notes.