And another block bug...

Thretion

I'm so EXCITED that the developers can't fix a non-working block for three months. Thank you, ZOS, for your hard and EXCITED work.

G0K4R

Wolfshade wrote: »

G0K4R wrote: »

Can confirm this, switching bars after getting the block bug now fixes it again.

I can confirm this. It took me 5 minutes to test it to find that the block still gets broken. Should this now be the fix, that swapping the bars will make you block again? In my opinion a bug is fixed when it didnt occurs anymore and make block possible after swapping is a kind of messy workaround while nothing is still fixxed.

Reading todays patch notes they said nothing about a workaround or temporary fix but stated they would have reverted block mechanics to pre update 36.

But that can't be true.

Also noone seems to have tested this at ZOS. And that's really sad. After all that happened recently...

danthemann5

ZOS_Kevin wrote: »

@React We are aware of the issue and investigating. Trying to get a bit more info before following up.

You've been aware of the issue and investigating for 7 weeks already. Is there an estimate of how much more time this investigation will take?

shaxigamingeb17_ESO

G0K4R wrote: »

Wolfshade wrote: »

G0K4R wrote: »

Can confirm this, switching bars after getting the block bug now fixes it again.

I can confirm this. It took me 5 minutes to test it to find that the block still gets broken. Should this now be the fix, that swapping the bars will make you block again? In my opinion a bug is fixed when it didnt occurs anymore and make block possible after swapping is a kind of messy workaround while nothing is still fixxed.

Reading todays patch notes they said nothing about a workaround or temporary fix but stated they would have reverted block mechanics to pre update 36.

But that can't be true.

Also noone seems to have tested this at ZOS. And that's really sad. After all that happened recently...

This is how a corporation tells you that they truly don't value you as a customer in the slightest

KilianDermoth

The funny thing is that the bug is stackable now.

int blockBugCounter = 0;

//some code

blockBugCounter++;

//some code

🤣

Parrot1986

At this stage surely it’d be better to put the “fixes” on PTS and have players test whether they work or not. Something clearly not working on the testing ZoS.

MajorProblem

React wrote: »

Since the other thread from today was closed just now..

@ZOS_GinaBruno @ZOS_Kevin

The block bug from the most recent live patch is still present. Is zenimax aware of this? Is there a further timeline for fixing this?

Who cares? They have been aware for two months now. It changes nothing.
The best about it is: it's a new iteration of the bug, not even just the same. They broke it AGAIN.

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

React

ZOS_Kevin wrote: »

@React We are aware of the issue and investigating. Trying to get a bit more info before following up.

Thanks for the information. The user @rpa made a good comment speculating about the causes in the other thread, which seems logical and is probably worth testing. I cannot quote it because @ZOS_Icy closed that thread, but I can copy + paste it below.

@rpa says "Any action that prevents client blocking terminating without allowing block again may or may not be a potential cause. Being mounted, sheathed weapon, bar swap, opening door, picking a lock, scrying or excavating, triggering a loadscreen and so on.

I have to say, it is very troublesome from my perspective that I was able to reproduce this bug within 10 seconds of signing in using publicly available steps that have been here on the forums for over a month.

How is it possible that QA didn't catch this?

G0K4R

Hmm, got me thinking:

After all, if Q3/2023 will look like this I'd probably rather prefer the usual update cycle and play two new dungeons with a roll dodge tank build

Wolfshade

"Rolled back some code that was preventing you from blocking, most commonly occurring when attempting to swap weapons while weapons were being drawn or sheathed. This change will bring Block back into the state it was in prior to Update 36 launching."

I got it. Now it looks like, that the bug didnt has to do anything with the newer code they wrote and placed in u36. When it got replaced with the old code today and the bug still occurs. End of the day, it isnt fixed jet, but the newer coder seems not to be the problem.

Jaraal

G0K4R wrote: »

Hmm, got me thinking:

After all, if Q3/2023 will look like this I'd probably rather prefer the usual update cycle and play two new dungeons with a roll dodge tank build

Makes one wonder how many bugs will actually get fixed in three months at this rate, doesn't it?

SaintJohnHM

ZOS_Kevin wrote: »

@React We are aware of the issue and investigating. Trying to get a bit more info before following up.

You've had almost two months "to get a bit more info". I don't think more information is going to solve these continued failures.

TechMaybeHic

I imagine if you are making a video game for something like baseball; you'd want to be able to do basic things like swing a bat or else the game might as well be disabled until it's fixed. If you just can't design your uniform; probably would just let it go live until a fix makes it.

By that logic, I think we can only surmise that combat is not the game anymore. A slot machine with a virtual world to show off your winnings is the game. It's been a zinger for years that PvP is just a tacked on mini game; but it appears all combat parts of the game are just a mini game to show off your crown store winnings

FrankonPC

I don't know about anyone else, but it's becoming more uninspiring by the week that the re-architecture will go as planned. If they can't fix block within two months, what happens when you redo 27 million lines of code.

RupertVandy

Its become a fantasy Sims competitor. Soon combat will be just a minigame and all classes and skills will be homogenized down to "press E to progress"

anvilbert

I have made a habit of resting block after every skill use or bar swap while tanking , this still isn't a 100% cure. Butt damn this is getting ridiculous. ZOS you need to fix your [snip]. Would anyone use a financial institution that had this many software problems???

[edited for profanity bypass]

danthemann5

FrankonPC wrote: »

I don't know about anyone else, but it's becoming more uninspiring by the week that the re-architecture will go as planned. If they can't fix block within two months, what happens when you redo 27 million lines of code.

Ah yes, the totally really real and 100% going to happen code rewrite. Or is it server re-architecture? Or multithreading? The one with no progress updates for almost a year? That one?

