@meddler: A QoL suggestion for Ahri's Foxfire

Basically I think foxfire should get some kind of QoL to make the spell more controllable or reliable.

If you hover over the foxfire icon in game to see the range you get a blue circle like this.

http://i.imgur.com/jqr2u.jpg

Which makes it look like foxfire has a fixed range around Ahri with Ahri at the center.

But the range indicator is a lie. The way foxfire works is that each flame has it's own range with itself at the center, which means 3 smaller range circles, which looks more like this.

http://i.imgur.com/yi4nCQ5.jpg

This difference is the reason why foxfire can actually be unreliable despite it's targeted nature.

Here's how foxfire works right now.

When the Ahri player presses W - 3 flames are generated, each with their own separate range, these flames rotate around Ahri at a fixed speed and after a brief moment launch off to damage an in-range target. The target is chosen based on a priority list.

Nearest in-range champion > nearest in-range non-champion.

If there's no target in range the foxfire(s) continue to rotate and attack the 1st target that comes in range or disappears after 5 seconds.

These mechanics opens up some situations where the spell doesn't/can't attack the desired target.

Some examples:

1. In lane when fighting or harassing, 1 or more foxfire bolts can attack a nearby minion instead of the intended champion target, even if that champion was inside the blue range circle.

2. In a jungle fight this same thing can happen except with jungle monsters instead of lane minions. One or more foxfire bolts gets pull off by a nearby camp, which also causes that camp to attack Ahri.

3. when chasing someone and another target comes in range before the intended target, "stealing" that foxfire bolt.(refering to when 2/3 bolts attack right away and then you chase to get the last bolt to attack as well. NOT when the player summons foxfire while completely out of range)

4. Attacking the scuttle crab while doing baron or dragon

5. Being unable to be used on a minion/attacking a champion when foxfire was meant for a minion

6. Attacking the wrong minion(melee minion instead of siege minion, etc)

---

1- This happens because each foxfire bolt has its own range, the champion is in range of the first 2 bolts(which attack the champion) but not the last bolt, that last bolt only sees minions and so attacks the closest one of those. To avoid this you need get closer to the champion but you have to get much closer which usually requires Ahri's ultimate.

2- this is the same as 1

3- This happens when the intended target isn't already in range of 1 or more bolts when you summon foxfire. Depending on how close you are the target might come in range as the foxfires rotate, but there's nothing stopping another target from coming in range 1st. The best way to avoid this is by getting closer before summoning foxfire(which usually means using your ultimate).

4- This happens because baron/dragon and scuttle crab are both non-champions and so they have the same priority, which ever one is closer gets hit. This can be avoided by simply getting closer to baron/dragon

5- This happens because champions always have priority over non-champions, foxfire simply can't be used on a minion or monster when a champion target is nearby, there's no real way around this.

6- This happens because all non-champions have the same priority, usually you can avoid this by moving closer to the intended target but sometimes minions are so close together that moving closer doesn't have any real affect.

While getting closer helps with most of these it's not always that simple, there are 3 factors. Ahri's position - Target's position - Other targets in range also.

The Ahri player can only control Ahri's position, so while they can influence foxfire not everything is under their control

Here are some ideas on how to fix foxfire so these scenarios don't occur

Change foxfire to have a shared range with Ahri at the center, this makes it so all 3 bolts see the same available targets. This would fix problems 1, 2 and 3.

and/or

Make foxfire interact with the ignore non-champions button so that when it's pressed down foxfire ignores non-champions that are in-range. This fixes problems 1 and 2 and partially fixes 3

P.S on that note making an ignore champions button would be nice too(problem 5)

also on the lol wiki it says this.

> Fox-Fire's targeting priority is as follows: > 1. The enemy champion closest to the orb's location > 2. The target of Ahri's last autoattack > 3. The enemy unit closest to the orb's location

http://leagueoflegends.wikia.com/wiki/Ahri

sadly, I've tried this in game and autoattacks don't affect the targeting priority.

But if autoattacks indeed are supposed affect targeting then foxfire is bugged and needs to be fixed. This would fix problems 4 and 6

If that's a feature that use to be there but got removed intentionally then someone at riot should clarify that so we know for sure.

If you're not going to change foxfire you should at least change the range indicator to match how the spell actually works. Although most Ahri players know each missile has it's own range there's nothing in game that clarifies that, the player has to figure it out on their own. This matters because the indicator shouldn't be misleading to new players and also because when discussing foxfire it should be widely understood that foxfire isn't just a spell where you get in 700range and press w, it has much deeper mechanics than that.

I've already made threads about this but it never seems to get noticed so I'll just keep posting until it does.