Thursday night vCR training group. Nocturnal's favor... had 4 where the block bug occurred but I had enough health/shield to survive. Had 5 where I died.
Dear ZOS - PLEASE FIX THIS. 13 pulls. 9 unblocked heavy attacks, 5 upstairs tank deaths. Your game is killing the team.
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.
So, vCR prog night again. We did a +0 where I had 5 unblocked heavy deaths, one of which might have been me. Then we did vCR+1. I had 12 unlocked heavy, 2 were my fault. I'm considering quitting the game, since I really prefer tanking and simply cannot do my job like this. I've stopped recording video, because it tells the same old story. Every. Single. Time.
It's been six months since I first reported this bug and I have exactly ZERO indication that anyone is looking into it. I am really disappointed with the dev/support team.
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
Sorry to bother you all, but is there any way to know if there is any status for this issue (including, as disappointing as it would be "not a high enough impact bug to schedule resources against")? I can still easily repro the lack of blocking while holding block for any instant cast on any character at any PC I sit down to (there are harder repro cases which are likely the same underlying issue).
I kinda wish this were an actual bug tracker, so I could see assigned status/priority/severity... Some million posts earlier in this thread, Kevin said he would look into the in game bug reports I created (mentioned elsewhere in the thread which had been closed with "Thanks for the feedback"). I hadn't heard anything support/bug related since.
I've provided more video and information than I ever get when I have to deal with a bug reported from a live title, so I really hope you've been able to reproduce the issue. If I thought I would ever be in the neighborhood (I'm not - different coast, different country) I would offer to drop in... repro only takes a second.
I don't play a lot anymore, and I doubt anything will repair that, but occasionally I find myself wishing for closure here. I cared a lot back when I first posted this.
Hope the holidays are kind and quiet (and lacking in data center power outages, etc).
-- Thaellin
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.
When I was running my guild`s Friday trial event, from what was happening to me was just lag. I would block and a couple of seconds I would finally block. As far as having a block up and the enemy still damaging me, I was good.
@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.
Figured I'd drop a new video. Not really much different from the old videos... Problem is certainly unchanged. Alone in my house, no gear. Showing a bit of 'thjs works and this does not'
The blocking/not addon is my own (seen in previous videos), which just complains if I am holding the right mouse button and block is not active (it is a bit more intelligent than that, but in my house, not running/jumping, outside combat... it really just boils down to 'right mouse button is down, and blocking is not true')
To deal with this in content I notice my loud 'not blocking' notification and must release block and re-press (calmly, so as not to just re-enter the not-actually-blocking state). Often times I cannot get back to blocking before I am hit with a one-shot attack. It sucks.
I just want to BLOCK when the game should allow me to block. It really feels reasonable to expect 'basic, core functionality' to work when there is nothing at all going on that could possibly interfere.
If ZOS has anything they would like me to run which would do precise input timecoding or whatever... anything at all I could do to help get this fixed... I'm still interesting in trying to be useful.