yy. looks like continuous ww is broken. if blizz wont rollback it seems there will change of bvb tactic

they should upgrade a f.... ith scanner to remove all hibs , but they going in wrong way f.... up all classes

this, Amazons selfsynch for everything.

Damn bro would suck if all those multi $1000 ghost ppl built suck now.

They already have an ith scanner. Hybrids aren't iths.

its not big deal they can do that in one night , if they have brain they can delete all bugs

Once you put a runeword in it, it stops being an ith. Hybrid runewords are not iths so an ith checker will not see it. The game has an ith scanner that checks whenever you leave a game.

Unless you actually think the server should be checking the contents of everyone's inventory 25 times a second and flagging them for deletion, which could be postponed indefinitely by just perming out frame-perfect with a bot

This post was edited by Worrywart on May 18 2018 02:31am

has nothing to do with tri-ww its just the fact, that u cant chain ww without making every second ww dealing no dmg at all

https://us.battle.net/forums/en/bnet/topic/20764386292?page=3

here an actual thread in blizz forum, post in here and get this hopefully fixed soon.

This post was edited by Manartoth on May 18 2018 03:40am

i imagine the two bugs are related, and have to do with a client/server desynced events when holding a button down to chain issued commands
the walking through moor glitch seems to only occur when you're holding down left click walk without ever lifting it, and goes away as soon as you reclick
whirlwind should be same deal, but the desynced client appearing to whirlwind makes issuing a new whirlwind command impossible