The bug that wasn't
#1
Around 1.10, Rogues started saying that Vanish was, once again, far less reliable than it used to be. The most noticeable (and easily repeatable change) was that someone simply autoattacking you would break a Vanish. Their autoattack is not broken by the Vanish.

For months this has been a very contentious point between Rogues and Blizzard, them repeatedly saying that nothing was changed. Oh?

Quote:Latency on the server-side does not affect the sequence in which these events are processed and that is what causes what you are seeing. The combat log really only reports the matter in a confusing way. Latency is not the root of the issue, it's how the issue is reported through combat text.

That and you have become comfortable with the functionality of Vanish for some time and now that things are working more as we wanted, it starkly contrasts with what it once was.

I can appreciate if you disagree with the functionality, but it's not broken.

So it was, in fact, an intended change that they repeatedly denied making. Wanna make fun of a Rogue trying to Vanish? Simply keep autoattack on. :angry:
Trade yourself in for the perfect one. No one needs to know that you feel you've been ruined!
Reply
#2
wow....that's bs....
Garrin

<span style="color:blue">Garrin - Lvl 60 Human Paladin - Stormrage <Lurkers>
Gasan - Lvl 14 Dwarf Priest - Stormrage <Lurkers>
Bladewhisper - Lvl 60 Rogue - Stormrage <Carpe Aurum>
<span style="color:red">Garrin - Lvl 25 Orc Warlock - Dethecus <Frost Wolves Legion>
Tigarius - Lvl 14 Tauren Warrior - Dethecus
Garrin - Lvl 13 Tauren Druid - Thunderhorn
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)