I'm also waiting for an update on this

Did vCR0 again. Only had three block bug deaths this week during the Z'maja fight. Had a few with the minis, though. I wish someone from ZOS other than ICY was reading my posts. Would be really nice if, when working through hard content, I did not get killed by bugs in the game I want badly to enjoy playing.

We have the same problems with the block bug. Not just in Vcr but all raids. Have many Video proofs of my char being obviously in block, but I still get one shot by a heavy. Also, heals do not respond many times. No matter how much I heal my self or the healers try, my bar doesnt go up and I die at the end. Yesterday was the worst when even all my attacks turned dark and I coudnt press anything despite my spot. This game is full of bugs right now, no one seems to care about, that makes tanking hell. Tanking is no fun anymore, and I really consider canceling my subscription and leaving my raid group and this game for good. @ZOS_GinaBruno

Just mentioning this still occurs exactly as it has since last year (or longer)

Just a note to remind/clarify; if it is not an instant then it does NOT show the issue. Even arcanist flail with a 0.3 cast time does not show the issue.

@madman65 Sadly the issue in this post is independent of any lag conditions, so your issue is unrelated.

This issue is a bug, in which block will never be active unless you release and re-apply block. If you right-click-cast as if you were attack weaving, then immediately after casting the 'instant' skill you right-click and HOLD (to block, obviously) that block will not be applied. You can hold block 'forever' (my longest was in vDSR twins - I think there is a video above - holding block but /not/ blocking while the AOEs spawned at my feet... the healer kept me alive am amazingly long time). In general it doesn't last so long because a one-shot mechanic will have killed me (which is, of course, the problem).

When one is holding block (and there are no game mechanics which would prevent blocking), then block should be active. Unfortunately that's just not the case for this input sequence.

A quick capture of the same issue from PTS... no addon, but we can still clearly see the block button held on the mouse overlay and no block active on the character.

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

It would be cool to get any statement on this

it's good to try, but to be honest, I don't have much hope. I don't think they just "lose" active threads, and you are giving them all the info they could possibly need to see that this issue is not resolved.
So.. I have to guess that they just don't care enough about this, or about the players who encounter this bug.

Standard update... unsurprisingly, with no fix attempted so far, the problem continues to occur as written..

@ZOS_Kevin over a year has passed. Still an issue. any word?

I played with this a bit more today. I wonder if the issue is related to the very short period in a double-right mouse button click where the game knows the button is pressed, but it also has NOT applied block.

I'm not sure if my musing about the cause or trying to tease out additional data has any value. I find this issue particularly annoying because I feel like I could fix it with a couple days effort (assuming the existing incorrect behaviour is not actually preventing worse behaviour).

@ZOS_Kevin am I wasting my time here? It's been like 14 months since I made the forum post (and longer since my first in game report).

In this case, it's not desync, lag, etc: you can hold block all day and it will never attempt to block. You must release and reblock. Standard desync should also not be 100% reproducible: this is. It could be considered a kind of desync, but an utterly avoidable kind.. the 'oops we never bothered to send the state request' kind... which I would be grumpy about showing up in my task box as a 'desync'

I would say it could be the second, but I am suspicious, since:
* the game is aware the mouse button is held.
* I can 100% repro the issue for any instant cast. Any simple 'huh, that button press did not take' would not have such a reliable timing window. This issue is /highly/ predictable and reproducible; if you can make other button presses into 100% repro cases, then this may indeed represent a full class of issues. I /suspect/ it is specific to block, since block is 'pretty special' from a state machine rules processing point of view.
* The issue seemingly cannot be reproduced when using a skill with a cast duration, though my input timing is essentially identical (as I said, I can repro this thing 100% when trying, so I am pretty confident on this part, though the timing window may have simply shifted).
* I am (personally) unable to reproduce the issue without any skillcast in between releasing and attempting to reapply block (however another player, video shown earlier in the thread, was able to make it happen by just 'feathering' block).

Being hit through block is another bug, and also really sucks and also needs to be fixed badly - that's not what I have in my video footage, unfortunately. If I ever catch it, I will perhaps post video in another thread... assuming I ever get indication that providing exhaustive detail and footage for a bug is actually appreciated or remotely useful to ZOS - so far, it seems to have been wasted effort on my part. I am still hoping to be proven wrong about that, obviously.

I had once thought this issue was going to be rooted in the input layer (either a dblclick identification error or input debouncing code), but I now think it is in the character game rules state machine. I think the impulse to block was sent to the character state machine and (since I am holding the right mouse button) input is done with it and will not say anything more. This is based on the situations I have seen to be working which I expect would also be broken if it were in input.

I think the block impulse was processed and discarded by the character state machine. I /think/ it has to do with a block state transition occurring in proximity to the request for the instant skill cast (either the block release right before the instant or the apply right after.... or the release/apply being in the same window with the instant). It could even be special code which is meant to prevent the block state from getting stuck "ON" with tight block/cast/release timing.

If you hold block through the instant, block works - that's block casting! We all do it - it works!
If you click, hold the RMB (no skillcast) it works (most the time?)
if you click, duration-cast, hold RMB, then the block is applied after the cast is resolved.
Click , instant-cast, hold... (with correct timing) character does not attempt to block
Slow it down and blocking works.

Unfortunately, during a trial, I seem to often find the 'right' timing to repro the issue, which significantly reduces my usefulness as a tank 8(

I wish I could set breakpoints and inspect the code. Oh well.