Boards›Gameplay

Attack-moving backwards makes your character move forwards! (And other attack-move feedback).

OrangeTacTics·11/28/2014, 2:09:43 AM·3 votes·2,735 views

I picked up Kalista the other day, and I decided to tweak my controls to get better control over her.

Since you can't cancel her autoattacks, I decided to disable auto-attack in the options. In times when I want to attack the nearest target, I configured shift+left mouse click to issue an attack-move command.

However, I noticed three quirks.

First, and most seriously, is one when you try to retreat with an attack-move. I found an edge-case where issuing an attack-move behind you causes your character to move forward instead. It has gotten me killed in more than one game. After a few deaths, I realized what the conditions were:

When an enemy is just outside of your range, issuing an attack-move will cause you to pursue them, even if it means walking in the opposite direction of where you clicked.

Needless to say, it's very frustrating to die from this.

The second issue is less critical, but still obnoxious later in the game when you can one- or two-shot minions. Attack-moving causes your character to move to the target location attacking the enemy first unit that enters your range. However, once that target is dead, your character stops in place.

It would be nice to see the behavior of attack-moving match that of Starcraft and Warcraft III. In these games, attack-moving does not cause you to pursue targets outside of your range, and attack-moving at a location will cause your character to follow through until it reaches that destination.

While testing this, I also found a bug with hold-position. When you disable the auto-attack option, hold-position will cause your character to stand in place without attacking any units in range.

Lastly, as long as I'm posting, one more behavior I noticed a long time ago when I first started playing. As a Starcraft and Warcraft III player, I used to have a habit of holding my mouse over the minimap when I flashed. I expected to flash in the direction of where I clicked. But in League of Legends, you instead flash as if your minimap was not a part of your HUD, and you had clicked the ground beneath it.

It would be great to see any of these issues addressed to promote the use of Kalista and auto-attack-less play.

3 Comments

Leonerdo1/23/2015, 9:13:20 PM1 votes

First, and most seriously, is one when you try to retreat with an attack-move. I found an edge-case where issuing an attack-move behind you causes your character to move forward instead. It has gotten me killed in more than one game. After a few deaths, I realized what the conditions were:

When an enemy is just outside of your range, issuing an attack-move will cause you to pursue them, even if it means walking in the opposite direction of where you clicked.

Needless to say, it's very frustrating to die from this.

I second this. I like to mash attack-move click late-game because it's almost impossible to screw up your leaps that way, but thus makes it harder to attack-move click to disengage and run away. Several times I have mashed a-move far behind me in an attempt to get a few parting shots, leap out of range and then run, but then kalista ends up walking back into range. I thought maybe this is because when the a-move command is issued for the final leap to get out of range, it also registers an attack against the nearest target, and THEN leaps out of range. But I don't know if that is the true culprit, because I usually keep mashing away, and later a-moves after the leap should stop me from chasing back into range.

In anycase, I accept that until this is figured out, I am going to have to use regular move actions once I am out of range of the enemy to run away. I just have to work on the transition between a-move and move at the right time.

Drunk Rummate1/23/2015, 9:23:59 PM1 votes

i actually noticed this trying to kite with kalista myself, that i would often hop in the wrong direct. it is extremely annoying! i hope they can figure out a fix to this.

Kei1431/28/2015, 7:02:04 PM1 votes

First, and most seriously, is one when you try to retreat with an attack-move. I found an edge-case where issuing an attack-move behind you causes your character to move forward instead. It has gotten me killed in more than one game. After a few deaths, I realized what the conditions were:

When an enemy is just outside of your range, issuing an attack-move will cause you to pursue them, even if it means walking in the opposite direction of where you clicked.

Bump

This doesn't seem to be a problem with sivir when I'm trying to kite back, get some movespeed and continue kiting. It is an issue for kalista.