ZOS_GinaBruno wrote: »Hi everyone, just confirming we are aware of this issue. We've been working on getting it fixed, but weren't able to fully fix it before today's patch. Once a fix is complete and tested, we'll plan to roll it out into an incremental patch.
ZOS_GinaBruno wrote: »Hi everyone, just confirming we are aware of this issue. We've been working on getting it fixed, but weren't able to fully fix it before today's patch. Once a fix is complete and tested, we'll plan to roll it out into an incremental patch.
Sanguinor2 wrote: »Izanagi.Xiiib16_ESO wrote: »@ZOS_GinaBruno Will this issue be resolved by today's update?
The word block doesnt even appear in the patch notes.
ZOS_GinaBruno wrote: »Hi everyone, just confirming we are aware of this issue. We've been working on getting it fixed, but weren't able to fully fix it before today's patch. Once a fix is complete and tested, we'll plan to roll it out into an incremental patch.
How was this even allowed to happen, though? There were so many bugs reported during the PTS that you guys straight up ignored, which then went live with the harrowstorm launch. What is the point of having a PTS?
You shouldn't have touched the blocking system until you had a polished rework available for testing, and when you put it out for testing you should have actually acknowledged the feedback and made adjustments based on that. Now we're going to be stuck with a broken base combat system which will be compounded by how bad overall performance STILL IS during the "performance" focused patch, and it is going to make a lot of people leave the game. I mean if it seemed hopeless before that the developers might be able to improve performance and fix the game, this patch has just hammered that point home.
ZOS_GinaBruno wrote: »Hi everyone, just confirming we are aware of this issue. We've been working on getting it fixed, but weren't able to fully fix it before today's patch. Once a fix is complete and tested, we'll plan to roll it out into an incremental patch.
/script JumpToHouse("@Paramedicus")↑↑↑ Feel free to visit my house if you need to use Transmute Station or vet Trial Dummy with buffs and Aetherial Well (look for the Harrowing Reaper on the northern rock wall) ↑↑↑
JumpmanLane wrote: »Oh, god just revert the changes to block. THAT isnt fixing performance. Geeze
. I'm getting a refund for Greymoor and I'm just gonna play something else. It's just not fun anymore.
JumpmanLane wrote: »Oh, god just revert the changes to block. THAT isnt fixing performance. Geeze
. I'm getting a refund for Greymoor and I'm just gonna play something else. It's just not fun anymore.
I guess block casting will also trigger this, spamming bash is also legit especially if you have lag who i assume also trigger the risk.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.
Mojomonkeyman wrote: »@ZOS_GinaBruno
The issue is still making me crash to login screen almost every single bg match or dungeon I play, it even happens when block cancelling with sprinting or barswapping rapidly in pve overland - several times an hour. I dont know what to do anymore, it's impossible to play that way. Several tickets have been sent.
It's been almost 3 weeks since you broke what was working, can we get an update on when your fix is coming? I can't justify spending subscription on a game that is not working and 3 weeks is a damn long time.
Mojomonkeyman wrote: »@ZOS_GinaBruno
The issue is still making me crash to login screen almost every single bg match or dungeon I play, it even happens when block cancelling with sprinting or barswapping rapidly in pve overland - several times an hour. I dont know what to do anymore, it's impossible to play that way. Several tickets have been sent.
It's been almost 3 weeks since you broke what was working, can we get an update on when your fix is coming? I can't justify spending subscription on a game that is not working and 3 weeks is a damn long time.
Have you tried disabling some of your addons? I was getting disconnected on 6 out of 7 pvp characters in bg's untill I disabled Bandit UI.
LadyDestiny wrote: »Just great. Let's hope it doesn't take till next year to fix this.
ZOS_GinaBruno wrote: »LadyDestiny wrote: »Just great. Let's hope it doesn't take till next year to fix this.
Nope, we have a fix included with the next PC incremental patch.
ZOS_GinaBruno wrote: »LadyDestiny wrote: »Just great. Let's hope it doesn't take till next year to fix this.
Nope, we have a fix included with the next PC incremental patch.
When is that, BTW?
ZOS_GinaBruno wrote: »ZOS_GinaBruno wrote: »LadyDestiny wrote: »Just great. Let's hope it doesn't take till next year to fix this.
Nope, we have a fix included with the next PC incremental patch.
When is that, BTW?
It is likely going to be on Monday, but we're still getting everything planned out.