GAME BREAKING ISSUE - spamming block can now disconnect you from the server

jadarock

People complain about the tank meta zos nerfs them to the home screen lol

Fur_like_snow

Can confirm that spamming block for about 10-15 sec will result in a boot to login screen. It’s almost like none asked them to “fix” block animation. What a horrifying mess this patch turned out to be.

ZonasArch

Royaji wrote: »

Dusk_Coven wrote: »

L2Pissue wrote: »

Yep it works
I just spammed block for 15 seconds to log out,
Thanks for this feature.

Then maybe don't go around spamming block for 15 seconds till your kicked?
If it turns out to be destabilizing the server and/or affecting the players around you, honestly a kick should be followed by a ban for deliberately sabotaging the game.

Stop shooting yourselves in the foot and asking ZOS for a bandaid.

So you are going to place the blame on the player who discovered a quite serious bug and made others aware of it and not the developer who has either failed to discover such a serious problem as part of the internal testing or considered it acceptable to release a patch with this problem despite being aware of it?

Spamming block for 15 seconds isn't a serious issue, it's a proof of concept. Nobody spams it like that anywhere.

The real issue is how does this connect to normal gameplay disconnections while blocking.

You guys need to learn how to make complaints so you don't sound like desperate fools. This is important! Don't be all "internety" about it. Be reasonable.

shadyjane62

The past week has taught me you don't have to be doing any thing to get DC'd and crashed out of Cyro.pvp is the onlt thing I like to do. Have already cancelled recurring sub.

Olupajmibanan

Got booted to login on two consecutive pulls in vet AS+2 at around 20% of boss hp.

When Fires began, my ground abilities stopped working. I could use other abilities normaly but ground abilities simply didn't work. I thought that I got booted for hard spamming my Luminous Shards in misbelief that it will eventualy go off (this should not boot me either, it's not my fault that abilities randomly stop working). But now that you say it, I surely block a lot in that phase, constanly dropping and activating block because 999999 mechanics occur, so I might got booted for block bug or combination of the two: hard spam of abilities + blocking.

Celephantsylvius_Bornasfinmo

I see no changes wake up in the morning and I ask myself
Is ESO worth playing should I delete it myself?
I'm tired of crashin' and even worse I'm kicked
My head hurts so I'm lookin' on the forum for a patch to snatch
ZOS gives no damn about a playa
Pull the plug kick a pug now block cast disconnects it's a nuva laya

Cirantille

I dont think it is consecutive blocks causing it though

I tried to spam it and it didnt kick me

I was thinking ok it doesnt happen

But when you press it fast it happens

:O

Is that because of this AC changes :O

Royaji

ZonasArch wrote: »

Royaji wrote: »

Dusk_Coven wrote: »

L2Pissue wrote: »

Yep it works
I just spammed block for 15 seconds to log out,
Thanks for this feature.

Then maybe don't go around spamming block for 15 seconds till your kicked?
If it turns out to be destabilizing the server and/or affecting the players around you, honestly a kick should be followed by a ban for deliberately sabotaging the game.

Stop shooting yourselves in the foot and asking ZOS for a bandaid.

So you are going to place the blame on the player who discovered a quite serious bug and made others aware of it and not the developer who has either failed to discover such a serious problem as part of the internal testing or considered it acceptable to release a patch with this problem despite being aware of it?

Spamming block for 15 seconds isn't a serious issue, it's a proof of concept. Nobody spams it like that anywhere.

The real issue is how does this connect to normal gameplay disconnections while blocking.

You guys need to learn how to make complaints so you don't sound like desperate fools. This is important! Don't be all "internety" about it. Be reasonable.

With any kind of software repeatedly using an intended function should never lead to a disconnect or any other problem. If there is a potential for the function to cause such a problem there should be a safeguard implemented to prevent the user from getting to the point where a problem would occur.

We have seen reports that the problem can happen after 15, 20 and in some cases even 10 seconds. It is completely reasonable to expect someone to initiate and stop blocking several times repeatedly over a short period of time in both PvE tanking and PvP in general. This does indeed have serious gameplay implications.

I'll go to the stables to get your magnificent steed ready now, m'lord.

typo

aiio

I'm just here to confirm as well. I had so many issues with these disconnects in the past few days, I even made a thread about it myself. Thank you so much for posting this, I would have never realised that this was the problem.

