Oh... NOW you're just lying...
12:25 PM
In LK, we made a change for PvE reasons to let some of these stuns also cause an interrupt, since many bosses were immune to stuns.
It was never the intent that they cause both a stun AND an interrupt. The original change was made to let the interrupts work on stun-immune targets (generally a boss). A target upon which a stun has DR'd is not the same as a stun immune target. The original change was not intended as a stun buff for PvP.
Bottom line: the interrupt portion of these abilities will never happen against players. (source) -GhostCrawler
Well, let's take a look back, shall we? It seems that I can find a place where the stun WAS intended to be used as an interrupt against players who had become immune through diminishing returns...
Hammer of Justice: This ability will now still interrupt casting even if the victim is immune to the stun due to diminishing returns. (source)
That's right... it's from the 3.1 patchnotes. It's not like I went through and found this statement in season2... this is something that happened a couple months ago deliberately. So, either GC is completely off base on this one, or is just lying for some unknown reason.
Subscribe to:
Post Comments (Atom)
June 10, 2009 at 4:02 PM
Why lie when you can just mis-remember?
The real test comes when you throw it in his face. Does he make up some reality where they're both true? Or does he man up and admit that it didn't happen the way he remembers it?
Either way, Bliz won't change it back without a mountain of QQ.
June 10, 2009 at 4:15 PM
He just ignores me and forces me to accept his reality moving forward, however the past may have unfolded. I don't really care about the change because it is rather minor that Maim doesn't also interrupt... it only really matters against mages/pallies.
The thing that bugs me is that they claim it wasn't intended to be part of the PvP arsenal... when it clearly was designed that way at some point.