Maintenance for the week of October 6:
• [COMPLETE] ESO Store and Account System for maintenance – October 8, 2:00PM EDT (18:00 UTC) - 6:00PM EDT (22:00 UTC)
• [COMPLETE] ESO Store and Account System for maintenance – October 8, 2:00PM EDT (18:00 UTC) - 6:00PM EDT (22:00 UTC)
Bugged Battlespirit 2.2.9
-
Keiryan✭✭✭Never mind.
It's really not even worth complaining and pointing out the incompetence anymoreEdited by Keiryan on January 13, 2016 3:21AMKeiryan / Yuluka / Keir Jong-Un
Glorious Leader of North DC and The K-Hole6 -
MormondPayne_EP✭✭✭✭MormondPayne_EP wrote: »I have an idea for a PvP player protest...
How about we all congregate in a popular PvE spot, as many people as we can get and sit there spamming AOE's, Heals, purges or whatever and lag the absolute *** out of PvE.
We'll see if that gets any attention.
What is the bet they jump on that faster than you can blink.
Did that one time in Auridon. 4 GM's showed up to answer questions, and this was back when orbs were a thing. So some people started orb bombing the GM's and lagging Auridon. Lead to a long, hilarious night.
Sounds like a plan then...2 -
Talcyndl✭✭✭✭✭Hmmmm....thought my health was a little low.
Tal'gro Bol
PvP Vice Officer [Retired] and Huscarl of Vokundein
http://www.legend-gaming.net/vokundein/0 -
Soulac✭✭✭✭✭
✭✭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.
Are you telling us that we get the fix for passives not increasing the battlespirit health buff earlier than a fix for sets and champion passives not increasing drink buffs?
R.I.P Dawnbreaker / Auriel´s Bow
Member of the Arena Guild and the overpowered Banana Squad.
Nathaerizh aka Cat - Nightblade V16 - EU
- Meow -7 -
Huckdabuck✭✭✭✭✭incompetence
noun | in·com·pe·tence | \in-ˈkäm-pə-təns\
Definition of incompetence
1: the inability to do a good job <… they were frustrated by their … own incompetence. — Jack London, The Call of the Wild>
Examples of incompetence
1. Because of his incompetence, we won't make our deadline.
2. She was fired for gross incompetence.
Synonyms: impotence, inadequacy, incapability, incapacity, inability, incompetency, ineptitude, insufficiency, powerlessness
Antonyms: ability, adequacy, capability, capacity, competence, competency, potency
Texashighelf - VR16 Sorcerer EP NA - FILTHY BARBARIAN
Texasimperial - VR16 Dragonknight EP NA - How do you like your DK?
Texas'Imperial - VR16 Dragonknight DC NA - How do you like your DK?
Texas-Imperial - VR16 Templar DC NA - Queue Clogging Lagsploitter
Texas Highelf - VR16 Sorcerer DC NA - Queue Clogging Lagsploitter
Texas Imperial - VR16 Nightblade DC NA - Queue Clogging LagsploitterJessica Folsom wrote:It's a very grey area.12 -
Tower_Of_Shame✭✭✭✭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.
Are you telling us that we get the fix for passives not increasing the battlespirit health buff earlier than a fix for sets and champion passives not increasing drink buffs?
Let's face it, they give a flying f*ck about your problem with that set... probably it will never get a fix. Like many other bugs which are here for a long time now...
2 -
Soris✭✭✭✭✭
✭
Why you cant just roll back everything you did with that patch and redo again? Come one guys are you really gonna leave this issue till the next major update?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.Welkynd [Templar/AD/EU]3 -
BuggeX✭✭✭✭✭
✭ZOS_GinaBruno wrote: »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.
well @ZOS_GinaBruno i cant understand it any more........ this doesnt just happen once a while, which would be ok, anyone Fails at times. But this is on a regular weekly Basis for any incremental patch you release....#makemagickadkgreataigan
#givemeaexecute
#ineedheal
#betterhotfixgrindspots7 -
AlcastClass RepresentativeTeargrants 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.https://alcasthq.com - Alcasthq.com Builds & Guides
https://eso-hub.com - ESO-Hub.com Sets, Skills, Guides & News
https://dwemerautomaton.com - Discord, Telegram & Twitch Command Bot4 -
PainfulFAFA✭✭✭✭✭
✭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.
WHY GINA WHYYYY >:(
3 -
LegendaryChef✭✭✭✭✭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?Zzoro/Elliot Brown/Baldy ~Kitesquad/Noricum~
PC EU.
Spider mount was the only good part about morrowind release.22 -
MormondPayne_EP✭✭✭✭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?
Because logic and ZOS are mutually exclusive terms...7 -
Tower_Of_Shame✭✭✭✭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 at ZoS they use Quantity over Quality uhhh this year we made xxxx incremental patch, and then the leadership/managment is like:
"GJ boys keep going."
9 -
T3hOwnage69✭✭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.
Are you telling us that we get the fix for passives not increasing the battlespirit health buff earlier than a fix for sets and champion passives not increasing drink buffs?
the gods forbid you to use your willows path set as intended0 -
Nifty2g✭✭✭✭✭
✭✭✭✭✭they said they are fixing it next patch why you guys all throwing a fit
just unlucky for the console players#MOREORBS0 -
themdogesbite✭✭✭✭✭
✭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...:]1 -
BuggeX✭✭✭✭✭
✭johan.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#makemagickadkgreataigan
#givemeaexecute
#ineedheal
#betterhotfixgrindspots1 -
Nifty2g✭✭✭✭✭
✭✭✭✭✭
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
#MOREORBS1 -
BuggeX✭✭✭✭✭
✭
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
im not saying let the Bugs left 4ever.
im saying it would not matter if they retread the patch or not, since they have to pay it anyway twice.
#makemagickadkgreataigan
#givemeaexecute
#ineedheal
#betterhotfixgrindspots0 -
themdogesbite✭✭✭✭✭
✭johan.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
No, thats exactly what gina said they wouldn't do, she said that they will include it in another "incremential patch". Meaning that they will include the fix in a patch that was going to be scheduled no matter if the issue was present or not.:]1 -
Jhunn✭✭✭✭✭
✭
Or maybe it's because they yet again show their incompetence.
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
Calling stuff like this minor which happens so frequently really tells how lowered your expectations are from playing this game for so long.Gave up.11 -
themdogesbite✭✭✭✭✭
✭
Or maybe it's because they yet again show their incompetence.
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
Calling stuff like this minor which happens so frequently really tells how lowered your expectations are from playing this game for so long.
Friendly reminder how long this took to fix;
https://www.youtube.com/watch?v=Uq2-Zl1PETM
And game was still better at that point then now.:]2 -
BuggeX✭✭✭✭✭
✭johan.danielsson1994b16_ESO wrote: »
Or maybe it's because they yet again show their incompetence.
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
Calling stuff like this minor which happens so frequently really tells how lowered your expectations are from playing this game for so long.
Friendly reminder how long this took to fix;https://www.youtube.com/watch?v=Uq2-Zl1PETM
And game was still better at that point then now.
found this better
https://www.youtube.com/watch?v=EMJfGiWEXd0 #makemagickadkgreataigan
#givemeaexecute
#ineedheal
#betterhotfixgrindspots0 -
Wollust✭✭✭✭✭
✭✭✭✭johan.danielsson1994b16_ESO wrote: »
Or maybe it's because they yet again show their incompetence.
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
Calling stuff like this minor which happens so frequently really tells how lowered your expectations are from playing this game for so long.
Friendly reminder how long this took to fix;https://www.youtube.com/watch?v=Uq2-Zl1PETM
And game was still better at that point then now.
That wouldn't be possible nowadays because there would be too much lag with so many people to reliably activate stuff and move and whatever Susano'o
Zerg Squad2 -
OdinForge✭✭✭✭✭
✭✭
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.Edited by OdinForge on January 13, 2016 1:02PMThe Age of Wrobel.15 -
Tankqull✭✭✭✭✭
✭ZOS_GinaBruno wrote: »Thanks, everyone. Just wanted to let you know that we are aware and investigating this. We'd like to get it fixed as soon as possible.
Why do you guys never consider a rollback?
Because every player out there that logged in after the original patch would lose whatever progress, items, gold, etc, that they had acquired during the time between patch and rollback. Can you imagine the screamin' and cryin'?!?!?
I'm not sure if you're aware of what a rollback indicates.
Based on the contents in this game, simply rolling back a few patches might make elements break. It seems the entire game is one custom effort.
QFT.
Things are head together by strings and duct tape.
its more like hopes and wishes...spelling and grammar errors are free to be abused
Sallington wrote: »Anything useful that players are wanting added into the game all fall under the category of "Yer ruinin my 'mersion!"0
