I was wondering if anyone else is having trouble with their Guardian's Guard ability after today's patch.
For some reason my Guardian often takes the stance, but he doesn't actually go "into" Guard mode, he puts his shield up but he keeps taking damage as normal until I release SHIFT and press it again - then if I'm lucky he'll start blocking properly.
This happens with a full Guard meter, so it's not an issue of it being down - at first I thought it was some sneaky Drow ability, but everything is getting past the Guard as if it's not there (except for the animation).
Hopefully they'll revert or optimize some stuff, it's made my Guardian pretty much unplayable. =/
yea i have realised it too its effecting me in pvp a lot also i hold down my key and wen i realase it its fine but if i press the button again it will block for a second and ten stop this happens when im moving in any direction.. need a fix to this asap kinda makes a gaurdian a 1h gwf lol
What was happening before the patch, which was blocking being 100% client-side and the server just accepting whatever it gets (including client-side hacks), is obviously not acceptable. But not everything needs to take a round-trip to the server every time.
They don't want us to hold threat, or block incoming attacks.
What is it that you don't understand?
Gaurwulf - GF, hybrid tank/dps, GS 12.5k
I'm starting to feel that this is one of those games where I picked the redheaded stepchild of the classes.
Still, they promised that they'd look into balancing once the more urgent issues settle down, so I'm hopeful things will improve (and that this latest problem will hopefully be fixed before then).
I noticed this yesterday as well, figured it was lag and it frequently caused me to not block "dazed" effects from rogues. Which in PVP is huge and cost me a death or two almost every game. Last minute block is really the biggest thing a GF has, take that away and as others mentioned, just a 1H GWF... which is also very underpowered...
I really hope this gets fixed soon, or this is going to be another "D3" fail where it took so long to fix, people quit...
**** exploiters always ruining it for the rest of us. =/
on a side note agreed exploiters ruin it for everyone in my opinion you should all get banned if your a constant offender because i assume about 60% of those that used this exploit probably used the other ones like the massive damage exploit n whatever is stil unknown to majority of the public gj dickheads.
But pwe you need to fix this asap. Your player base has shrunk after the whole AD fumble and now you hav followed up with this.. when are you guys going to actually fix an issue with out messing something else up?
The best work around that I've found is to immediately Cleave after you use an encounter, followed by a quick shift to go into guard mode. (or if you exit guard mode by letting up on shift, make sure you Cleave before going into guard mode again)
If you don't do this, it'll sometimes look like you are in Guard, but you'll still get hit.
I hope they fix this soon so that we get back the responsive blocks that we're used to.
Yeah except that they have said they want to fix those very things, threat management being very high on their list.
^ good one
This 100x. It's not just guard after guard, it's guard after everything but cleave.
Its only logic they moved it to server side?...
From #1 Guild Pve/Pvp [ Lemonade Stand ]