riot this bug has been known for years and it has not been fixed.......why? I am talking about what i like to call the RED CONE of RAGE.

what is the RED CONE of RAGE you ask? well if you play anyone with cone abilities you might have ran onto this infuriating bug that seriously questions why riot spends time on things like bots instead of fixing a blatant bug

i will use Panth as an example because it happens the most with him because he is in melee range. But what happens is your in a fight but end up near ANY wall or turret (even a flippen broken down turret counts....) and you try to use his E, his cone ability and his main source of dmg, but nothing happens??? what??? you must be stunned or something nub thats why.........no whats happens is your cone will turn red and it simply won;t let you use it. so your stuck there trying to turn the cone in different areas while its still red, while the turret is shooting down on you. then an easy turret dive turns into a death....

SO i will ask again riot WHY HASN'T THIS BUG BEEN FIXED YET?

I have brought this up multiple times without avail so i apologize for the sour attitude......

My riven and I have missed many a kill because of this...

smart cast ftw

it's because cone abilities don't start at your champ, but a little ahead. So if there's an obstacle at the source of the ability, you can't cast it. It's not a bug, it's intentional. If they didn't want it there, the cone would just never turn red.

Kahmehameha, but there simply isn't an obstacle most of the time i am pressed up against the wall but facing outwards or beside a turret.

.

bumpity

They did this to prevent a lot of the no-risk baron and dragon steals during season 1, but I think that was only intended for behind the baron and dragon pit with certain skills.

But if Riot gave a fck about anything else but vomiting up a new champion every 2 weeks, how would they vomit a new champion every 2 weeks?!

"Lol ruin stealth on Eve and Twitch: release Rengar and Kaz"........ Really?