test content
Logo
What is the Arc Client?
Install Arc
Options
Guardian Fighter's Guard ability not working properly.
azahron
Member, Neverwinter Beta Users, Neverwinter Hero Users, Neverwinter Guardian Users, Neverwinter Knight of the Feywild Users Posts: 2 Arc User
(Copied this from my other thread. Where you can see I'm not the only one suffering from this bug.)
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).
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).
Post edited by azahron on
0
Comments
also the char often turns away from the target if you atack under guard mode
Please consider implementing some other 'less lazy' solution than the one you chose. Server side for a PvP game blows. If you are going to really make it server side, please consider changing the game protocol from TCP to UDP.
"We've seen a couple reports of that and are still looking into the issue. Thanks for the heads-up!"
I find that holding down shift to guard doesn't seem to register immediately after using an encounter, or if you drop guard and put it back up again without doing anything else in between.
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.
On top of that, I find it's not working if I use it after threatening rush.. I'm so use to using TR and immediately blocking in dungeons its <font color="orange">HAMSTER</font> me over hard atm, the trick for it working that particular time is just to wait a bit before blocking (or using cleave).
The worst though is not being able to drop guard, then put it back up again (in pvp).
It makes the game unplayable as I am unable to defend myself anymore.
agreed you really suffer in pvp even with this minor work around it dosnt help in pvp
and as for their twitter reply dont expect a fix for at least a week or 2 if they even deem it needs a fix.. even though this is class breaking its like telling a rouge u cant stealth.. and makes guardians a 1handed gwf lol
Weapon enchantment effects like plaguefire are not being applied on guard attacks like aggravating strike and shield bash.
I love my GF in pvp (though I play it in pve as well for the better gear and it is just as bad in some circumstances) and this issue with blocking ruins me regularly. It isn't too noticeable 1v1 usually if I outmatch the person in skill or gear or both, but in 1v1 vs challenging opponents and when I am outnumbered it ruins me. Basically, block tends to fail me when the combat is most hectic and I need to use it most.
Yeah it's horrible with 1vx in pvp... It's destroying me in T2 dungeons as well.. Since I use threatening rush to set marks, I can't block afterwards so I'm getting destroyed by everything I just pulled aggro on, not to mention cannot re-guard after using encounters..
I know the client side hacks were an issue, but fixing a problem witnessed by a small population of players by making things worse for an even larger population is not a solution. Did they even do the most cursory of testing before rolling this out?
this needs an immediate fix. more immediate than exploits, which were patched posthaste. instead of being an occasional inconvenience if you're playing PVP and run into an exploiter, this breaks the game for all Guardian Fighters. Where is the official response? All we've heard is "we've heard a couple people say this we're looking into it." What's there to investigate? Server side blocking is broken, end of story. I'm ruffled by this, and GF isn't even my main toon. I can't imagine how bummed you T2's must be.
This is what my OH is finding, that basically his reflexes of putting the guard on are too quick for the game to cope with, and basically he has to leave a slight pause in between encounter skills/threatening rush etc before he can successfully block. Unfortunately the enemy is not compliant with the pause
Recruitment is CLOSED!!
Theres actually a short cooldown and activate time on block and other Shift powers. Its better to keep block up than let it down if you are going to need it again so quickly.
They are also all predicted client side, so if theres a bit of latency and you get hit when trying to dodge/block something late it will rubberband you back, but most times it just lets block and roll feel smoother, which is critical for these sorts of abilities to feel and look better in more cases.
::end quote::
located here:
http://nw-forum.perfectworld.com/showthread.php?296372-GF-Block-is-BROKEN-as-of-most-recent-patch/page3
So I guess they're claiming working-as-intended now. Weak. GF riot in protector's enclave?
Then get raised after the embarrassment to realize that during random times my guard just drops with me still holding shift, just because I moved around a bit and to get it back up I have to break my finger and my keyboard spamming shift so I dont die instantly because Im taunting all the ****ing mobs as a GF should do.
I guess its time to make another character until the break something else INTENTIONALLY. Thank you so much.