Another suggestion: Simplistic direct connect alongside the more complex way of connecting using the "socks" commands.
It'd work similarly to a DCC connection, except there'd be no window to view the text, a port could be set to connect on, it listens on a certain port or ports and there could be modifiers set to do things on connect, failed connect, and disconnect.
example set of all parts of this:
/clisten 0.0.0.0 port -f <command> -c <command> -d <command>
/connect 1.1.1.1 port -f <command> -c <command> -d <command>
/cmsg 1.1.1.1 port
on cmsg:0.0.0.0 port:*text*:{ commands }
$caddress <-- for use in "on cmsg"
Here 0.0.0.0 corresponds with the true ip of the computer, so that it binds to that ip (instead of the computer's LAN ip, if it has one). 1.1.1.1 corresponds to the ip of the computer the script is connecting or connected to.
The command after the modifier gets set off when the connection fails (-f), connects (-c), or disconnects (-d).
example of a script created with this:
on 1:start:{ /clisten $ip 7070 }
alias linkup { /connect $$1 7070 -c /cmsg $1 pass $2 -f echo -a Linkup to $1 failed! -d echo Disconnected from linkup! }
on cmsg:$ip:7070:pass 1234:{ /dosomething }
alias dosomething { blah blah blah }
get the drift? It'd be something very easy to script, not complex at all (unlike the gaggle of 'socks' commands *shudders*).
Now, I know I'm going to get the reply "just use the socks commands..", so I'll say this now: I'm suggesting this as an addition for people who don't want to bother with the socks commands, and don't want to use DCC connections for their script (as that gets messy. It's very ugly and the port that it connects on can't be set specifically).
