MIRC Remote Events scripts allow you to set mIRC to react to a huge variety of events automatically. This is the basis for 'bots' or robot scripts that can be used to serve files, play games and more.
The kind of events that can be used to trigger mIRC into any action you can script vary from set times of day to setting key-words. The use of events is not just for the creation of bots of course. You can automate any task to any event that you like.
The mIRC events scripts can do almost anything you might have use for in IRC chat. Because it can react to text, a mIRC event script can send files it is asked for or answer simple questions.
The mIRC editor for events is overall much the same as for aliases and popups as covered in those tutorials.
As you can see, the 'View' menu again lets you select any loaded Remote Events Script for editing. You can load and unload Remote Events Scripts from the 'File' menu of the mIRC editor.
Commands are much the same in any script type - refer to the MIRC Commands tutorial for more details. The User Levels and the Events themselves are the things you will learn here.
The ':' colons are essential to the correct format of the lines of script. They are used to divide the various sections and some parameters of the event script. Always look at the examples carefully to learn the placement of colons.
That is as much of the formatting as can be covered until the events themselves and the user levels are covered. User Levels are the simpler part so that shall be the next focus of this tutorial.
User Levels allow you to teach mIRC to treat some people differently to others. You can define as many different levels as you wish and then categorize the users you know into those levels.
The default level is 1 and this is the level assigned to everyone by mIRC unless you specify differently. When you script events, the code includes the level of user that the reaction you give applies to.
on 1:<EVENT>:<COMMANDS>
The above shows the format of an event script that applies to all level 1 users, which as stated is the default level. This therefore affects everyone except anyone you previously assign another level to.
To change the level of a user you must decide whether to apply the level to the nick (anyone using the specified nick) or you must specify a hostmask to use.
You can use numerical or named levels (level 5 or level Friend for instance). There are two different methods available to assign and change levels to users.
The first method is to directly edit the User List with the mIRC editor. Open the editor as if to edit your Remotes or Popups scripts and then turn to the Users tab.
The format to use is:
<level>:<Nick OR Hostmask>
You can specify multiple levels if you put a comma ',' between each level.
The other method to assign and change the access levels of users is to use the mIRC commands available. /auser, /guser , and /ruser , are some of the commands available to set and change access levels for users.
The /auser command adds the specified nick/address exactly as it is given to the users list with the specified levels. If you specify [-a], then if the user already exists, the specified levels are added to the current levels the user has.
The /guser command works the same as the /auser command except that it looks up address of the specified nick and adds it to the user list. It does this by doing a /userhost on the given nickname, and returning an address in the format specified by type (see next few paragraphs). If no type is specified then a default address format is selected.
Since this is really the first example shown that uses hostmask types I had better explain this a little. A user/host address is comprised of several parts. There is the Nick, the Identd, the Host and the Domain.
nick!user@host.domainThe host and domain portions of the hostmask are the parts that relate to the server they are connected to the internet through. The domain will therefore be the ISP company, while the host is the specific server machine they are logged onto.
The 'nick' portion of the address is simply the nick that they are using, while the 'user' part is the identd that they have set. In mIRC this will be the identd set in the options. In other clients this is usually the name portion of the e-mail address they entered.
The point is that while anyone can use anyone else's nick on most servers, only persons using the same ISP provider could have the same domain too. However for many of us, we get a different IP each time we dialup to the internet (dynamic IP is the term)
Using the entire User/Host address would not work for such cases so we need to apply a mask (hostmask). This mask matches to parts of the full address rather than the whole thing. There are ten types of hostmask.
When specifying a type of mask to use you simply give the number of that mask type.
0: *!user@host.domainFrom the above, type 3 is one of the best for our purposes here since it uses only the identd and domain portions, and cannot be thrown by a change of nick or the changing of IP after a redial.
The /ruser command, if used without specifying levels, removes the specified user from the user list. If you specify levels then these levels are removed from the current access levels of this user. If all a user's levels have been removed, the user is removed. If you specify a type then the users address is looked up with a /userhost and any users in the users list matching this address are removed.
The purpose of user levels is simple: it allows you to set automatic responses to events that treat your friends differently to people you dont know. This can be used to allow your friends to access your fileserver while not allowing people you don't know to do so, for instance.
All this affects our Event script format as follows:
on 1:<EVENT>:<Command>The first event will apply if the event given was triggered by a level 1 user, while the second event will apply if the event given was triggered by a level 2 or higher user.
You can use a '*' asterisk to specify a 'wild' level, that is the event script will
will be triggered by a user of any level.
on *:<EVENT>:<Command>
Prefix any level with a '!' exclaimation mark to prevent it being triggered by
your own actions.
on !1:<EVENT>:<Command>
You can use a '+' prefix to limit the event trigger to only respond to users of
exactly, specificly the level you set for the event.
on +2:<EVENT>:<Command>
This event will not trigger for level 1 users or for level 3 users (unless they
have additionally been set as level 2 users).
You can limit events to being executed only when you have Ops on a channel by
using the @ prefix.
on @1:<EVENT>:<Command>
That's the basics of setting access levels. Remember that unless you specify different levels for some users, everyone is level 1 and therefore the on 1:is the only level you will need (with or without the ! or @ prefix).
Now its time to look at the events themselves. The events are things you want mIRC to react to. The events cover pretty much anything that can occur in IRC.
You can react to text, either specific words / phrases, or to text from specific users / nicks. You can react differently to those words in ACTION text or Notice text, Channel text or Private Message text.
The text to match can be an exact phrase:
or a word or phrase in the text:
or any text at all using a * wildcard:
The location type can be a channel (#):
one or more specific channels:
a query window (using '?'):
or in all normal or private text (use *):
For more on location types see the OPEN / CLOSE events description further down the page.
The following examples should help you to understand exactly how the formatting of a TEXT event works. Note that the following examples use commands that you should be familiar with from the Commands tutorial.
The above event looks at all text in any channel (from a level 1 user that is not the user of this script) for the word 'help' and if it finds it, sends a message to channel asking the person who triggered the event if they need help.
The above event will trigger when anyone says 'hello' somewhere in the text of a private message or query and will send a private message 'hello' in return.
The on ACTION and on NOTICE events use exactly the same format as on TEXT, and trigger on an action and on a notice event respectively.
The above events respond to an Action and a Notice message respectively. The $1- identifier used in the Notice example contains the entire text content of the notice.
The /describe command is identical to the /me or /action command, but allows you to give a location of which window to send the Action to. The $chan identifier gives the location as the same channel where the notice that triggered the event came from.
The Join / Part events are triggered when a user of the level specified joins or parts (leaves) a channel you are in. Unless otherwise set, this includes your own joining and parting of channels.
The above example will trigger when any default level user (except yourself) joins any channel, and will welcome them. Note that the /say command cannot be used in an events script since it cannot specify where to send the text. The /message <channel / nick> works exactly as /say however.
This one triggers when a user with level 'Friend' parts from the channel #mIRC when you are there. It sends a private message saying 'See ya soon' to them.
The on CHAT event is similar to the TEXT events. The above example triggers when a level 1 or above user says 'hello' in a DCC Chat. The equal sign in =$nick is required to send the reply as a dcc chat message. If no equal sign is used, the message is sent as a private message.
Window types are like the '?' for Private messages and '#' for channels that we have used already in some of the earlier examples.
? means a Private Message or Query Window
= means a DCC Chat Window
* means any window type
! means a File Server Window
@ means a Custom Window
You can't use OPEN or CLOSE events in relation to channel windows however. You must use JOIN and PART events instead.
The above open event is an example of a ^ prefix event, which allows you to halt events. In this example, if the incoming message is from a level 1 user the query window is prevented from opening by using the /halt command. A level 2 or higher user would be subject to the second event script instead.
MIRC Events always try to use the highest applicable level for reacting to any event you have set.
This triggers when a dcc chat connection is first established. The equal sign in =$nick is required to send the reply as a dcc chat message.
This event triggers when you close any Query window, it displays the 'echo' to the status window. In case this seems rather pointless, remember that because logging can be applied to only specific windows, you could choose to log your status window only, and keep track of all major events there where it would be copied into the log - an activity log kind of arrangement.
There are many more events yet but all follow the same basic principles as those above.
For the full list of events and more tips on their use read the help in mIRC on the subject of 'Remotes'.
MIRC Workshop proudly presents Black Knight's mIRC script writing Java Applet. This applet lets you quickly and easily generate lines of code for mIRC scripts. The Script Writer applet is especially suited to writing Remote Scripts including aliases, popups and events.
Simply use the menu driven generator to create multiple lines of code including colours, bold and underline codes, a wide range of preset identifiers, commands, events and anything else at all with 'own input' and edit capabilities.
A few simple clicks and any additional custom input you like and your code is ready to cut and paste into your mIRC scripts. Best of all, using this applet is totally FREE!
The mIRC Script Writing applet is a MIRC Workshop exclusive. No other site offers you such a great and easy way to generate your scripts and popups.
Choose a Subject from the list to continue. (Some subjects contain several tutorials.)