I'm wondering if the QA department fails to catch some bugs not because they're doing their job poorly, but because they're doing it on the in-house test server. It's nothing like live megaservers or even PTS, it operates under virtually no stress compared to the live environment. I'm saying this because I've seen some Korean games which featured timed and rhythmic mechanics that worked well on Korean servers but utterly failed when these games were published on global servers, due to both much larger population and longer/more variable latencies. Maybe ESO's combat is coded around the reality of internal servers and it fails on megaservers due to time-sensitivity of queuing action inputs.

ZOS_GinaBruno wrote: »

Hi everyone,

While we can confirm we have fixed the original issue with block, we identified the cause of this new blocking issue that went live with yesterday’s incremental patch. This issue most commonly occurs when attempting to swap weapons while weapons are being drawn or sheathed, preventing you from blocking again until zoning or relogging.

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; unfortunately, the fix for this issue does require another new client build and is not something we are able to hotfix. It will also be present after the console incremental patch on Wednesday.

We understand how frustrating this is for everyone, including us. We’ll let you know as soon as possible when to expect the fix but expect it to be on or around December 19.

It certainly wasn't my intention to spread "misinformation/conspiracy", so let me go ahead and provide the context for my previous claim.

The above quote from Gina suggests that the fix which released today was being "thoroughly tested". This does not appear to be true, because the exact same steps to reproduce the bug from this thread still work.

What exactly does "thoroughly testing" mean in zenimax terms?

My progs are dying.
My friends are leaving.

We gave you time. We accepted the guars. We tried to play nice, to watch our language, to emphasize with the people on the other side of the screen who likely could do very little to fix longstanding, well-known bugs.
We gave you your two weeks. We tried work arounds like testing block before each pull. We talked to each other to ensure all teams were aware of the progress of the bug and the best ways to adjust to a core game function being so supremely unreliable.

And now we find ourselves here with yet another block bug. The good news this time is that we maybe might be able to get out of it with bar swaps? This isn't a fix -- we should not be working around the team's lack of double checking before rolling something out. We should not be adjusting to your team's errors while also experiencing radio silence and snipped comments (on that note, the forums are for more than just the mods or various teams. It is where players can communicate to solve problems -- please let us do so without shutting things down. Since we have to play catch-up with workarounds and guars we didn't ask for, please let us have this one inconsequential thing).

U36 almost hurts worse than U35. U35, we knew that people would leave. The outcry was massive, the backlash swift, and the wallets cinched. But now it's like a slow motion papercut -- watching teammates leave because they've grown angry, disheartened, and turning to other valid options in a marketplace saturated with other games just waiting to be enjoyed (even if they are not MMORPG's).

But I am a sucker. And I will be here, yet again, waiting for a fix. At this point, this is now the fourth? fifth? attempt to fix this. Instead of spending your energy and time censoring a very unhappy playerbase, please just fix the bug. Just fix it.

Thank you. Happy holidays, if you celebrate them.

PingTheAwesome wrote: »

Instead of spending your energy and time censoring a very unhappy playerbase, please just fix the bug. Just fix it.

Thank you. Happy holidays, if you celebrate them.

The people censoring are not the devs, they are moderators of this forum.

RupertVandy wrote: »

tomofhyrule wrote: »

I'm wondering if the reason this seems so hard to fix is that everyone's looking in the wrong place. This might not be a block bug, it might be a barswap bug.

If they reverted block to pre-U36 state, then that means that this problem either isn't caused by block or this issue was extant before U36 dropped, but we just never noticed it. Granted, there aren't many points that people would unsheathe/barswap/light attack all at the same time in combat, and if barswapping reset it to its default state, then the only way we'd notice it is if we got caught by a meteor or something right after it landed (at which point everyone - including the logs - would say that the block just didn't come up in time).

Come to think about it, I have felt that barswap was a little clunky recently and more than once I've ended up on the wrong bar by accident even though I know I hit barswap.

But in the end, if this is just "Block Bug v2 but fixable by barswapping," that alone downgrades this from 'gamebreaking' to 'annoying,' so I'll take it. My progs are on hiatus for the holidays now anyway, but even with the last bug we got a nice win last night, and if we can just do that again but with people being able to fix themselves from block bug in the middle of a pull, that's great.

