[GAMEPLAY] several bugs with Attack Move Click and Move Click

there are several auto attack move bugs. I notice them mostly when playing Ashe, as I am one-trick and rarely play other champions. If I do, it's Maokai in other roles, where due to being a spellcaster and melee my attack patterns wouldn't result in these bugs. So I assume these are relatively easily repeatable with any ranged champion, but certainly with Ashe.

I use Attack Move Click to initiate almost all my auto's.

1. if the target I'm autoing with Attack Move Click consistently gets displaced by someone's ability, especially blitz's but also even just thresh's displacement, even tho that target is most certainly closer to the click than the minions behind me - sometimes she'll attack the minions behind me. it is as if the enemy isn't there at all.

2. if there are minions really close up together, and to select one you need to click between two minions, it seems to me as if what "looks" like is closer to one minion is calculated as closer to the other. I assume this is because it is measuring distance of the minion's base to the click, whereas when I look I see the round minion as a circle, and think the minion's head is closer so it must be closer. As much as I'd like to just learn this quirk - the visual information is that I'm practically on top of a minion when I click, yet don't attack it. Frustrating!

3. ever since the change in a recent patch to make auto's less likely to cancel, it is actually the case that sometimes as Ashe I'm stepping back and forth, quick movements, with my Move Clicks, and she reaches the click I've clicked 'cause I was so close to her, and so for a moment she is standing still before my next click. and she'll send out an auto - which is especially weird because, this time frame with my early game attack speed almost never sends an auto if I'm trying to - it gets cancelled 'cause I issued the move command to soon. I've always noticed that Ashe is slower than other adc's to send her autos out, more time is needed before canceling the animation to still have the attack go through. maybe ashe and other champions who still have more archaic attack animation cancel frames need updating? if their slow windup is intentional for balance however - on such champions they'll need to have this bug adjusted so that they can't cheat out a quicker cancel sometimes.

4. sometimes when a minion dies shortly after I've targeted it with Attack Move Click, my auto is cancelled entirely. I have to wait the time it'll take to make another auto - which is weird for two reasons - this doesn't seem to happen if I use Move Click command instead, and also sometimes during this type of attack bug Ashe's Q passive doesn't stack focus either. Usually if my auto doesn't strike the target - for whatever reason- whether it died, went invulnerable, was block, was blinded, etc - I'll still get a passive stack. if my attack has been consumed so that I have to wait before I can attack again - I get her stack for it. but - sometimes when it's cancelled because the minion died right after issuing an attack move click command - she don't get no stack and has her auto consumed anyway.

5. Attack Move Click doesn't register Gangplank barrels unless you select it directly - which isn't observed with any other traps that I've noticed. Perhaps this is intentional but if not - it's a bug.

6. Sometimes when I issue an Attack Move Click that selects a target walking out of my range or into a brush, my auto is canceled - This definitely is weird because there are many times when this doesn't happen and it's been like this for a long time, that if someone is in your range and vision at the start of a windup for your attack, but walks out of range or into a bush, the attack still goes through. but within the past half year this has changed to its current inconsistent state, at least when using an Attack Move Click to issue an attack under such circumstances.

7. When near a tower - It used to be that you could easily walk between the tower and the wall easily. but now - and I notice this more on a bigger-frame champ like Maokai but also i see it with Ashe too - the champ will walk the long way around the tower, sometimes even they'll start walking towards the wall space as I intend but then turn around to walk all the way around. I notice this when using Move Click commands, especially if I've issued multiple clicks within a short time frame.

8. Fizz E interaction - sometimes if I use an attack move click to select fizz for an auto and he jumps to his invulnerable state, instead of attacking another target nearby, my character will walk towards the click location. they also won't stand in place with their auto cancelled, like seen in a previously mentioned bug. instead of either of these, they walk to the location as if I'd used an move click command, which I hadn't.

9. it's next to impossible to target a ward that's visual behind baron nashor - unless you use an attack move click. moving the screen up to change baron's angle does give some better shot at it - but this is often quite inconvenient.

10. an Hurricane bug - with Runaan's Hurricane, if you attack a ward to clear it in range of the baron or dragon but they had not been aggro'd - the hurricane's extra projectiles will still target them and aggro them. This actually maybe currently been inconsistent - but it seems strange, I swear that this isn't the intended interaction, I'm pretty sure that I've had times when I have been able to clear wards with Runaan's Hurricane without aggroing the baron/dragon.

thank you for reading! I hope some or all of these bugs can be address soon.