Dusk_Coven wrote: »Carespanker wrote: »Dusk_Coven wrote: »If you don't believe, spam block button yourself real fast for like 10-15 seconds and you will get kicked.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 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.
Ya know tanks do split-second blocks quite frequently in hard content right?...
If tanks are blocking legitimately and having crashes, that's one thing. But deliberately manufacturing an issue by spamming block until you get kicked... I don't feel that's ZOS's responsibility to fix.
If legitimate uses of block cause a problem, I'm sure the reports will make their way to ZOS. Standing around spamming block for 15 seconds to manufacture a problem is not legit.
Just because theyre not announcing this issue to the forum doesnt mean an urgent memo didnt go out to the relevant departments before the weekend.
JumpmanLane wrote: »If someone's wondering... this is not exclusive to spamming. Clicking it real fast is just the easiest way to replicate this bug. In PVP you may hold block for a second, drop it and then depending on the situation, hold it again for a second and drop it again and do that over and over again. Add in some block cancel animations in between and that's already enough to get booted.
Lol considering you have to dodge with block first on controller, this would explain a lot. Wtaf ZoS xD.
This AND considering you lightly tap block and the right trigger to break free quickly on controller might explain some people being unable to break free at times.
Quick blocks are not even registering sometimes. Block’s BROKEN and it’s affecting dodge and break free.
Just because theyre not announcing this issue to the forum doesnt mean an urgent memo didnt go out to the relevant departments before the weekend.
The point is it would be comforting to hear an acknowledgment of the issue and they are looking to fix it.
Something so simple can go a long way towards good faith.
Silence gives the impression that they don't care.
Twenty0zTsunami wrote: »report bugs through officially intended avenues; don't cry about them on the forums.
List of "exploits" * NEW for U25, all rewarded with a disconnect:-
- Blocking a lot
- Changing location
- Being in Cyrodiil for a bit
- Using a ladder in Imperial City / Sewers
- Using skills
- Typing in chat during the guild trader flip
- Trying to access your Guild Bank.
(All very naughty, you bad people).
Coming Soon! NEW exploits to be added with the next patch, all rewarded with a disconnect:-
- Typing in chat AT ANY TIME!
- Swapping your SKILL BAR!
- MOVING!
Good news though! All exploits will be linked to a timer. Your timer can be reset to zero if you make one purchase from the Crown Store every ten minutes!
*the word "exploit" newly redefined.
@Dusk_Coven
So you can quote my posts to try and make your argument seem legitimate, but you can't respond to them directly like you have been other people? Good to know. Also your little snippet from my post about people blocking rapidly in numerous situations did nothing to back up your argument, because it actually backs up the opposite; that there isn't very much room for this being intentional, because I'm sure the devs understand how people needing to block rapidly could very well happen. You say that the patch notes don't always include something the devs have introduced, and that might be true for things that aren't a basic gameplay mechanic that literally everyone who does content makes use of. This isn't some little niche thing we're talking about, it's a literal base mechanic. And you really think they wouldn't mention if they made something so integral to the game log you out like this?
Also, you're making a lot of assumptions about what people do or don't do just because they're saying something you don't agree with. You included part of my post and then claim "I suspect a lot of people use it or something close to it", but I hardly do PvE content in ESO these days outside of events or new dungeons for the story, and I PvP even less than that. So your little assumption that people are only making an argument against you because we want to be able to...exploit the game I guess, is way off. I even mentioned before that myself and my friends like to goof off with spamming bash at each other and just randomly blocking because we're messing around, which is something a lot of people do. It's not out of any malicious desire to mess up someone else's game (and you still haven't explained why you think something as simple as block spamming would affect someone else's game, other people have had to do that) or because we're trying to exploit something in any given context.
You seem to think that everyone doing this has it out for other players or something, that people want to do it to intentionally grief others and cause problems. Again, that's NOT the case at all. If, by some ungodly reason, this turns out to be intended, you won't hear people complaining because they've lost some precious means of trolling others. You'll hear them complaining because it will 100% affect legitimate game play. Can you take a few seconds to look at this from the perspective of people doing a vet trial or doing something like a vet no death run on harder dungeons, where they might be blocking/bashing a lot and just using normal game mechanics, only to find themselves abruptly crapped out of the game for something they were doing in the course of normal game play? I don't even do that kind of content and I can empathize with how that could affect people.
rager82b14_ESO wrote: »Maybe not spam block?
Now the server has to confirm to the client that blocking has stopped and desync caused this. These changes to block also assumed there are no desync issues but voila, they're getting exposed more visibly than ever now.Túrin_Vidsmidr wrote: »
Izanagi.Xiiib16_ESO wrote: »@ZOS_GinaBruno Will this issue be resolved by today's update?