Kassadin, Nidalee and possibly others with backwards firing abilities

Dyonas·10/11/2014, 2:04:46 AM·7 votes·1,163 views

Type of Bug: Gameplay Summary of the Bug: Force Pulse, if cast after a Rift Walk, aims / fires behind. Reproduction Steps: Play Kassadin, Rift Walk with a charged Force Pulse and cast as you land. It'll appear behind you no matter where your mouse cursor is and no my mouse cursor was not behind me. Reproduction Rate: It happens every time you try this combo and means any time you're chasing someone down or just engaging you are effectively down to 2 usable abilities. Server: NA

To elaborate Force Pulse is crippled and will always cast behind you after you Rift Walk. Talk about a stealth nerf... please get this out in a hotfix as he's already crippled enough and this is just too much. I just played a game and came to see if anyone else has reported it and this video sums it up perfectly. The cursor is clearly ahead but the ability is cast behind.

YouTube video

Why am I posting this when it's already been posted? Somehow despite it being reported very early after the patch and being a major issue for at least Kassadin and Nidalee it is still not on the list of known issues! These are two pretty crucial skills for both champions but for Kassadin it's a key part of his already very weak all-in potential. Without this you're stuck with two sources of damage you can use when you try to Rift Walk in for a combo. I don't count the damage from Rift Walk as it's not much higher than a lane minions damage.

6 Comments

Cursed BR10/11/2014, 3:54:08 AM3 votes

I've been having the exact same problem with nidalee. Where, whenever i use her pounce with a followed swipe with the mouse in front of the character, it will automatically use swipe behind the character and not where i commanded to. This has being a real issue that penalised me heavily in many games recently. I, but only wish that this matter is taken into account !!

vesanus10/11/2014, 5:30:23 AM1 votes

Yes I can confirm, happens every time you cast Force Pulse immediately after you riftwalk, a staple Kassadin initiation. Was not the case in 4.17, only after 4.18. Severely hurting his gameplay right now, I would consider it a high priority bug fix. Kassadin summoner 3

FredsSlacks10/11/2014, 1:33:14 PM1 votes

I was just meaning to post the exact same problem. I can also confirm the Kassadin force pulse bug. It is incredibly annoying especially when trying to chase down someone. At first I thought it might have been just mouse positioning but after paying very close attention to my mouse positioning, that possibility was ruled out. I hope something gets done about this soon! Kass is my favourite champ at the moment.

MookieNJ10/11/2014, 11:12:00 PM1 votes

I am having the same exact issue. As Kassadin, I'm very used to using my R followed immediately by my E. As of the last patch, every time I execute this combo my E fires backwards. It's very frustrating as I have to constantly remember to wait a second to properly execute my combo, and during that time enemies can get out of range of my slow. This needs to be hot fixed ASAP.

2yftLP0KQC10/12/2014, 4:42:30 AM1 votes

yeah, this happened to me so much. i thought my mouse was broken! lol

Devilia Satanica10/13/2014, 1:50:26 PM1 votes

What if this is actually riot's way of nerfing these champions?