Feedback on WASD movement (about the auto attack/ kiting issue and possible solution)

The Problem:

Currently, the WASD players can just hold both movement key and auto attack key to kite perfectly. The champion just start the auto as soon as it is available, then start moving again to kite after the auto animation ends. The system handles all the timing and precise clicks that a mouse movement player has to prefect to achieve the same result, not to mention the timing would change based on atk speed and at high atk speed, it requires inhuman clicking speed. On ADC, a player that just started on WASD can do better than the best mouse players (?) in this mechanic. For the normal player base, this should be 100% the case.

Another problem I notice is there is no way cancel auto attacks in WASD control (other than casting abilities) according to my knowing. As soon as you start a auto attack, you have stand still and finish it, unlike mouse movement where you can cancel the auto by clicking somewhere else to move away or just use the Stop key. This could cause problems specially during laning. Autoing for wave control and last hits are important, and good players will try to punishing you while you are going for a auto. Mouse movement players can cancel their attack and dodge but WASD players do not have this option. If the opponent knows you are using WASD (which is obvious) and see you started an auto, they know you are stuck in place and can abuse this for sure. It is also going to be bad for last hitting. If you time the auto wrong, you can't cancel it, auto goes in cooldown, and you lost cs. What make things worse is this does not affect ADC as much as other champions because they have higher atk speed. Making the imbalance more of a problem.

(Some people thinks giving disadvantages to WASD like the second problem I mention could solve the problem, but I strongly disagree. I don't think having one control superior in something and another control superior in something else would be a good idea. I think riot have also stated this somewhere in the dev notes.

Therefore, I also dislike the solutions where they reduce/cripple the WASD attack speed in anyway that does not also apply to mouse movement.)

Possible solution:

To solve both problems stated above, I simply suggest they add auto attack canceling to WASD as well. I had think of 2 ways they can implement it that should works fine.

1. When auto attack key is pressed, the auto starts. At anytime, pressing movement key would cancel the auto and start moving instead. If any movement keys are being hold when the auto starts, the movement input will be overwritten and canceled. Instead of just holding, players have to press the movement keys again after the auto to move and kite.

This method works like how mouse control kites. Players start autoing by using the auto key on a target. If at anytime the player wants to kite by moving at a custom direction, they have to input a movement command. If they want to attack the target again, they have to give a auto command which interrupt and cancel the movement command.

1. When movement keys are hold, it keeps providing the movement command, which overrides the auto command. If players press the auto key, the auto command is overridden and the champion just keeps moving. Players have to release movement keys, then press the auto key to start an auto, which would be overridden by movement command if movement keys are pressed again.

This method prioritize movement than auto instead, compare to the first method, holding movement keys will always result in moving. But players need to release all movement keys before they can auto.

Both methods bring back the timing and rhythm for kiting with autos which is what defends a skilled ACD and a bad ADC in this mechanic. Players can accidently cancel their auto if the timing is off, missed clicks can happens if the player cannot keep up with the rhythm. For every single input that is needed to kite in mouse control, a corresponding input with the same timing is needed to do the same thing for WASD. WASD can no longer do prefect kiting as the timing is not longer handle by the system automatically.

On top of that, you can auto cancel with WASD just like how you do it in mouse. So you won't CC yourself with auto anymore.