Game Breaking Negate Bug

DTStormfox

People are currently knowingly exploiting this bug in pvp. This is unacceptable and a violation of Code of Conduct section 5.2.

@ZOS_GinaBruno please check support ticket references:
231107-002931
231107-002953
231107-002963

Beaverton

Crown wrote: »

I logged in to play in PvP today, had it happen to me three times in 10 minutes going to the bridge, swore a bit and logged off. I'm going to play Bladur's Gate this evening, where if I get frustrated it's my own fault..

Hmmmm...I find it hard to believe that griefers and trolls were at the bridge . . .

TechMaybeHic

Went all night without it. End of the night, ran into a particular group we've seen before tonight when we would get it regularly; and several of us got it. Yeah; is say it's mostly intentional

IZZEFlameLash

TechMaybeHic wrote: »

Went all night without it. End of the night, ran into a particular group we've seen before tonight when we would get it regularly; and several of us got it. Yeah; is say it's mostly intentional

Yeah, even if the method was to be complex like in the past, bad actors always will exploit. Just that now it is easy access, a lot more exploit... quite unfortunate that this will be only addressed at incremental patch dates despite the damage it does.

ForumSavant

They did not comment here, but on the other post they said there will be a fix on Monday.

DTStormfox

ForumSavant wrote: »

They did not comment here, but on the other post they said there will be a fix on Monday.

Regardless of that announcement, the fact that people are exploiting the bug and, seemingly, getting away with it without consequences is very unfavourable for the status of the community.

Panderbander

DTStormfox wrote: »

ForumSavant wrote: »

They did not comment here, but on the other post they said there will be a fix on Monday.

Regardless of that announcement, the fact that people are exploiting the bug and, seemingly, getting away with it without consequences is very unfavourable for the status of the community.

Much like the bugged double-infused jewelry a while back, ZOS will probably do nothing about it. I mean, just look at a certain streamer that was banned for showing exploits on stream recently then was welcomed back with--according to him--a package of a free year of ESO+

IZZEFlameLash

Panderbander wrote: »

DTStormfox wrote: »

ForumSavant wrote: »

They did not comment here, but on the other post they said there will be a fix on Monday.

Regardless of that announcement, the fact that people are exploiting the bug and, seemingly, getting away with it without consequences is very unfavourable for the status of the community.

Much like the bugged double-infused jewelry a while back, ZOS will probably do nothing about it. I mean, just look at a certain streamer that was banned for showing exploits on stream recently then was welcomed back with--according to him--a package of a free year of ESO+

In his own words, he was banned by weaponized mass reports with that vid. And he said that... they kinda don't care about that particular exploit. That it is an 'overtuned intended mechanic' as per the dev, iirc.

And this is getting even more ridiculous with all the 'video game experts' groups using this now very blatantly and openly.

Auldwulfe

Per the patch notes, this has been fixed -- want to verify, so I can start bringing my sorc out to Cyrodiil, again.....
I had changed out the negate for another ultimate... but I also noticed that people avoided me, as I was a sorc... or would rush me in big groups, to take me down quick... neither of which was fun.

Auldwulfe

Crown

If anyone is curious reading this at some point in the future, there weren't any bans or even warnings (that anyone is aware of) sent to those who exploited this for two solid weeks until it was fixed (and another bug introduced that is just as impactful but single target).

TechMaybeHic

Crown wrote: »

If anyone is curious reading this at some point in the future, there weren't any bans or even warnings (that anyone is aware of) sent to those who exploited this for two solid weeks until it was fixed (and another bug introduced that is just as impactful but single target).

You mean something else is going around?