Original Post — Direct link
There appears to be a new bug with the Blackwood chapter.

When blocking attacks it drains a lot more Stamina than intended often double my block cost listed on my Advanced Stats page - it appears that anything that reduces block cost is potentially not working such as Sturdy Gear or CP.

This is a huge issue for Tanks in difficult content - especially newer/inexperienced Tank who block more regularly as your Stamina is gone after using Pierce Armor and blocking a couple of hits.

**Update**
This is only a small part of the issue.
The bigger problem appear to be when you block a hit you'll lose your regular amount of Stamina (Lets say 600 Stamina) and then when you drop block you lose the full cost of your block again (So about 1300 Stamina) so in total it can cost almost 2k Stamina to block 1 attack.

Current Block Issues:
1. You get charged nothing for blocking and when you drop block you lose all the Stamina you should have lost from blocking.
2. When you block 1 attack it ticks twice.
3. Block costs ignores your reductions such as Sturdy/Passives/CP and charges you the full amount.
4. Combinations of all of the above and probably more bugs.

**Update 2**
ZOS_JessicaFolsom;c-7281902

Hi everyone,

We got confirmation this morning that a fix for the block cost issue reported in this thread will be going into the next PC/Mac and Stadia incremental patch (on June 14.)



**Update 3**
ZOS_GinaBruno;c-7283383

As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.



https://youtu.be/TsshjjeaWcI

Thanks,
-Lee
over 3 years ago - ZOS_Adrikoth - Direct link
Hey folks,

We appreciate all of your reports and we wanted to let you know that we are investigating this issue.
over 3 years ago - ZOS_JessicaFolsom - Direct link
Hi everyone,

We got confirmation this morning that a fix for the block cost issue reported in this thread will be going into the next PC/Mac and Stadia incremental patch (on June 14.)
over 3 years ago - ZOS_GinaBruno - Direct link
Dabulousness;c-7282223

When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?



As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.
over 3 years ago - ZOS_GinaBruno - Direct link
Texecutioner187;c-7283395

ZOS_GinaBruno;c-7283383

Dabulousness;c-7282223

When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?



As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.



Thank you. When is that incremental scheduled?



We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.
over 3 years ago - ZOS_JessicaFolsom - Direct link
BlakMarket;c-7282364

Honestly this is crazy I changed two toons from nord to imperial because of sustain issues, to realize it was a BUG!!!!!!!! Who would I speak to, to get a refund of race change tokens.



Hey @BlakMarket our Support team should be able to help you out with this. I'm checking on what ticket category they'd recommend you use. Are you also looking to switch your characters back to their original races?
over 3 years ago - ZOS_GinaBruno - Direct link
MurderMostFoul;c-7283597

ZOS_GinaBruno;c-7283445

Texecutioner187;c-7283395

ZOS_GinaBruno;c-7283383

Dabulousness;c-7282223

When is console getting the fix? Are we going to need to wait even longer than the 14th or will you be squeezing it into the console chapter release?



As we only just fixed this internally for the upcoming PC incremental, it will not be fixed in time for console launch in a few hours. We're planning to include the fix in the first console incremental patch.



Thank you. When is that incremental scheduled?



We don't have a date scheduled yet, but it typically tends to be a few weeks after launch.



Here's to hoping the range bug, the set bonus bug, the companion item lost bug, and any other new bugs I'm forgetting are all included in this incremental as well



The range bug and set bonus bug should also be fixed in the first incremental. The Companion item loss bug was actually able to be hotfixed with launch so that shouldn't be an issue.