React

FrankonPC wrote: »

I don't know about anyone else, but it's becoming more uninspiring by the week that the re-architecture will go as planned. If they can't fix block within two months, what happens when you redo 27 million lines of code.

Yeah, my hopes were already severely diminished after the u36 launch coupled with the November 17th update, but the ongoing context of this block bug has fully convinced me that the code rewrite is a pipe dream.

[snip]
[edited for bashing & conspiracy theory/misinformation]

Aka_

Made this a few weeks ago. This is sincerely one of the poorest series of bugs and "fixes" I've witnessed. What little trust was left is just gone. Best of luck to the devs, you guys need it.

DemonicGoat

As soon as I saw the note that it was another revert of sorts I knew they did no QC/QA. This just screams "Maintenance mode" to me and given what Matts letter boils down to I have no reason to think otherwise.

FrankonPC

danthemann5 wrote: »

FrankonPC wrote: »

I don't know about anyone else, but it's becoming more uninspiring by the week that the re-architecture will go as planned. If they can't fix block within two months, what happens when you redo 27 million lines of code.

Ah yes, the totally really real and 100% going to happen code rewrite. Or is it server re-architecture? Or multithreading? The one with no progress updates for almost a year? That one?

Very good point. I should have been more specific lol

FrankonPC

React wrote: »

FrankonPC wrote: »

I don't know about anyone else, but it's becoming more uninspiring by the week that the re-architecture will go as planned. If they can't fix block within two months, what happens when you redo 27 million lines of code.

Yeah, my hopes were already severely diminished after the u36 launch coupled with the November 17th update, but the ongoing context of this block bug has fully convinced me that the code rewrite is a pipe dream.

[snip]

Exactly. I try not to be doom and gloom but it was an already big task that looks impossible after this latest DLC. A whole DLC without a core combat mechanic working properly.

[edited to remove quote]

hurry143

Like a lot of other people. the first thing I did when the servers came back up was to log in and check to see if blocking was finally fixed. Yes, I was hugely disappointed to find that block can still be broken using the same steps as before, albeit not as badly as before.

This change will bring Block back into the state it was in prior to Update 36 launching.

Something about this statement bugs me...

Is it implying that the bug we're seeing now had always been around, and it's just getting noticed a lot more now?

If this is the case, then I would've respected something in the patch notes along the lines of: "Hey, we reverted the recent code changes that broke block, but there's still something fishy going on. Let us look into that more!" At least that would prove that they're trying to be transparent, rather than hoping that none of the players would notice that something's still wrong with blocking.

On the other hand, if the devs really did think that this patch was going to make block 100% A-okay...

I honestly don't know which would be worse

BlakMarket

I'm actually done. This being my main game ends now.

Every part of content I enjoy has been effected by this bug. Block has/will be it seems bugged FOR MY ENTIRE 8 WEEK BREAK.

WHAT HAVE YOU DONE TO THE GAME???????????????????????????????????????????????????

I"m at point where I feel embarrassed that I haven't left sooner.

TechMaybeHic

BlakMarket wrote: »

I'm actually done. This being my main game ends now.

Every part of content I enjoy has been effected by this bug. Block has/will be it seems bugged FOR MY ENTIRE 8 WEEK BREAK.

WHAT HAVE YOU DONE TO THE GAME???????????????????????????????????????????????????

I"m at point where I feel embarrassed that I haven't left sooner.

I've been teetering on embarrassment after saying "if this year of performance doesn't help, I'm done" and yet here I am wanting to say it again.

I think I've moved from embarrassment to extreme shame in being an enabler

Chef42

It is interesting to note that ZOS never said they actually fixed it. If you read Directors letter, published on the 12th (after the deadline for the patch to be submitted for certification) it clearly stated that "we are still chasing down issues with blocking in combat." So they knew then that this patch would not fix it.

So I'm not really surprised there has been no real comment. Why would they when they never said it was fixed to begin with.

Einar_Hrafnarsson

I simply can not believe this. So glad my partner and i cut eso+

Jack-0

[snip]

How on earth do you manage to keep breaking block for such a long and continuous period of time? When will it actually get fixed, for real? What measures are you going to take to ensure this sort of gameplay-critical bug does not make it to the live servers in future? Do you even bother testing these supposed fixes? [snip]

I am so, so disappointed, and unmotivated to keep playing. 'Trust us' lol, yeah right, like any of us will ever trust you again.

[edited for bashing]

BlakMarket

TechMaybeHic wrote: »

BlakMarket wrote: »

I'm actually done. This being my main game ends now.

Every part of content I enjoy has been effected by this bug. Block has/will be it seems bugged FOR MY ENTIRE 8 WEEK BREAK.

WHAT HAVE YOU DONE TO THE GAME???????????????????????????????????????????????????

I"m at point where I feel embarrassed that I haven't left sooner.

I've been teetering on embarrassment after saying "if this year of performance doesn't help, I'm done" and yet here I am wanting to say it again.

I think I've moved from embarrassment to extreme shame in being an enabler

The epitome of sunk-cost fallacy. No wonder this video has nearly 50k views.

https://www.youtube.com/watch?v=-ZO7QTqSktw

One comment really resonated with me "I was obsessed with this game- every aspect of it- for so many years, and these last few patches just broke me. The magic is gone and I don't feel that same pull anymore."

The magic has gone, I need to stop lying to myself.

MajorProblem

ZOS_GinaBruno wrote: »

[...]
We are working on a fix now and want to take some time to thoroughly test over the next couple days to ensure things are stable;
[...]

Whatever they had promised you, it must feel like a shot in the back now.