Invocation not working properly since 5.3

[Lyreth]

Did it occur multiple times or just once? If it only happens once you may have just moved or clipped the spell. Please post how many times it has happened and how far apart so we can make a case to blizzard that it is still broke.

[Mastamage]

Did it occur multiple times or just once? If it only happens once you may have just moved or clipped the spell. Please post how many times it has happened and how far apart so we can make a case to blizzard that it is still broke.

Full cast. Twice. Believe me, I know when I clip Invocation.

[WarpKnight]

The clipping thing is BS anyway, in my ideal world it'd apply seconds of Invoker's Energy in the same manner as the ticks of mana restoration

[Deleted]

Full cast. Twice. Believe me, I know when I clip Invocation.

Since your basically the only one complaining about experiencing this the last 1-2 weeks, it would be nice if you could accompany your claim with a WoL, instead of just "trust me".

I am pretty sure a lot of those experiencing this often, and stated so in the past 11 pages, would have come back after a supposed fix to say so. So far your the only one.

[Hasufer]

A hotfix was even posted today on mmo frontpage.
I havn't encountered any bugs only selfinflicted clippin' when being a moron :P

[iamthedevil]

Since your basically the only one complaining about experiencing this the last 1-2 weeks, it would be nice if you could accompany your claim with a WoL, instead of just "trust me".

I am pretty sure a lot of those experiencing this often, and stated so in the past 11 pages, would have come back after a supposed fix to say so. So far your the only one.

The hotfix on just went through on the 3rd... so "1-2 weeks" is off.

[Deleted]

http://us.battle.net/wow/en/forum/to...7604?page=4#63

The hotfix on just went through on the 3rd... so "1-2 weeks" is off.

Yes the Note just went through .... the hotfix been here a while.

[Mastamage]

Yes the Note just went through .... the hotfix been here a while.

And you believe Blizzard when they say they hotfix something? Ohhh IDK, like the time they said they fixed Invocation in early May yet we still saw the bug throughout June? Since I'm RoP Arcane now, the chance of me capturing a failed Invocation is very unlikely.

[Deleted]

I never said i trusted blizz. What i said was it was strange you where the only one reporting the bug still to be live, when every one else since the hotfix 26/6, have either confirmed it to be fixed, or have kept silent, witch i take as a confirmation as well, since I am sure they would be back here reporting it to debunk the blizzard blue post..

Also you might be RoP, but since you claimed it happened I assumed you would have logs from that time. Unless your guild do not log every raid.

[Mastamage]

I never said i trusted blizz. What i said was it was strange you where the only one reporting the bug still to be live, when every one else since the hotfix 26/6, have either confirmed it to be fixed, or have kept silent, witch i take as a confirmation as well, since I am sure they would be back here reporting it to debunk the blizzard blue post..

Also you might be RoP, but since you claimed it happened I assumed you would have logs from that time. Unless your guild do not log every raid.

Had it happened in a raid I would have the logs. There have been 2 hotfixes thus far, 1 of which occurred in late April that they didn't publicize but confirmed on Twitter; this one obviously didn't work. The next came in June: they assumed it worked since they had no cases...until I had one. GC is aware of it, and whether he'll do anything about it is beyond me. My guess is no, since he likes to procrastinate.

I've tried to replicate it, but I really don't have the time to sit and spam Invocation all god damn day and have it logged so an MVP can do nothing with it.
Who knows how many other times this has occurred with other players? Casuals don't know the difference between a bug and successful cast on Invocation and therefore won't report it. Again, I had it happen, that's all there is to it.

[Polarthief]

STILL. BUGGED. Incident occurred July 4.

I had ONE single case on Friday (July 5th)

So yeah. Third time they "fixed" it but it's still not fixed. LOL.

[Methusula]

I had ONE single case on Friday (July 5th)

So yeah. Third time they "fixed" it but it's still not fixed. LOL.

That's pretty crazy. I thought I saw it happen a few times since the hotfix, but I wasn't diligent enough to verify that I wasn't clipping. And no, I don't use the nochannel macro.

[jtmzac]

I haven't seen it happen since it was apparently fixed. I do usually wait half a second to make sure its finished casting since I don't trust the castbar with my 200ms latency.

[voltaa]

I haven't had an issue since the first time they said they fixed it, and since there are only very isolated and very undocumented (unproven) cases popping up I'm going to wager it's user error/latency if IE isn't applied, but I am sure since blizz admitted that it was at one point broken we will hear "omg still bugged fix plz" til the end of the expansion when this talent is removed

[Saegno]

Raided for 5 hours tonight and had zero issues where I was having multiple failed evocates before the fix. I'll keep an eye on it in case I get another one but I'm hoping it's fixed for good.

[Deleted]

It bugged on me in ToT yesterday (07-07), twice. So myea ...
Fix =/= fixed

I have a latency of 25-40ms so that can't be an issue, and I'm pretty sure I don't clip the cast with another spell.
__________________
http://eu.battle.net/wow/en/characte...erage/advanced

[Deleted]

Instead of just saying "i am pretty sure i dont clip, and i have good ms" Just post the logs, or have a look your self.

GC or any dev gets blasted with thousands of post every day, empirical will make them more likely to look at it again, especially if they think its been fixed. Otherwise what's keeping them from thinking "Lol troll" or "we fixed it, the newb just clipped he's evocate". There has been a significant decrease in reports of this, and many of the people that were affected the most have since 26/6 reported no problems, so the peer pressure of almost every mage reporting this have declined, to the point were those thoughts seems reasonable from a devs standpoint.

It is not because i dont believe you, it's just that Logs showing this will make a much better argument for devs to take it seriously and have another look.