Invalid Target bug

07/04/2018 05:59 PMPosted by Pheromone
To anyone still having this bug go ahead and press your (Left ALT) key on your keyboard about 4-5 times. This solution works for me whenever this bug occurs. Cheers all and hope this helps in the future! :-)


This fixed my problem thanks.
How is this bug still a thing
Oh good, it's not just me.

I can literally sit there pressing an attack 100 times while the mob hits me and all it says is invalid target.
09/15/2015 02:08 PMPosted by Pancakê
06/28/2015 04:24 AMPosted by Orcimonde
No clue what happened but I alt tabbed out and back in and things started working for some reason.
People really don't read anything in threads before posting do they?

Alt-tabbing fixed it because you PRESSED ALT.

Which is EXACTLY what I have been saying and quoting over and over and over and over and over and over and over again in this thread.

Invalid Target? Press Alt. Fixed.


Had same issue, wouldn't let me attack or use hearthstones or anything.

Pressed alt and it fixed it.
2 relog fixed the problem
2018-The bug is still there :/
And it happens too when logging on with alts. Same issue started on my monk today, when I switch to my Warrior, there was the same issue.
Mid Rated BG -_-. Same happened to me.
Same thing here. Logging in and out twice for some reason was the magic number to fix it.
THis is bull!@#$
Experience the bug very regularly since BFA.
7 years and this is still a problem wtf blizz
1 Like
I've been playing WoW since the end of BC and I've never had anything like this before until today. It happened to my mage as soon as we started the FH+9 and exiting out of the game and logging back worked. It was very frustrating. Then my dps meter bugged for about 5 minutes. Whatever the cause is please find a solution as this happening in raids, high lvl m+ keys and in pvp is a big no no...
2011-2018 still not fixed LUL
Just had this problem now on my warrior and my hunter..
Had this happen on my mage yesterday in a dungeon, relogging fixed it.
Just happened to me. /reload fixed it.
Happened to me. /reload did not fix it. Relogging did.
This is the second time it's happened to me, ever, and both have been during BFA. This time it was during an island expedition, and I got booted out for my inability to hit things. Thanks Blizz. Great coding you've got there. Can't even fix a 7 year old bug.
Still happening in 2018. For me it was during Black Temple.