mechanical inncongruities
I'd like to point out some details that I think are flawed in regards to game mechanics.
1 - The attack move click: In my opinion, the "shoot the target that's nearest to the cursor" option should ALWAYS make it so you shoot the target that's nearest to the cursor. Not only when the said target is in a certain range. Its really annoying that the attack move click behaves differently when your cursor is barely out of your champion's range.
2 - The mini map: When the "disable mini map movement" option is enabled, the mini map should simply lose it's hitbox. it should never 'capture' the cursor for whatever reason, just never. You guys (RIOT) are already starting to disable interaction with mini map for certain abilities (Zac jump and the like), but it should be the same for move commands when mini map movement is disabled.
An example of bad mini map behavior: When "kyting" an enemy, you alternatively click on the enemy, then away from him and so on. But if when you mean to click away and you miss click on the mini map, even if the mini map movement is disabled, you champion is going to keep running in the enemy's direction, because last buffered command was 'attack' but 'move command' did not go through. See, mini map should simply not exist from the cursor's point of view when mini map movement is disabled.
#MAKEALPHASTRIKENOTBUGGY -> Either state that its normal for AOEs to hit Master Yi in alpha strike (wouldn't make any sense to me) or repair alpha strike. -> Some interactions with untargetability are simply unfair. I'm looking at you Annie's Q and Tibbers. Q's cool down should not reset for failing to hit something because it's untargetable. Tibbers should not stun you when untargetable (A rioter stated at some point that it's normal because it's coded like this, if Tibbers is casted while out of range (buffered), then the target goes untargetable and then Annie flashes in range and tibbers goes off, the "untargetable" target gets targeted.... BUT PLEASE IT SHOULD NOT WORK LIKE THAT).