test content
Logo
What is the Arc Client?
Install Arc
Forums > Home› Class Forums›
Options
GF Block is BROKEN as of most recent patch
keshavex
Member, Neverwinter Beta Users, Neverwinter Guardian Users Posts: 8 Arc User
Easy to test. Stand anywhere, Protector's Realm, or safe area in a dungeon or zone.
1) Hold down Shift, your shield goes up and stays up, blocking.
2) Let go of Shift, blocking ends.
3) Quickly hold down Shift again. Shield goes up again, but then inexplicably drops, even while Shift is down. Blocking just stops working. Damage incoming. 1 or 2-shot boss with knockdown, dead GF. Wipe.
This is our class defining mechanic and it doesn't work as of the last patch. The reason, apparently, was because they moved this mechanic server-side to avoid hacks that were altering client side values. The one thing that Ralf Koster taught about MMO design in 1998 was that "The client is your ENEMY. Never put ANYTHING client side". This is still true 15 years later, it's hard to understand why blocking AND stamina regen were implemented client side. Sure, it is more responsive, but look what happens. The inevitable.
Now that blocking has been moved server side, it doesn't work. That's obviously not a workable solution, so I hope PWE is aware of this issue and is working hard to fix it. Meanwhile, please bump this thread GFs to keep the issue front and center.
Thanks
Edit: given all the confirmation in the latter part of this thread, please note that some of the following posts that deny a problem exists have since confirmed the bug in subsequent posts.
1) Hold down Shift, your shield goes up and stays up, blocking.
2) Let go of Shift, blocking ends.
3) Quickly hold down Shift again. Shield goes up again, but then inexplicably drops, even while Shift is down. Blocking just stops working. Damage incoming. 1 or 2-shot boss with knockdown, dead GF. Wipe.
This is our class defining mechanic and it doesn't work as of the last patch. The reason, apparently, was because they moved this mechanic server-side to avoid hacks that were altering client side values. The one thing that Ralf Koster taught about MMO design in 1998 was that "The client is your ENEMY. Never put ANYTHING client side". This is still true 15 years later, it's hard to understand why blocking AND stamina regen were implemented client side. Sure, it is more responsive, but look what happens. The inevitable.
Now that blocking has been moved server side, it doesn't work. That's obviously not a workable solution, so I hope PWE is aware of this issue and is working hard to fix it. Meanwhile, please bump this thread GFs to keep the issue front and center.
Thanks
Edit: given all the confirmation in the latter part of this thread, please note that some of the following posts that deny a problem exists have since confirmed the bug in subsequent posts.
Post edited by keshavex on
0
Comments
D&D Home Page - What Class Are You? - Build A Character - D&D Compendium
> http://mopp4.net/ <
D&D Home Page - What Class Are You? - Build A Character - D&D Compendium
I hope it is indeed fixed, that would be great news, but interested in hearing from others.
The first time you block in a fight, it works. Since it's no longer client-side, the latency can let one hit in perhaps, but the shield does go up. If I drop my guard to throw an attack and quickly block again, no matter how far ahead of the next enemy attack, the shield doesn't actually block anything. In fact, not only will my character be holding her shield up, but she's using her guard at-wills... and yet attacks are still getting through.
Happens 100% of the time if I block something at first, drop guard to do anything else and quickly put it back up. It almost feels like there's a "minimum cooldown time" in place.
Before people suggest it, the attacks that are going through are not DoTs or coming from behind me, and I do have guard meter.
Any consecutive presses roughly a second (think "one mississippi" then press shift) apart seem to work fine, any consecutive presses faster seem to duplicate the "bug".
> http://mopp4.net/ <
Seems common to me but I agree that sounds annoying. By common I mean there's always a delay between server side and client side in any game. Just if you're aiming to block quickly it's a bit too late.
More threads pertaining to this issue
http://nw-forum.perfectworld.com/showthread.php?288402-Guardian-Fighter-s-Guard-ability-not-working-properly
http://nw-forum.perfectworld.com/showthread.php?294151-Guardian-Block-totally-unresponsive-now
http://nw-forum.perfectworld.com/showthread.php?293741-Guardian-Fighter-Blocking-broken-after-the-patch
http://nw-forum.perfectworld.com/showthread.php?285582-GuardianFighter-Block-button-problems
It occurs to me that there is another possibility that may explain why some are not "seeing" this. I know most of your experienced GFs of course know this, but on the off chance that some may not be aware of this, there is a difference being the combat stance where you are holding your shield in one hand and your sword in the other, and the blocking animation where the shield goes up high and center. Being in combat mode puts your shield in hand and has it raised to mid level. When you then block, your shield is raised high and center. Let go of shift, and it drops back down to combat mode, but still your shield is in hand. I thought I'd add this in the event anyone trying to test this is concluding that the shield is still "up" while shift is down based on this misunderstanding.
It's also possible that the bug only affects certain people who are affected by the latency issue, but I'm less inclined to believe this since I'm in the same area as the servers and have excellent network performance otherwise. Trying playing around with the delay variable to see if/when you're affected by this, as eidama reports.
Blocking now honestly isn't even worth trying just buy more pots and try to GTFO of the way. It seems to cause rubberbanding (without blocking ever) if you press it in a hurry or put you into this bugged stance, where you don't block.
It sucks.
Now the class is completely broken.
The name open beta was not a bad choice however open alpha might have been more convincing.
Ah, so that was what caused it? Because I have been having massive rubberbanding since this week whenever I use my Shift movement on any class.
It is definitely not a general network problem because I do not and have not suffered from network lag or latency at any other times.
This makes kiting strategies basically a nightmare or even impossible, at least for certain people.
1) Press Shift and Hold : Shield Up Guard on. ( Guard Stance)
2) Let go Shift : Shield Down (Combat Stance)
3) Press Shift again and Hold : Shield Up but guard is off.. ( But we still see Guard Stance as animation)
4) Press Down to move backward : So your character will move.. nope.. will run!(Not slowly as it should be) At there the fake animation is removed.
This renders the game unplayable in my book, as I need to feel that I am in control of things, which I definitely am not. Counting "Mississippis" and standing around taking free hits before even attempting to block after using any form of powers simply feels utterly ridiculous.
Trying to manage mobs and larger foes at the same time? Without knowing whether or not your GF will block any wind-up swing while trying to keep the small ones in check, based on what feels like Russian Roulette with the odds 60/40 against you, each encounter has caused me to cough up more vile language than I'd like to admit.
Please, you need to adress this issue ASAP.
My tank is actually 53 so it's manageable.. but I agree on T2 fight.. it's a mess.
This has to be fixed fast as the GF class is already not that mandatory on T2 runs (based on what I read)... so if he's the reason of the group wipe it'll be the end of the class on high end dungeon.
later
The fact is that it seems that the guard meter "lies".
It says it's full, you raise your shield, you stab, the enemy attacks you and *BAM* you take the full hit. (which can also mean knockback or knockdown)
It doesn't happen always, but it's rather frequent in epic DD runs. I'd say 30-40% of the time, this can be potentially game-breaking and requires a sort of a fix.
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.
Its strange that there are 4-5 different topics opened about this after the patch.
So if you speak for the devs it means: 1000's of you are imagining things and whatever it is we wont fix it?
Woah wait so Cryptic is claiming working-as-intended on this mechanic? ::deletes Guardian Fighter; Rolls Cleric::