Binding Mouse Button 1 to Attack Move Click interferes with UI/HUD clicks

Deadbeef·Jan 20, 2016·1 votes·10,429 views

When I change my input.ini file to manually set evtPlayerAttackMoveClick=[Button 1], evtOnUIMouse1 = [Shift][Button 1], evtOnUIMouse2 = [Shift][Button2], evtOnUIMouse3 = [Button3], and evntHudMoveableSelect = [Shift][Button 1],[Button3], I can no longer drag and drop the camera on the minimap. Item selection in inventory and shop is workable but slow--double-click behavior in particular is unresponsive.

Expected Behavior: Setting Attack Move Click to MB1 and UI/HUD interactions to Shift+MB1/MB2 allows for responsive Shift-clicking inside UI/HUD elements.

**Actual Behavior: **Shift-clicking on UI/HUD elements is unresponsive or unusable.

Success Rate: 10/10

**Steps to replicate: **

In input.ini, set:

evtPlayerAttackMoveClick=[Button 1] evtOnUIMouse1 = [Shift][Button 1] evtOnUIMouse2 = [Shift][Button2] evtOnUIMouse3 = [Button3] evntHudMoveableSelect = [Shift][Button 1],[Button3]

Attempt to move minimap by shift-clicking. Attempt to buy and sell items smoothly and responsively. Attempt to successfully and consistently interact with menu options. Observe unresponsive or unexpected behavior.

Let me know if I can do anything else!

6 Comments

RiotRiot BaconhawkJan 20, 20161 votes

Hey there,

Thanks for the thorough bug report! Unfortunately, changing your .ini manually is not supported and can result in unexpected behavior. It is known that rebinding mouse button 1 can cause issues, which is why it's actually not allowed ingame.

Sorry m8 Amumu

DeadbeefJan 20, 20161 votes

I understand, and thanks for the speedy response! I guess you could consider this a feature request?

This particular rebind of MB1 is really helpful for AD carry players in terms of APM while kiting. Is there any chance you could pass this along to someone who might be interested in taking a look at it? [zombie-nunu-tears]

MudintheWaterJan 20, 20161 votes

[{quoted}](name=Riot Baconhawk,realm=NA,application-id=LqLKtMpN,discussion-id=knbAjRgQ,comment-id=0000,timestamp=2016-01-20T00:42:12.128+0000)

Hey there,

Thanks for the thorough bug report! Unfortunately, changing your .ini manually is not supported and can result in unexpected behavior. It is known that rebinding mouse button 1 can cause issues, which is why it's actually not allowed ingame.

Sorry m8

Wait, given how many people seem to do this can you clarify the "not allowed ingame" aspect of it? I remember a ton of posts on Reddit about how to work around the binding; are workarounds that force the binding allowed under the rules or are they considered unfair advantage since you can't set the input in game?

DeadbeefJan 20, 20161 votes

It's not allowed ingame because it's unsupported functionality. They're allowed under the rules (probably?) but it doesn't really work perfectly so it's not permitted without some tinkering. That way they don't have to call it a "bug," because it was never intended to work that way. I think.