THIS ATTACK MOVE BUG CAN KILL YOU

its been like this for a very long time, its also hard to notice or even think about so here i am reminding and informing everyone so u dont have to end up in a situation where this is a problem. OR be aware that this was the problem! a shorter version of this will prob be added into the guide, unless riot decides to fix this stupid bug... noob rito
If you want to support me by buying a coaching session check the link bellow
use either link or code to help support me if you're planning on buying anything🙏
#ritogames #leagueoflegends #wackaflcka

[wackaflcka]

if u knew about this id like to know, this rly isnt intended though but im curious how many were aware. Will prob add a short version of this in the guide too, just mentioning the fact. not covering it as much as i did here as this video informs about a lot more if riot were to ever find it..

[table]

The real attack move bug is that you can't attack move while rooted, you must click directly on target.

[FrenzFkn]

Mr flacka i think you are mistaken here. You have attack move on cursor on, so it selects the target closest to your cursor. Since the closest target to your cursor is the enemy at the back, you will move towards him. The behavior you seem to be describing as intented is the „closest to champ“ or whatever it’s called. It might be annoying on twitch but imagine this: Im a cait and i wanna attack the sona in the back who is just a bit outside my attack range while there is an ornn in front of me. so i attack move close to the sona and cait walks to sona to attack her. This is intended, i dont want to be attacking ornn in this situation.

[VeryStrangeweather]

Oh boy... this is a wild one.
Yes you are correct. But I don't think it can be classified as a bug. The best example is that if you attack move click in the middle of the map, while your champion is moving towards it, if it comes against any control ward, it should start attacking it. This is indeed how attack move works in traditional RTS games. This imo is going to be hard concept for others to comprehend if they haven't played StarCraft or some trad RTS.

I think what happens in league of legends with that setting on is that it instantly creates and latches on a target near the cursor creating a right clicked targetable and you basically start walking past any targetable on the way.

I do think this is intended as coding attack move near cursor and there doesn't seem to be another way to create that option without bypassing the traditional understanding of an attack move click.

[table]

After doing some of my own testing, here are the results
My testing:
standing in top alcove:
trying to auto attack dummy in range, hits (expected)
attacking dummy still in top but out of range while another is in range, moves to hit out of range dummy (expected)
attack moving to enemy dummy in river outside baron pit, moves to out of range dummy (expected)
attack moving to enemy further than baron pit, starts attacking dummy in front of me (unexpected)!!

NOTE THAT:
if you attack move close enough or directly attack move click onto the dummy further than baron pit, expected behaviour returns and you will start moving to the out of range dummy
attack moving anything further than the range of top alcove to edge of baron pit results in behaviour desired by wackaflcka

what appears to be happening is expected for most league players up until the range exceeds half of the river.
Why this is the case is unknown: could be a bug, could be an intended feature that turns map misclicks into attack move.
What is weird is that it turns this attack move into an attack move 'nearest player' NOT 'nearest cursor'
I tested this by:
Standing in the middle of top lane:
placing an enemy close to me up and to the left, placed an enemy far (but still in range) down and to the right.
I placed an enemy in mid lane and attack moved to it.
The enemy that started taking attacks was the one closer to my character and not the one closer to the midlane enemy.

This indicates that this out of range attack move turning into a normal attack move is more likely the bug.

[tsuntsunpenguin]

You're right when you say its important to be aware how how the interaction works, but this is intended behavior.

[fyrdup]

the setting worked exactly the way it should have, you want it to target the champion that's closest to the cursor, and it did just that. What I'm getting from this is that you expected the system to adapt to twitch ult, which would be completely unnecessary, or even situationally problematic.

[yorik]

Luckily, I'm not affected by that since I'm scripting

[KoteEndeladze-uu]

There's attach move mechanic where you can use it and show your attack range with it. This all sounds like a skill issue to me. I'll test it later in my game to see if it sometimes works like you say and sometimes not. I doubt it, though. I've always played with the logic that if it's outside of my attack range it will go near to it.