Sockwrites & identifiers

can anyone get me a list of sockwrite/sockread/identifiers needed to to code things for nuclearmsn thanks

sure... if i can remember some, lol...

sockets - all the sockets in nuclear start with msn. and most of the one's you'll be using are the same as in vincula.

msn.look.main - subscription lookup server

msn.look.comm - groups lookup server

msn.server.<cid> - channel server for specified connection id

if you have Broadband Mode enabled, nuclear maintains 12 connections to the channel servers on msn's network. for example:

msn.chan.149 - broadband socket conencted to 207.68.167.149 (TK2CHATCHATG13)

signals - so you don't have to edit the connection to do an action on the raw code from a socket, nuclear sends signals for everything it receives from these sockets.

signal names:

msn.look - lookup server signal

msn.server - channel server signal

msn.chan - broadband socket signal

$1 is the socket name and $2- is the information received from the socket.

example:

on *:signal:msn.server:{ echo -a * Socket $1 sent $2- }

identifiers

$msn.chan(<channel|N>)[.prop] returns information about the specified channel. if N is a number, returns the Nth channel on MSN you are on. (if N=0, returns total number of MSN channels.) if you specify a channel, then you need to specify one of these properties:

pp - passport you're using on the channel

srvip - IP of the channel server

port - local port you're using to connect

rsock - name of channel server socket

lsock - name if local feedback socket

key - highest-ranking known password

cid - connection id

server - server name (tk2chatchata03, etc)

fname - full IRCX channel name

url - link to room

$msn.decode() $msn.encode $msn.ifdecode - sort of the same as in vincula. $msn.decode works the same way. $msn.encode only works on nicknames in channels you're in, it won't try to create a UTF string for plain ASCII text, it returns the stored UTF value for a decoded nickname (so it doesn't get it wrong).

something else that's helpful for scripting with nuclear...

/msn.socklist - displays all nuclear sockets currently open and what they're doing

/msn.debug [u|s] - opens/closes the debug windows. the u switch applies to passport update debug window, and the s switch applies to the server socket debug window. if you specify no switches it opens/closes both windows.

that should be ok for now... theres a lot more tho. if you have questions about the best way to do something with nuclear, please ask here and i'll see what i can come up with.

are the ownerkeys, hostkeys etc stored in vairables or hash tables and how do i +o or +q using stored passwords?

theyre stored as variables:

%msn.qkey.#!!!!chan - ownerkey

%msn.okey.#!!!!chan - hostkey

to host yourself:

/pass <key> or /mode $me +h <pass>