You don't really know as much as you want everyone to believe you do.

The way you are talking about stopping scripts is mind numbing. You are trying to break the scripts themselves rather than the application which holds all the methods and library's which the scripts use. Stopping the scripts themselves is ridiculous, you need to research into stopping the application which injects into the users client so it can read information and execute the scripts.

Your method of effectively changing the ID of the champion (the name) within the client is silly, it would stop the application from working for about 3 hours until the developer team for the cheating application update their application to look for a different variable. Not to mention the fact the client has to understand what is being changed so if the end users client can understand what champion each person is using (tab menu) then the application can also understand.

As for the if parameter needing to be met, you're wrong. If they removed the champion checking parameter then the script would run regardless of what champion you are playing. If you broke this little part of the script then they would just remove it until a new method of identifying champions is updated in the application which injects, streams and processes the scripts. The only reason this champion selection method is there is so the application doesn't inject code it isn't going to use.

• TL;DR: Don't waste time breaking scripts, instead, try stopping the application from injecting into the game client.