I think they will not fix wsg no matter how hard we beg, because at the end of the day, it was never supposed to function like that. The “meta” of how d2 pvpers adapted to glitches like this ( and others, like c/t casting, invisi fields, desync, etc.) is the natural progression of player bases adapting and min/maxing game mechanics whether intentionally included or not.

I think the more logical request here is instead of asking for blizzard to add back in a glitch to maintain the previous meta of d2lod pvp, we request a balance patch that adds new mechanics that are intentionally aimed to balance pvp mechanics so that fhr lock with stun abilities don’t debilitate all other classes. Maybe a cooldown on fhr stun animation, changes to stun frames, or another mechanic to counter endless stun. I don’t have the answer, but I believe that would be the approach Blizzard would take, IF they take any measures.

This is how From Software handled the shield toggle glitch which was basically exactly this on dark souls. You'd get put into a stunned animation if a weapon did enough poise damage, and then changing your shield or weapon cancelled the animation.

From Soft realized this was a huge part of PVP, so in the next games they just baked this in to all of the weapons. if it was a big weapon, it would get 2 hits guaranteed. Little ones would let you roll out of them- rolling being a way to have invincibility frames and a dodge in one.

I hope they take a page from from soft and handle this the same way and bake it into the game vs players.

That certainly is one direction to take this, but I don’t trust Blizzard to follow suit.

But I’d also say - just because something was a huge part of pvp before, doesn’t mean it has to be a huge part of pvp forever. And especially because this was an unintentional effect, it would be better to have an actual, intentional mechanism incorporated instead of continuing the unintended effect.

As an example, cooldowns / synergies were added into the game. New runewords changed the meta completely. These had huge impacts and shifted pvp viability for tons of builds. But they were inserted intentionally, as designed, by Blizzard. Baking in an unintentional glitch simply because the player base got used to taking advantage of it isn’t necessarily the only solution.

This post was edited by AvanineCommuter on Nov 9 2021 01:30pm

I really hope so. it hurts build diversity both ways if you have people saying "oh boo we don't want sins and barbs" or are instead forced to play classes that have a way to ignore stun and stun heavily themselves like barbs sins and paladins.

kinda lose lose, hope they at least address it and tell us their thoughts.

Yeah absolutely they *HAVE* to address this, and the broken ias caps, since these are absolutely game breaking atm for pvp. I’m just hoping they introduce a new mechanism that actually makes gameplay even more interesting and maybe even open up new viable builds too.

This post was edited by AvanineCommuter on Nov 9 2021 01:32pm

That issue is actually something that might be fixed, because it's not working as intended at all. Unlike WSG which is considered a bug by the devs for some stupid reason.

Basically, the issue he's describing is desyncing on teleport - you are actually teleporting directly on them, but their position isn't updated on your screen. If you do that and shoot down you'll still hit them, though. So it's some issue w/ client not updating or receiving positional updates after teleport. I think it's due to the same thing that is causing mercs/minions to not follow players on their client(even though server is updating their position correctly)

It causes chainlocking to be extremely difficult and they sometimes don't resync at all so it's really annoying to deal with, but unlike WSG, it's something the devs might actually address because it should fall under their "bug" category. It also affects pve players(since visually your merc/minions don't follow you around properly and it can cause gameplay issues) so it has plenty of visibility.

Devs actually haven't commented on WSG at all. I think it was removed from the game accidentally, and wouldnt be surprised if it was even server related.

To the window licker in here. Blizzard knows about wsg. They accidentally removed it from legacy in either 2017 or 2018. They realized their mistake and fixed it back in.

This post was edited by TriWinning on Nov 9 2021 01:40pm

also this

from what ive heard the devs for d2r are using the patch that they rolled back

This post was edited by Arkontas on Nov 9 2021 01:46pm

Yeah IIRC it was a server related issue. That shit was worse than what we have on D2R currently, i remember rubber banding hard any time u were in mindblast lock and being completely stuck.