Bugged Battlespirit 2.2.9

ksimpscnub18_ESO · January 2016

Xsorus wrote: »

heh i'm happy with my decision on not to bother with PvP till the next patch...

Leveling Alts for the VR change instead

hahahahahaha you actually think this is gonna happen you sad strange little man

Kwivur · January 2016

I demand a re-roll

ksimpscnub18_ESO · January 2016

OdinForge wrote: »

Dreyloch wrote: »

I have a possible reason for this. Might be easy to test too. There was a patch awhile back where camo hunter would agro everything in a room. It was eventually fixed, but since they messed with it again, maybe that agro bug is back.

Just go to the sewers clear one side of the larger rooms. Then pop camo hunter and see if the other side agros. If it does, then that's maybe the reason. I could walk straight into the second room from DC spawn, clear the 2 melee deadra, pop camo hunter and the entire rest of the room from the left would charge straight at me. It was baffling till I went back, didn't use CH, and the mobs remained in place as they should have. Stuff was agroing thru walls too. It was stupid.

Wow.

yes in 1.6 when it was bugged it was due to aggro. if the target was not aggrod on you then the camo hunter proc chance was increased exponentially. not sure why that had anything to do with it because the base ability has nothing to do with aggro but thats why vamps in cloudy bats were hitting huge for camo because the player they were fighting couldnt see them (could not aggro them)

Minno · January 2016

Ezareth wrote: »

Minno wrote: »

Ezareth wrote: »

I was wondering last night why I had lost over 1000 hitpoints. I was checking my gear for broken pieces and wondering WTF I was doing wrong. It completely slipped my mind that it was patch day....I should have known.

I rage quit after playing after about an hour when my 6th or 7th death was caused by the can't use my left click need to /reloadui in the middle of combat bug. It seems worse than ever...

I am so done with this crap. I'm going to play some other games and hopefully ZoS can get their house in order.

What other games you play?

In current order of time consumption:
Ingress (Geolocational capture the flag phone game)
Starcraft II: Legacy of the Void
Hearthstone
The Witcher 3

...and then as of last count about 3 dozen other games that I bought on Steam but never had a chance to play yet haha. So many good games that I haven't had a chance to even look at yet.

Witcher 3 is such an amazing game.

Xsorus · January 2016

Don't worry guys...This game will actually be playable again sometime around CUs launch I hear.

This game at this point is basically the equivalent of using a Chain Saw to remove a splinter in your Toe

Soulac · January 2016

Minno wrote: »

Soulac wrote: »

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.

What about willows path, or rather sets increasing stats in general, and champion passives not working as intended and basically ignoring drink buffs?
You said the same back then.. Like 18 weeks ago.

Might be because they are concentrating on server performance for cyro and various class balance changes for the new update.

No.

booksmcread · January 2016

I hope it's pretty obvious to everyone that the management of this game is atrocious. There is zero oversight and no ownership, which is why we experience these problems constantly. If they keep refusing to step up their game, ESO will go the same route as Warhammer Online, which oddly enough, a ZOS exec was involved with.

Jhunn · January 2016

What a joke.

Dreyloch · January 2016

ksimpscnub18_ESO wrote: »

OdinForge wrote: »

Dreyloch wrote: »

I have a possible reason for this. Might be easy to test too. There was a patch awhile back where camo hunter would agro everything in a room. It was eventually fixed, but since they messed with it again, maybe that agro bug is back.

Just go to the sewers clear one side of the larger rooms. Then pop camo hunter and see if the other side agros. If it does, then that's maybe the reason. I could walk straight into the second room from DC spawn, clear the 2 melee deadra, pop camo hunter and the entire rest of the room from the left would charge straight at me. It was baffling till I went back, didn't use CH, and the mobs remained in place as they should have. Stuff was agroing thru walls too. It was stupid.

Wow.

yes in 1.6 when it was bugged it was due to aggro. if the target was not aggrod on you then the camo hunter proc chance was increased exponentially. not sure why that had anything to do with it because the base ability has nothing to do with aggro but thats why vamps in cloudy bats were hitting huge for camo because the player they were fighting couldnt see them (could not aggro them)

No, the issue I'm talking about was recent. It was happening in the sewers. Maybe as little as 2 months ago? Then all the sudden it stopped. I think maybe its back again. They tried to fix something else wrong with it, and re-introduced the bug I'm talking about.The poster talking about Molag Bal room all agroing seems about right for the same thing I saw way before that room. I can't test it myself atm, I'm at work.

ZOS_GinaBruno · January 2016

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.

Jhunn · January 2016

I'll repeat.