I do like the suggestion that incrementals be pushed to PTS though, and I would hope ZOS takes that into consideration. The PTS doesn't do much between patches, but if the incrementals went up there and people could test them, that might help to catch a lot of these issues earlier.

Without knowing the "spaghetti code" exactly, but knowing how client/server interactions work, this is my educated guess. There's essentially action queues stored in memory and time stamped. These resolve actions for combat and movement etc. They're also used to prevent the client from cheating and saying its doing such and such or has moved 100 steps in 0.5 sec. So the server must resolve this queue before anything meaningful (interaction with another entity) can occur. This also means that any screw up on the timestamps or status of an object/event/skill/BAR/shield etc can result in a situation along the lines of a status being set like "currently blocking" at the client level but the eso server recognizes no such status. What needs to likely happen is a periodic resolution step where the server and client verify their current states. Its likely a "weapon isnt out yet" or "character is mounted" state is being recognized by one and not transmitted to the other.

This makes sense.

In my (absolutely uninformed) opinion, addressing something like a periodic check that the server and client are in the same state may also fix other things, notably things like 'am I in combat or not?' for the perennial 'stuck in combat' bugs.

I haven't been playing as long as many people, but I have heard anecdotes that combat got a lot clunkier once several of the calculations were moves server-side. Could it be that we're ending up with a lot of desynch? If so, could a periodic 'resynch' call fix (or at least address) a lot of issues?

can confirm, crown store is working

I was able to verify block was still bugged within twenty seconds of logging in and testing.

I'm glad we waited two months for this "fix".

How many raiders will we lose before the next patch?

We raided for 2 hours today and nobody complained about block issues.

The repro that people are talking about today is a bit contrived--you generally don't sheathe your weapons in combat, and as people often cast skills to prebuff before combat, people generally don't start combat by light-attacking to unsheathe.

It's a scenario that I imagine most people will never run into in actual gameplay. And the only reason we're seeing it is because it was being used to reliably replicate the more serious form of the bug that is indeed gone after today.

It's fine. Try it in actual gameplay rather than a contrived set of repro steps; the bug that existed before today was legitimately bad since it could happen in actual combat from just bar swapping. The issue people are talking about today is nothing like that.

The current state of the block bug is mildly inconvenient at worst and can be remedied by bar swapping if you happen to get it. The sky is, in fact, not falling.

It can be frustrating that it is not completely fixed, but it is in a much better state after today's patch and should not prevent anyone from doing any content.

You can bar swap now to fix it. So the stuck in combat bug shouldnt prevent you from fixing the block bug in pvp, unless you are using oakensoul.

ZOS_GinaBruno wrote: »

We want to apologize because the patch note for today’s block fix wasn’t as clear as it should’ve been. While we did roll back code to make it so block is in a state from before Update 36 launched, we missed a known issue that should have been included in the patch notes.

As some of you have noted, your character can get into a temporary bad state by performing any action that cancels sheathe or wield animations; weapon swapping should resolve the issue. If you cancel the sheathe/wield animation multiple times, you will need to bar swap the same number of times to fix the issue. While we do know that this issue pre-dates Update 36, we are investigating whether any changes in Update 36 resulted in how frequently it can occur.

For next steps, this issue requires further investigation then we will have internal discussions about the plan. We’ll follow back up with everyone as soon as we have more information to share. Again, apologies for missing this critical piece of information in the patch notes for today’s fix.

@ZOS_GinaBruno: Weren't you JUST begging us for patience, and promising thorough testing after more than a month of this bug being present?

The issue here isn't that you "missed a critical piece of information in the patch notes for today's fix." It's that there is STILL a major, game-breaking bug around block, so your teams haven't really FIXED anything.

Do you think folks in PvP have time to futz around with whatever janky *** removes the bug temporarily while in the midst of already-laggy, under-performing combat? Do you think folks who wipe in PvE will be content knowing that they might not have wiped, had their tank bar swapped 1s earlier, preventing the one-shot that then wipes the raid?

ZOS is doing precious little to earn patience and understanding from their player base.

So I'm guessing the feature for Q4 next year will be a blocking skill line you can buy for crowns? At least then we would know it would work.