VaranisArano

ZonasArch wrote: »

Royaji wrote: »

Dusk_Coven wrote: »

L2Pissue wrote: »

Yep it works
I just spammed block for 15 seconds to log out,
Thanks for this feature.

Then maybe don't go around spamming block for 15 seconds till your kicked?
If it turns out to be destabilizing the server and/or affecting the players around you, honestly a kick should be followed by a ban for deliberately sabotaging the game.

Stop shooting yourselves in the foot and asking ZOS for a bandaid.

So you are going to place the blame on the player who discovered a quite serious bug and made others aware of it and not the developer who has either failed to discover such a serious problem as part of the internal testing or considered it acceptable to release a patch with this problem despite being aware of it?

Spamming block for 15 seconds isn't a serious issue, it's a proof of concept. Nobody spams it like that anywhere.

The real issue is how does this connect to normal gameplay disconnections while blocking.

You guys need to learn how to make complaints so you don't sound like desperate fools. This is important! Don't be all "internety" about it. Be reasonable.

I get this objection to some extent. I tested this while standing around in Craglorn and both times I had to spam block much faster than I usually would in combat before I disconnected. Not exactly a realistic combat situation for me, considering the only thing around to be "blocked" was a couple of sheep.

The trick is, as you say, connecting that behavior with the disconnects we see in BGs and trials. That's a lot harder for players to test correlation vs causation because there's an awful lot going on in a real combat situation besides just the blocking. Its impossible for us to rule out those extra factors.

Who can? ZOS.
My take is that its a valid concern that we've got a new problem that didn't exist before: rapidly spamming block boots players to the log-in screen. If nothing else, ZOS can affirm that it was intended, or if its not intended behavior, it would be wise for them to make sure it's not having other unintended consequences during actual combat situations where there's a lot more going on than just blocking.

Toanis

Yep. Confirmed

Arunei

Dusk_Coven wrote: »

Then maybe don't go around spamming block for 15 seconds till you're kicked?
If it turns out to be destabilizing the server and/or affecting the players around you, honestly a kick should be followed by a ban for deliberately sabotaging the game.

Stop shooting yourselves in the foot and asking ZOS for a bandaid.

You do realize this is called "being able to replicate a bug", right? You understand the concept of bringing something like this to light so other people can test the validity of it and see if they can get it to happen as well? OP isn't telling people to go around doing it to purposefully "destabilize" the game, they're telling people to try it and see if it affects them too. Also I don't even know why you would think blocking causes an issue like that anyway, and there are plenty of people who like to spam block or bashing just to goof off (me and a lot of my friends being among them). We don't do it because we have malicious intent, we're just doing it because it's fun.

Claiming that spamming block is causing server destabilization and people shouldn't spam it is like people who jump everywhere suddenly finding that doing so kicks them to log in, but telling them that "hey you're destabilizing the server so stop doing it". It's equally silly when you consider you have no idea what's actually causing this to happen, so telling people not to do it because of what you think the problem is could actually hinder ZOS finding out what's causing it. Being able to replicate a bug reliably is one of the fastest ways of fixing it.

Edited for typo.

MajBludd

Just tried the block spam and I didnt not crash. Not to discount anyone who has, just fyi.

I have crashed several times, all week though, during various actions, i.e., porting, riding to a keep, a big fight, small fight, etc.

ZonasArch

VaranisArano wrote: »

ZonasArch wrote: »

Royaji wrote: »

Dusk_Coven wrote: »

L2Pissue wrote: »

Yep it works
I just spammed block for 15 seconds to log out,
Thanks for this feature.

Then maybe don't go around spamming block for 15 seconds till your kicked?
If it turns out to be destabilizing the server and/or affecting the players around you, honestly a kick should be followed by a ban for deliberately sabotaging the game.

Stop shooting yourselves in the foot and asking ZOS for a bandaid.

So you are going to place the blame on the player who discovered a quite serious bug and made others aware of it and not the developer who has either failed to discover such a serious problem as part of the internal testing or considered it acceptable to release a patch with this problem despite being aware of it?

Spamming block for 15 seconds isn't a serious issue, it's a proof of concept. Nobody spams it like that anywhere.

The real issue is how does this connect to normal gameplay disconnections while blocking.

