egghelp/eggheads community

bind mode (servermode on split rejoin)

2007-08-21T06:20:00-04:00

Thanks heh, got that already. Just wasn't clearly explained in the bind mode help.

Statistics: Posted by awyeah — Tue Aug 21, 2007 6:20 am

bind mode (servermode on split rejoin)

2007-08-20T09:32:14-04:00

MODE (stackable)
bind mode
proc-name

Description: mode changes are broken down into their component
parts before being sent here, so the will always
be a single mode, such as "+m" or "-o". target will show the
argument of the mode change (for o/v/b/e/I) or "" if the set
mode does not take an argument. The bot's automatic response
to a mode change will happen AFTER all matching Tcl procs are
called. The mask will be matched against '#channel +/-modes'
and can contain wildcards.

If it is a server mode, nick will be "", user@host is the server
name, and handle is *.

Statistics: Posted by Sir_Fz — Mon Aug 20, 2007 9:32 am

bind mode (servermode on split rejoin)

2007-08-20T04:23:15-04:00

JFYI, on a server rejoin (rejoin from split) on DALnet, I logged this from my bot recently:

For a normal bind mode proc:

Mass op: ($nick) ($uhost) ($hand) ($chan) ($mode) ($target)
=> Mass op: () (tranquility.hub.dal.net) (*) (#awyeah) (+o) (Lucifer)

Meaning the "nick" is considered null (empty), while the "uhost" is the name of the server.

Statistics: Posted by awyeah — Mon Aug 20, 2007 4:23 am

bind mode (servermode on split rejoin)

2007-08-02T14:10:54-04:00

ah ok.

Statistics: Posted by BoaR — Thu Aug 02, 2007 2:10 pm

bind mode (servermode on split rejoin)

2007-08-02T13:59:07-04:00

Thanks, but my idea was a bit different. My bind mode fires on, servermode sometimes. The script basically checks for people mass opping/voicing users and so it kicks the person who set the mass chan modes and bans that persons *!*@host.domain.com

So when a server does the same thing on split rejoin, the script cannot kick, because there is no such nick, as it is a server, but it places the ban *!*@*. So I was wondering, maybe the nick and uhost args are null.

Anyway, will just have to wait for another one on DALnet. You can find them often on DALnet hehe.

IMHO bind rejoin is only useful when we are dealing with users joining from a split, and not concerned about the server modes which the server sets after the rejoin is successful.

Statistics: Posted by awyeah — Thu Aug 02, 2007 1:59 pm

bind mode (servermode on split rejoin)

2007-08-02T08:08:56-04:00

bind rejn - {*} [namespace current]::modes

Statistics: Posted by BoaR — Thu Aug 02, 2007 8:08 am

bind mode (servermode on split rejoin)

2007-08-02T03:22:59-04:00

Just wondering..

Code:

proc mass:op:chan {nick uhost hand chan mode arg} { global botnick moptrigger opflood kickno

when a split rejoins, and a bind mode proc is called and assumingly the server sets restores some channel modes as they were before the split, some +o/-o +v/-v +b/-b etc, the value on that proc $nick would be what?

Since a nick does not exist with the servers name then?? would it be null? Meaning ""? and what about the $uhost? I suppose *!*@* if not then? Just wanted to clarify on this.

The rest $chan, $mode and $arg should be fine, was just confused about $nick, $uhost and $hand if the server is taken as a nick.

Should we check for [string match *.* $nick] if we want to detect a servermode??

Thanks,
JD

Statistics: Posted by awyeah — Thu Aug 02, 2007 3:22 am