What a joke.

Ezareth · January 2016

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.

Well thanks for the honesty at least / =

MormondPayne_EP · January 2016

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.

Like a broken record...

What is the ETA?
Is this considered a priority?

Efficient · January 2016

MormondPayne_EP wrote: »

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.

Like a broken record...

What is the ETA?
Is this considered a priority?

You will never know.

Erynyes · January 2016

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.

seriously, wow

Glory · January 2016

Derra wrote: »

Congrats to ZOS - battlespirit is no longer effected by any % HP increases your character may have.

This took 3 minutes after logging in to figure out. Congratulations on your "internal testing".

lolol

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.

LOLOL

MormondPayne_EP · January 2016

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.

OMFG?!

duck this game.

Do not thank me for my understanding, I have no understanding and no sympathy left at all.
I now actively hope that Zenimax crash and burn and the game dies so that we are all put out of our misery.

Seriously, In over 20 years of gaming I have never ever seen anything as badly designed, developed and maintained as this shambolic franbkenstein monster from hell. The only humane thing to do now is to kill it with fire.

Don't apologise because you don't mean it, and you know what else? REGRETTABLY console players will have this issue as well, cos you know, duck PC players... TOO BAD that consolers will have the problem. PC players can stick is up their ass, apparently.

"So you will see the fix discussed above in the next major update"

No I wont, I'm not hanging around that long.

Sincerly,
Go duck yourselves.

Ara_Valleria · January 2016

MormondPayne_EP 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.

OMFG?!

duck this game.

Do not thank me for my understanding, I have no understanding and no sympathy left at all.
I now actively hope that Zenimax crash and burn and the game dies so that we are all put out of our misery.

Seriously, In over 20 years of gaming I have never ever seen anything as badly designed, developed and maintained as this shambolic franbkenstein monster from hell. The only humane thing to do now is to kill it with fire.

Don't apologise because you don't mean it, and you know what else? REGRETTABLY console players will have this issue as well, cos you know, duck PC players... TOO BAD that consolers will have the problem. PC players can stick is up their ass, apparently.

"So you will see the fix discussed above in the next major update"

No I wont, I'm not hanging around that long.

Sincerly,
Go duck yourselves.

Annnnnnnnnnnnnnnnnnnnnnd now this thread is going to be closed because of that /quit post. Rip

MormondPayne_EP · January 2016

Ara_Valleria wrote: »

MormondPayne_EP 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.

OMFG?!

duck this game.

Do not thank me for my understanding, I have no understanding and no sympathy left at all.
I now actively hope that Zenimax crash and burn and the game dies so that we are all put out of our misery.

Seriously, In over 20 years of gaming I have never ever seen anything as badly designed, developed and maintained as this shambolic franbkenstein monster from hell. The only humane thing to do now is to kill it with fire.

Don't apologise because you don't mean it, and you know what else? REGRETTABLY console players will have this issue as well, cos you know, duck PC players... TOO BAD that consolers will have the problem. PC players can stick is up their ass, apparently.

"So you will see the fix discussed above in the next major update"

No I wont, I'm not hanging around that long.

Sincerly,
Go duck yourselves.

Annnnnnnnnnnnnnnnnnnnnnd now this thread is going to be closed because of that /quit post. Rip

Good.

AbraXuSeXile · January 2016

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.

Wow you guys are bad

This game is still p2p, you have all devs working on crap we have to pay for and we are left with someone breaking an already unplayable game

OdinForge · January 2016

AbraXuSeXile 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.

Wow you guys are bad

This game is still p2p, you have all devs working on crap we have to pay for and we are left with someone breaking an already unplayable game

MisterBigglesworth · January 2016

Iyas wrote: »

Haha turn based

spam ambush for the next 20 rounds

Minno · January 2016

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.

Thank you Gina!
Look forward for the next fix.

Teargrants · January 2016

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...

MisterBigglesworth · January 2016

@Teargrants Which game? I may have to check it out...

Teargrants · January 2016

MisterBigglesworth wrote: »

@Teargrants Which game? I may have to check it out...

Dynasty Warriors Online, been out since 2006, they only have JP, TW, CN servers though.

https://www.youtube.com/watch?v=R6jBKXePVts

Wollust · January 2016

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.

*slow clap*

ItsDyvim · January 2016

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.

Such a sad state this game is in. I really liked it, but HOLY CRAP.

If this was a PVE grind spot we'd have a hotfix by now. Or a fishing bug. PVP? Ah, you can wait 6 months.

Good job.

MormondPayne_EP · January 2016

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.

Manoekin · January 2016

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.