You guys need to learn how to make complaints so you don't sound like desperate fools. This is important! Don't be all "internety" about it. Be reasonable.

I get this objection to some extent. I tested this while standing around in Craglorn and both times I had to spam block much faster than I usually would in combat before I disconnected. Not exactly a realistic combat situation for me, considering the only thing around to be "blocked" was a couple of sheep.

The trick is, as you say, connecting that behavior with the disconnects we see in BGs and trials. That's a lot harder for players to test correlation vs causation because there's an awful lot going on in a real combat situation besides just the blocking. Its impossible for us to rule out those extra factors.

Who can? ZOS.
My take is that its a valid concern that we've got a new problem that didn't exist before: rapidly spamming block boots players to the log-in screen. If nothing else, ZOS can affirm that it was intended, or if its not intended behavior, it would be wise for them to make sure it's not having other unintended consequences during actual combat situations where there's a lot more going on than just blocking.

Like you said, you test things, even if extreme scenarios, and report results. Whining about it won't help, and that's the point. When you flood forums with "yeah, I wanna spam block and not get kicked" you're not helping because whoever Dev reads it knows that's not an actual behavior people have while playing regularly. This creates a lot of noise for them to comb through to figure out what they can, but we can't.

I mean, who spams block that fast that long? Nobody. So OP reported it, and that's awesome!, but to jump from that to "yeah, I wanna be able to be super block spammy even if I'll absolutely never ever do that ever in my life"... That's unreasonable. That's complaining for the sake of complaining.

And let's face it... Nobody cares about the complaints pushed by whiny people. It's like the kid with the wolf. There's no credibility, no good will, he's now just an annoyance and will be readily ignored.

That's why I say "be reasonable" on complaints. You wanna do like OP and not like the bandwagon that so many jumped on after OP.

Moonsorrow

