And another block bug...

React

TechMaybeHic wrote: »

Can't wait for the entire game to be recoded. The track record is at an all time high

Well you'll be waiting a while! Here is a little copy pasta from another thread.

ZOS_GinaBruno wrote: »

One of our main priorities right now is upgrading the remaining server hardware which is still ongoing and on track - we'll have an update on the timeline before the end of the year. We have also been working on the re-architecture we originally mentioned earlier this year. It's worth noting this isn't a single item that will go into an individual update, but contains many smaller pieces that will be released over multiple updates starting next year.

Since this is the ONLY update we got in the 11 months the project has been underway, I can only assume that this statement means that they intend to finish replacing the servers hardware before implementing any "chunk" of this code rewrite. With the timeline for that being unclear, I am assuming the earliest we would see a chunk of this project roll out is Q2, but more likely Q3 2023. If I am correct about that, it means that the earliest the project would be completed would likely be in 2024, over a year after the initial completion date we were promised.

Carcamongus

Players when they found out about yet another block bug:



Seriously, though, I would like to know what's going on. The amount of mishaps, to put it mildly, we've been seeing is considerable. It's important to keep calm when faced by many obstacles, but there comes a time when acting as if everything were under control when it clearly isn't becomes detrimental. "We'll have to do better" could start with letting the people who support this game know why this year is being so turbulent. I don't think devs are incompetent or careless, but something is clearly out of place and it'd be far easier to understand their side if we actually got to see it.

So, my group that was starting vet Sunspire vanished because of U35, I very reluctantly helped a friend with vet Depths of Malalalatar because of U36's block bug and now I wouldn't risk a vet dungeon because of the new bug. I'm a tank and the game is making it very hard for me to do my job. These are legitimate reasons to be furious, but I'm concerned whatever's happening on the devs' side will continue into next year and put the future of the game I love at risk.

Jaimeh

Carcamongus wrote: »

"We'll have to do better" could start with letting the people who support this game know why this year is being so turbulent. I don't think devs are incompetent or careless, but something is clearly out of place and it'd be far easier to understand their side if we actually got to see it.

Better (and frank) communication would go a long way, but for ages we couldn't even get a definitive answer as to whether the promised Q&A was cancelled, which says a lot about their willingness to inform us in general. The thing is if the reason is having less resources because the studio is focusing on other projects, they wouldn't say that, because there's already 'game is dead' posts on the forums, they wouldn't want to further ignite that.

beer781993

I wonder which color the next guar will be

Lydawobbles

I think they took too many people off eso for their fancy “new AAA mmo” and we’re stuck with too big of a job for too few people to fix.
I am so sad.

TechMaybeHic

React wrote: »

TechMaybeHic wrote: »

Can't wait for the entire game to be recoded. The track record is at an all time high

Well you'll be waiting a while! Here is a little copy pasta from another thread.

ZOS_GinaBruno wrote: »

One of our main priorities right now is upgrading the remaining server hardware which is still ongoing and on track - we'll have an update on the timeline before the end of the year. We have also been working on the re-architecture we originally mentioned earlier this year. It's worth noting this isn't a single item that will go into an individual update, but contains many smaller pieces that will be released over multiple updates starting next year.

Since this is the ONLY update we got in the 11 months the project has been underway, I can only assume that this statement means that they intend to finish replacing the servers hardware before implementing any "chunk" of this code rewrite. With the timeline for that being unclear, I am assuming the earliest we would see a chunk of this project roll out is Q2, but more likely Q3 2023. If I am correct about that, it means that the earliest the project would be completed would likely be in 2024, over a year after the initial completion date we were promised.

Yeah, game might be better off the less they mess with code is what I'm saying. Might be in luck because if they keep breaking combat with these patches we'd think should be routine; everyone that cares about combat performance will be long gone before they are done

UntilValhalla13

So, I'm guessing the patch in a few days will do nothing for us console folks? Our DB prob has been cancelled for like a month now because of this. I guess I'll be playing FF14 even longer...

danthemann5

So when will this be fixed? January? July? Next December?

Anyone listening (lol)?

The very real and totally in-progress recode is going to be awesome!

Lixen

This issue seems related to sheath weapon and can occur in any zone. I have tried all the trials and few base game and dlc zones, all same results.

