Some users prefer to write their own IRC scripts to avoid the potential problems caused by a malicious or buggy script. IRC Scripts downloaded from public web sites or received from other IRC users may contain backdoors or similar malicious commands. Event handling code must be careful when dealing with input received from other IRC users a poorly written IRC script may leave the user vulnerable, allowing attackers to possibly read the user's passwords or private conversations, execute arbitrary commands in the user's IRC client, or access files on the user's hard disk. Since IRC scripts are used to interface with a public network, they are a favourable target for attack. Many scripts contain nothing but long lists of pop-ups that send humorous or cute canned messages to the channel many of those messages take the form of a 'slap', ridiculing a victim chosen by the user. Scripts for graphical IRC clients may contain pop-ups, which extend or replace the menus built into the client. Advanced event scripting usually requires knowledge of the IRC protocol, though basic events can usually be written without it. Event-based ScriptingĮvents, also known as remotes, allow a script to respond automatically when a particular type of message is received from the IRC server, or when a certain action is performed by the user, such as pressing a key or closing a window.

In some cases, an alias hypo can be associated with a keyboard shortcut. Aliases can usually be used as functions to produce a value that is used elsewhere in the script. Aliases can add new commands, replace commands built into the IRC client, or provide abbreviations for long commands or sequences of commands. For example, a simple alias might allow the user to type ' /j channel' instead of ' /join #channel', saving exactly 5 keystrokes (counting Shift). Aliases are used to bind some command to a set of commands, or give it parameters, to save time when typing such commands over and over. Most IRC scripts contain one or more aliases.

Mirc scripts 2015