[GAMEPLAY] Auto Attacks Cancel Stealth Without Dealing Damage

When playing a champion such as Shaco (likely others though I've only noticed this on his Deceive and the old Eve). This bug is twofold though I suspect that the issues are related.

Issue 1 - When you use a move which makes you invisible within auto attack range of an enemy it is possible for you to automatically acquire a target and begin attacking an enemy. This occurs even if you have "Auto acquire targets" off in the options menu.

Reproduction Steps:

1. Pick a champion capable of going invisible and moving (Shaco).
2. Use your Deceive to move directly on top of an enemy champion.
3. You will automatically attack the champion you selected.

This first issue combines with the second creating further issues.

Issue 2 - When you attempt to attack from invisibility it is possible for this attack to be canceled breaking your invisibility, but dealing no damage. I suspect this is related to how issuing multiple actions (say duplicate attack commands) will cause them to chain and cancel one another. However, in that case it shouldn't break invisibility. This bug is most easy to duplicate on Shaco due to the previously mentioned issue (Issue 1) which causes this to occur often when deceiving towards an enemy and attempting to get behind them before attacking.

Reproduction Steps:

1. Pick a champion capable of using invisibility (We'll use Shaco again).
2. Attempt to attack and immediately issue another command (attack and move works, but so will attack and attack [just click really fast]).
3. Your attack will play the attack sound and animation, you will lose your deceive buff and invisibility. No damage will be done.

These bugs have been around for ages. I've been able to reproduce it in all four of the previous seasons and can still produce it today. Issue 1 seems more prevalent with a higher attack speed, but that may just be my own bias (I remember games lost due to this bug more than single bad plays). Issue 2 is spotty to reproduce and I suspect it's caused by a race condition between client commands and the server (latency based).

I'd also note that a derivative of Issue 2 is possible to reproduce with any champion. If you attack fast enough you will never actually attack and simply continuously restart the animations.