Step to reproduce: have weapon sheathed, press light attack and immediately after press bar swap (same speed as light attack skill weaving or faster works). block will be bugged and cannot be fixed without zoning (porting within the zone or reloading ui doesn't fix it)

@ZOS_GinaBruno steps to reproduce

Andeh_s

FIX

As others have mentioned, this has been an issue on console since the Firesong launch.

Other than changing instance, the block bug can also be fixed by mounting, sprinting on your mount and whilst STILL SPRINTING, hit light attack. Your character will dismount and you will be able to block again.

Csleia

danthemann5 wrote: »

So when will this be fixed? January? July? Next December?

Anyone listening (lol)?

The very real and totally in-progress recode is going to be awesome!

it will be fixed when rich stops apologizing and does his job

Lydawobbles

Andeh_s wrote: »

FIX

As others have mentioned, this has been an issue on console since the Firesong launch.

Other than changing instance, the block bug can also be fixed by mounting, sprinting on your mount and whilst STILL SPRINTING, hit light attack. Your character will dismount and you will be able to block again.

Too bad you can’t mount in trials and dungeons, where most people are having the issues.

TechMaybeHic

Csleia wrote: »

danthemann5 wrote: »

So when will this be fixed? January? July? Next December?

Anyone listening (lol)?

The very real and totally in-progress recode is going to be awesome!

it will be fixed when rich stops apologizing and does his job

Well clearly this is a case of you can't please everyone. Some people like the block bug. Some don't

/Snark

Andeh_s

Lydawobbles wrote: »

Andeh_s wrote: »

FIX

As others have mentioned, this has been an issue on console since the Firesong launch.

Other than changing instance, the block bug can also be fixed by mounting, sprinting on your mount and whilst STILL SPRINTING, hit light attack. Your character will dismount and you will be able to block again.

Too bad you can’t mount in trials and dungeons, where most people are having the issues.

Very true! However it is a handy fix for Cyrodiil rather than zoning out/in. I've been getting this bug at least once an hour in PvP since the DLC launch

Lydawobbles

Not awesome that you’re getting the bug so often, but “awesome” that it fixes for you 🤗

LyricsEcho

This is beyond ridiculous. Quality assurance could have easily caught this current bug and im absolutely sure you guys knew about it before the "fix" rolled out.

Paralyse

This bug is pervasive enough, severe enough, and has such a negative effect on many areas of core gameplay that it merits an immediate and full commitment of dev resources to get it fixed ASAP.

In other words, this issue should far and away be the #1 priority of anyone working on ESO currently. Even if that means we have to have the servers come down for awhile to apply a hotfix.

I do not understand why ZOS does not seem to be taking this as seriously as the rest of us are, and why they do not seem to be committing ALL of their dev team resources to fix the issue. The game lately is in a state where continuing to make players want to quit is not a good strategy.

Csleia

beer781993 wrote: »

I wonder which color the next guar will be

The red, green and blue use 8 bits each, which have integer values from 0 to 255. This makes 256*256*256=16777216 possible colors.

React

Andeh_s wrote: »

FIX

As others have mentioned, this has been an issue on console since the Firesong launch.

Other than changing instance, the block bug can also be fixed by mounting, sprinting on your mount and whilst STILL SPRINTING, hit light attack. Your character will dismount and you will be able to block again.

This would be great...

if I could exit combat while in cyrodiil.

imaslowlearner

Y'all need to stop complaining about the new block feature and adapt to the new meta.

FluffyReachWitch

Lixen wrote: »

Step to reproduce: have weapon sheathed, press light attack and immediately after press bar swap (same speed as light attack skill weaving or faster works). block will be bugged and cannot be fixed without zoning (porting within the zone or reloading ui doesn't fix it)

Just tried this myself and reproduced it in one attempt. Showed my partner and they were able to reproduce it in one attempt as well.

React

https://streamable.com/1bky3k

Here is the bug demonstrated with an input overlay, using controller on PC NA. I also demonstrate the workaround @Andeh_s shared.

To replicate: Sheathe your weapon. With weapons away, press light attack -> barswap immediately after. Your block will no longer activate at all.

Workaround: Mount up. Press sprint. While sprinting, press light attack. You'll be dismounted and you will be able to block again.

@ZOS_GinaBruno

beer781993

I mean don't they see that all this mistakes and bad communication hurt the reputation of their company?
Even if they get their new project done faster, many will not pre purchase or even buy it. At least I will never buy another Zeni game. Can't go through that again.

Lixen

beer781993 wrote: »

I mean don't they see that all this mistakes and bad communication hurt the reputation of their company?
Even if they get their new project done faster, many will not pre purchase or even buy it. At least I will never buy another Zeni game. Can't go through that again.

They see it, and they know, that's why their QA department is unionizing not get axed, MS might catch up soon.

PurpleScroll

React wrote: »

Workaround: Mount up. Press sprint. While sprinting, press light attack. You'll be dismounted and you will be able to block again.

Can confirm that this works, nice find!

SkaraMinoc

For anyone who isn't aware, you can unsheathe your weapon by tapping block once. It's instant (< 100ms) and this is the recommended way to unsheathe in PvP so the animation doesn't lock your skills for a full second.

tap block > light attack > bar swap (block not bugged)

virtus753

React wrote: »

https://streamable.com/1bky3k

Here is the bug demonstrated with an input overlay, using controller on PC NA. I also demonstrate the workaround @Andeh_s shared.

To replicate: Sheathe your weapon. With weapons away, press light attack -> barswap immediately after. Your block will no longer activate at all.

Workaround: Mount up. Press sprint. While sprinting, press light attack. You'll be dismounted and you will be able to block again.

@ZOS_GinaBruno

Is there a workaround for a trial setting or other situation where ZOS doesn't allow us to mount?

VampiricByNature

Console player here [ps5]. It typically happens to one [or more] of us each vBRP run. We had just started to think about unchained, so we have been doing a few runs each weekend.

Our prog teams often experience it for trials too. We have become accustomed to waiting for players to travel out of the trial and back in. It has been a real nightmare for tanking this patch.

gameswithaspoon

ZOS_GinaBruno wrote: »

Thanks for sending this over! Could you try enabling the in-game Scrolling Combat Text to confirm if you are seeing any blocked damage or not? Just trying to eliminate the possibility of this being an animation issue.

Encountered this block bug in Cyrodiil this evening. Could not see blocked damage or block knockdown effect of NPC heavy attacks. Also could not dismount from my horse by holding block, though I could using a heavy attack. The block bug went away when I zoned into a delve, and did not return when I left the delve again for Cyrodiil.

M0ntie

This is appalling. It’s probably put the last nail in the coffin of my favourite raid team, which is one of a depleted number after update 35.