Can you get banned for using a macro in game for muting chat? i have had one for about 2 months now and its really helpful.
also can you get banned for macro for spamming an ability. like for an example i am playing urf and i get udyr and i decide that i want to go full move speed and make a macro so i dont have to keep spamming E i can just focus clicking and my finger wont get tired?
The former is a grey area at best, while the latter is a clear example of cheating.
aoto clicker is bannable and just making it so you can't chat is at your own risk
The big thing with macros in-game is whether they provide an unfair advantage; generally, anything that influences the gameplay itself (primarily, if it binds multiple key presses into a single bind).
I know that chat macros aren't explicitly against the rules, and I would think a macro for muting (especially if it's via chat commands) would fall under the same "flag", but even so they are also in a bit of a "use at your own risk" situation, since it may be difficult for Riot and Riot's systems to distinguish whether it does influence the gameplay. I'd recommend submitting a ticket to Support to get proper clarity on that point.
As for "using a macro to spam an ability", that's definitely something that would fall into the "bannable" category. Best to avoid that.
There are a few things in League that are bannable but are things Riot doesn't actually ban people for doing. As far as I know, using a macro to use abilities is bannable but not something Riot punishes. I know of many instances of people using macros and auto-key programs without getting punished, but that doesn't mean that will always be the case.
I believe using any macro/tool to automate actions within the game itself can indeed get you banned.
That includes macros to execute commands such as /muteall.
What's a "normal macro"?
Considering that the function is built into fairly standard equipment, there's probably a lot of players who are actually already doing this. I think that we'd have heard by now, if this was a problem...
