Automated Events

Vortec IRC includes a set of features which allow you to customize the client and automatically react to a variety of events that occur on IRC, such as people joining and leaving the channel you are on. You can also use events to specify custom CTCP responders.



Event Level List

Event levels can be used to give The event level list is sorted alphabetically but the order of the entries in the list are important since Vortec searches through events from the highest level (bottom of the list) to the lowest (top of the list) looking for user matches and event matches. You can add, remove, and edit event levels by clicking their corresponding toolbar buttons.


The lowest user levels should be placed at the top of the user list and the highest at the bottom. In many cases, it is simpler to use numbers in the level names to help in insuring your ordering is logical.


       For Example:        000-Default

                             500-Friends

                       900-Enemies


Creating the user list.

The user list is used to determine which users are affected by the event handlers and have access to the custom CTCP commands you set up. Users can be added, edited and removed either by using their corresponding toolbar buttons, or from the command line with the /adduser command and removed with the /remuser command, or through the channel popup menus (user | add to user list).


Events

Vortec includes an internal list of IRC events to which it can be programmed to respond to, such as ON TEXT for private and channel text messages. When entering a new event handler into the event window, you should be sure to write the event name in all uppercase characters. i.e. ON TEXT not on text.


@ and = Event Prefixes

Some events may be prefixed with either the @ symbol or the = symbol (cases both may be used where applicable), which modifies the conditions under which the particular event may be triggered. The @ prefix means only to execute the event if you have channel operator status in the channel the event occurred. The = prefix means only to execute the event if the user who triggered the event has the same exact level as the event was placed in, not a higher level.


Event List

All IRC events begin with the word ON followed by the name of the event.


ON ACTION

ON ANY

ON BAN

ON CHAT

ON CHATCLOSE

ON CHATOPEN

ON CLONES

ON CONNECT

ON CTCPFLOOD

ON CTCPREPLY

ON CTCPREQUEST

ON DCCDONE

ON DCCFAIL

ON DCCSENDFAIL

ON DCCSENT

ON DEOP

ON DEOPED

ON DISCONNECT

ON DNS

ON ERROR

ON FSERVGET

ON FSERVMAXGET

ON FSERVTEXT

ON FSERVUSERERR

ON IGNORE

ON INCOMING

ON INPUT

ON INVITE

ON JOIN

ON JOINED

ON KICK

ON KICKED

ON MODE

ON NICK

ON NOSOUND

ON NOTICE

ON NOTIFY

ON NOTIFYOFF

ON NUMERIC

ON OP

ON OPED

ON PART

ON PARTED

ON PRECONNECTION

ON QUIT

ON SERVERDEOP

ON SERVERDEOPED

ON SERVERMODE

ON SERVEROP

ON SERVEROPED

ON SNOTICE

ON SOUND

ON TEXT

ON TOPIC

ON WALLOPS



Custom CTCP Responders

You can create custom CTCP responders by creating event lines using a single word without the leading "ON". This allows users to /CTCP you using that command. For example, you can create a "Pager" to beep when you are away. Create an event line:


PAGE:/beep


Any user can type /CTCP <yournick> PAGE  and your computer will play a beep. This is also useful for XDCC commands.



Copyright © 2009, John G. Kirkland

Created with the Freeware Edition of HelpNDoc: Single source CHM, PDF, DOC and HTML Help creation