This Harrowstorm "performance" Update is such a mess. Performance and combat stability is the worst i`ve seen. Crashes ALL the time, bugs on bugs, Block issues, skill targeting/triggering/travel time/animation issues.

I crash like 5-10 times randomly in Cyrodiil in ONE hour. So cannot play there. Random crashes at PVE land too. Least amount of crashes at IC, but.. yes it does crash there also.

Last night i crashed in middle of a boss fight (was doing farming run at IC, killing random players too on the way), was so nice feeling to try to hurry back in the game after the crash, but obviously starting the game and the 2 loadscreens before back at IC.. i loaded into a dead character with 20k Tel Var lost (lucky i had earlier banked most), the boss had crash-killed me, obviously since when you crash your character still stands there in the game doing nothing for a while, and you as the player are watching the ESO Crash Report page at Desktop and type the obligatory "FUUUUUUUUUUUUUUUU..." in the report to describe your feelings.

Was so furious.

Cannot play anywhere without huge problems. Game just is not working reliably right now, skills & block not work reliably. No wonder Cyro Campaigns are half empty most times, not that many pvper wanna play this CRASHY mess right now.

Harrowstorm rating: 0/5 right now. New dungeons, especially Unhallowed Grave is cool and fun, but the disgusting performance and bad changes to mechanics on this "performance update" makes me wanna rage-uninstall the game - first time ever have that feeling. So it tells something. Fix your game. And/or stop doing performance updates if this is what we get.

Yours truly,

SALTSORROW

Shantu

Just part of the performance improvement plan

Sometimes this game feels like a Ferrari running on an antique Volkswagen engine.

L_Nici

I just tried it spammed over 30 seconds block and didn't got kicked, you really have amazing issues.

jadarock

ZonasArch wrote: »

VaranisArano wrote: »

ZonasArch wrote: »

Royaji wrote: »

Dusk_Coven wrote: »

L2Pissue wrote: »

Yep it works
I just spammed block for 15 seconds to log out,
Thanks for this feature.

Then maybe don't go around spamming block for 15 seconds till your kicked?
If it turns out to be destabilizing the server and/or affecting the players around you, honestly a kick should be followed by a ban for deliberately sabotaging the game.

Stop shooting yourselves in the foot and asking ZOS for a bandaid.

So you are going to place the blame on the player who discovered a quite serious bug and made others aware of it and not the developer who has either failed to discover such a serious problem as part of the internal testing or considered it acceptable to release a patch with this problem despite being aware of it?

Spamming block for 15 seconds isn't a serious issue, it's a proof of concept. Nobody spams it like that anywhere.

The real issue is how does this connect to normal gameplay disconnections while blocking.

You guys need to learn how to make complaints so you don't sound like desperate fools. This is important! Don't be all "internety" about it. Be reasonable.

I get this objection to some extent. I tested this while standing around in Craglorn and both times I had to spam block much faster than I usually would in combat before I disconnected. Not exactly a realistic combat situation for me, considering the only thing around to be "blocked" was a couple of sheep.

The trick is, as you say, connecting that behavior with the disconnects we see in BGs and trials. That's a lot harder for players to test correlation vs causation because there's an awful lot going on in a real combat situation besides just the blocking. Its impossible for us to rule out those extra factors.

Who can? ZOS.
My take is that its a valid concern that we've got a new problem that didn't exist before: rapidly spamming block boots players to the log-in screen. If nothing else, ZOS can affirm that it was intended, or if its not intended behavior, it would be wise for them to make sure it's not having other unintended consequences during actual combat situations where there's a lot more going on than just blocking.

Like you said, you test things, even if extreme scenarios, and report results. Whining about it won't help, and that's the point. When you flood forums with "yeah, I wanna spam block and not get kicked" you're not helping because whoever Dev reads it knows that's not an actual behavior people have while playing regularly. This creates a lot of noise for them to comb through to figure out what they can, but we can't.

I mean, who spams block that fast that long? Nobody. So OP reported it, and that's awesome!, but to jump from that to "yeah, I wanna be able to be super block spammy even if I'll absolutely never ever do that ever in my life"... That's unreasonable. That's complaining for the sake of complaining.

And let's face it... Nobody cares about the complaints pushed by whiny people. It's like the kid with the wolf. There's no credibility, no good will, he's now just an annoyance and will be readily ignored.

That's why I say "be reasonable" on complaints. You wanna do like OP and not like the bandwagon that so many jumped on after OP.

You want a reasonable complaint list ?
Read the 93826263 other threads!

*They are all reasonable considering the game isnt functioning properly

Claire

MajBludd wrote: »

Just tried the block spam and I didnt not crash. Not to discount anyone who has, just fyi.

I have crashed several times, all week though, during various actions, i.e., porting, riding to a keep, a big fight, small fight, etc.

It's not a crash with block spam, it's a disconnect. You'll be booted back to login screen.

Pauls

Final solution of permablocker builds problem

RD065

fred4 wrote: »

RD065 wrote: »

The only times I've crashed is going to homes but nothing in combat but tonight twice between Dolhman's. One time I was jumping around, the other I was standing still.

This thread isn't crashing, though. That's the other one. This thread is about a clean disconnect to login screen.

Sorry.

cyclonus11

I wonder if it also causes others around you to crash. Which would explain other random crashes and freezes.

Volckodav

+1 confirming it!

OMG after crashes and no stam recovery I thought nothing can be worst...

So we are now and one million of reason to NOT play the way we like, cool isn't it

ZonasArch

Claire wrote: »

MajBludd wrote: »

Just tried the block spam and I didnt not crash. Not to discount anyone who has, just fyi.

I have crashed several times, all week though, during various actions, i.e., porting, riding to a keep, a big fight, small fight, etc.

It's not a crash with block spam, it's a disconnect. You'll be booted back to login screen.

for the effects of poor satisfaction, aren't these basically the same?

DukeDiewalker

Just revert these block changes already! Nobody likes them, nobody wants them (except a few people who refuse to learn how the game actually works/is played).
They didn't really improve performance, HP desyncs are even worse than before... There really is no need to keep going at this point.

I'll spell it out for you: R - E - V - E -R - T
Thank you

D0PAMINE

@ZOS_BrianWheeler

Ysbriel

So now they are going after tanks....

Tigerseye

ykculnu wrote: »

Instead they rid animation canceling and other high skill features that brought people to this game for fluid and fast paced combat, in the name of "server load".

How is AC a "high skill feature", in your opinion.

What is so challenging about it?

Chi75

this is total *** from zos oO are they crazy

[Deleted User]

Hello everyone,

Recently we've had to remove a few posts for baiting and flaming, content that is against the Forum Rules. For further posts be sure to stay constructive and respectful to avoid thread derailment or action on one's own account.

Thank you for understanding.