Project

General

Profile

Scripting » History » Version 18

Per Amundsen, 04/02/2011 09:08 PM

1 1 Per Amundsen
h1. Scripting
2
3
In the latest beta's, I am experimenting with a little more advanced scripting features and I will use this wiki to track progress and features.
4
5 8 Per Amundsen
Syntax, variables and functions will probably change a lot, so don't except previous scripts to still work in the next beta and so forth.
6 1 Per Amundsen
7 15 Per Amundsen
As of build 020411.
8 1 Per Amundsen
9 16 Per Amundsen
There are 2 types of scripting atm, one that have been here for a long time, and a new system.
10
11
All scripting is done in Commands -> Edit Commands where one line represent a script or a custom command.
12
13 17 Per Amundsen
Please note that variables and functions are *different* for these 2 types of scripts.
14
15 16 Per Amundsen
h1. Normal custom commands:
16
17 18 Per Amundsen
Here are some variables which can be used in Custom Commands, its like creating aliases of allready available commands, e.g <pre>/hi /me says hi to $chan</pre> will show <pre>* kr0n says hi to #adiirc</pre> when typing <pre>/hi</pre>
18 16 Per Amundsen
19
Current variables are $1 to $9, $pagearams, $chan and $me. $1 to $9 represents what you type after /yourcommand e.g "/sup /say whats up $1", when typing /sup kr0n it will show like this "User: whats up kr0n".
20
21
$pagearam represents everything written after /yourcommand, $chan replaces itself with current channel and $me replaces itself with your current usernick. 
22
23
You can make combo commands by using | as a seperator, e.g /hi /me says hi to $chan|/me says hi again to $chan 
24
25
$file[path] returns data from a file, $frand[path] fetchs a random line from a file and $floop[path] gets one line increasingly (line1, then line2, then line3 etc).
26
27
h1. New Scripting
28
29 1 Per Amundsen
In Commands -> Edit Commands you can enter a scripting line with the following syntax:
30
31
The line must start with <pre>OnEvent<whitespace></pre>
32
33
Followed by either an expression like this (works recursivly)
34
35
<pre>
36
if (SOMETING == SOMETHINGELSE) { EXECUTE HERE }
37
if (SOMETING != SOMETHINGELSE) { EXECUTE HERE }
38 13 Per Amundsen
if (SOMETING ismatch SOMETHINGELSE) { EXECUTE HERE }</pre>
39 1 Per Amundsen
or by an executed command or function
40
41 2 Per Amundsen
You can now combine expressions with && (AND) and || (OR) like this
42 1 Per Amundsen
<pre>
43 2 Per Amundsen
if (SOMETHING == SOMETHING && SOMETHINGELSE != SOMETHINGELSE) { EXECUTE HERE }
44 13 Per Amundsen
if (SOMETHING == SOMETHING || SOMETHINGELSE != SOMETHINGELSE) { EXECUTE HERE }</pre>
45 1 Per Amundsen
The logic behind these expressions is not fully tested, id love any feedback on this.
46 12 Per Amundsen
47
(note: ismatch will check if SOMETHING exist inside SOMETHINGELSE e.g if something is "hello" and something else is "hello world" it would return True because "hello" exist)
48 2 Per Amundsen
49 1 Per Amundsen
Executed commands are /slash commands already in the client e.g /msg #channel hello world.
50
Executed functions are predefined functions in the client, only two exists for now.
51
52
An execution block can consist of both commands and functions if seperated by | (pipe) character like this <pre>/msg #channel hello world|.function bla bla|/msg #channel2 hello world</pre>
53
54
Furthermore there is a lot of predefined variables for use with these functions, for now they are:
55
56
$event / current event, e.g PRIVMSG 001 MODE and so forth
57
$channel / the channel the event occurred on, if any
58
$msg / the message to the channel/user or the message in a raw irc line e.g whois [kr0n] is a registered nick
59
$nick / the nick the event was sent from, can be a irc.server.com, a nick or null
60
$me / my current nick
61
$network / the network the event occured on e.g Quakenet
62
$ident / the from user ident if any
63
$host / the from user hostname if any
64
$myident / my ident
65
$myhost / my host
66 14 Per Amundsen
$server / host from the server e.g irc.server.com
67 1 Per Amundsen
68
Currently predefined functions are:
69
<pre>
70 13 Per Amundsen
.insert requires .insert <nick (use null for nonick)> <where (a channel or $channel, a nick or $nick, or status)> <MsgType (MsgServer/MsgUser/MsgEmote/MsgCTCP/MsgNotice/MsgClient/MsgLog)> <$msg or message></pre>
71 1 Per Amundsen
72
<pre>
73 13 Per Amundsen
.eat <what (text or all)></pre>
74 1 Per Amundsen
.insert is used for inserting a specific message type into a chat window, its intended for use in cases where you want to override how adiirc shows a given event, but can also be used for adding additional messages.
75
76
.eat is used to tell adiirc to either "eat" the text output from an event or "eat" everything and don't act on this event at all.
77
78
Putting it all togheter, here are a few examples:
79
80
<pre>
81 13 Per Amundsen
OnEvent if ($event == NOTICE) { if ($msg ismatch hi there) { .insert $nick status MsgNotice $msg|.eat text } }</pre>
82 1 Per Amundsen
83
insert the notice into the server window and tells adiirc to "eat" its own text output from this notice
84
85
<pre>
86 13 Per Amundsen
OnEvent if ($event == PRIVMSG && $msg == herp) { /msg $channel derp } }</pre>
87 7 Per Amundsen
88 1 Per Amundsen
if the event is a PRIVMSG AND the $msg equals "herp", then show "derp" in the channel
89
90 6 Per Amundsen
<pre>
91 13 Per Amundsen
OnEvent if ($event == PRIVMSG) { if ($nick == Q || $nick == $me) { /msg $channel Q or $me is speaking! } }</pre>
92 1 Per Amundsen
93
if the event is a PRIVMSG and the $nick equals "Q" OR $me then show "Q or $me is speaking" in the channel
94 9 Per Amundsen
95 3 Per Amundsen
A list of custom events that is also usable as $event ==
96 4 Per Amundsen
<pre>
97 3 Per Amundsen
OnOwner
98
OnDeOwner
99
OnSpecialOp
100
OnSpecialDeOp
101
OnOp
102
OnDeOp
103
OnHop
104
OnDeHop
105
OnVoice
106 13 Per Amundsen
OnDeVoice</pre>