Direct Data Exchange
You can use dde to control your bot/clone whatever. Since dde is exactly what it states, Direct, you can have one mIRC on one network and the other on another network. This can be extremely useful if you wanted to link two channels on two different networks, but who'd want to do that?
DDE Controls
Note: The servername is not an irc server just any name you wish your dde server be.
Commands:
/ddeserver on {servername}
/ddeserver off
/dde {dde server} command "" /command
Variables:
$dde {servername} connected ""
Returns connected,not connected, or connecting.
$dde {servername} channels ""
Returns the current channels that dde server is currently on.
$dde {servername} exename ""
Returns the path and filename of the program its running on.
$dde {servername} inifile ""
Returns the path and filename of its main ini.
$dde {servername} {channel}
Returns the channel name and all users on the specified channel.
$dde {servername} server ""
Returns the current server or last server if you are not connected.
$dde {servername} nickname ""
Returns the dde server's current nick.
$dde {servername} version ""
Returns the current version of mIRC the dde server is running on.
Sample Controls
These sample controls would be if your dde server was mirc and your clone's dde server was mirc2.
These are for the Alias Section:
clonestat {
if ( $dde mirc2 connected "" == not connected) {
echo 2 Your clone is currently not connected to IRC.
halt
}
echo 2 $dde mirc2 nickname "" is currently connected to $dde mirc2 server ""
echo 2 $dde mirc2 nickname "" currently on $dde mirc2 channels ""
}
clonejoin {
dde mirc2 command "" /join $$1
}
cloneinvite {
dde mirc2 command "" /invite $$1 $$2
}
cloneping {
dde mirc2 command "" /ctcp $$1 ping
}
These are just a few of the hundreds of commands you could make for your clone.
A Sample Channel Linker
Once again we'll assume that your dde server is on mirc and you are on #test on DALnet. Your clone's dde server is on mirc2 and it is in #testing on Efnet.
We'll use variables just to make it easier to switch around.
You will:
/set %link mirc2
/set %network DALnet
/set %linkchan #test
/set %playchan #testing
Your Clone will:
/set %link mirc
/set %network Efnet
/set %linkchan #testing
/set %playchan #test
Then for both you and your clone in the Remote, Events:
1!:ON TEXT:*:%linkchan:/dde %link command "" /msg %playchan [ $+ %network] ( $+ %linkchan) - $+ $nick- $parms
1!:ON ACTION:*:%linkchan:/dde %link command "" /msg %playchan [ $+ %network] ( $+ %linkchan) * $nick $parms
1!:ON JOIN:%linkchan:/dde %link command "" /msg %playchan [ $+ %network] ( $+ %linkchan) Joins: $nick
1!:ON PART:%linkchan:/dde %link command "" /msg %playchan [ $+ %network] ( $+ %linkchan) Parts: $nick
What this will look like when its running:
DALnet #test (you are TiAMaT) Efnet #testing (your clone is TiALink)
|
{bOnEz} What's going on? | {TiALink} [DALnet] (#test) -bOnEz- What's going on?
{TiAMaT} [Efnet] (#testing) * _MiZeR_ is bored. | * _MiZeR_ is bored.
{TiAMaT} [Efnet] (#testing) Parts: _MiZeR_ | *** _MiZeR_ (mizer@some.lame.isp) has left #testing
*** Fire27 (fire27@his.own.isp) has joined #test | {TiALink} [DALnet] (#test) Joins: Fire27
Of course theres alot more you can add to this, but its just a small example of the things you can do with dde.
This page hosted by Get your own Free Homepage
©1996 The Scripters Guild All Rights Reserved
Please send all questions and comments to TiAMaT