egghelp/eggheads community

bind notc

2004-09-27T02:19:52-04:00

No doubt, I can surely make a difference.

Statistics: Posted by awyeah — Mon Sep 27, 2004 2:19 am

bind notc

2004-09-27T02:17:04-04:00

ok now its working, and the second one is working too,

Thanks awyeah

Statistics: Posted by lsn — Mon Sep 27, 2004 2:17 am

bind notc

2004-09-27T01:54:47-04:00

Code:

[08:43:56]  OPER UP: * :*** Notice -- nick (ident@host) is now operator (O)

For this message it should be lindex 4 for the nick and lindex 5 for the ident and host. So now combining it all together we will have:

Code:

putserv "PRIVMSG $home :OPERUP: [lindex $arg 4] [lindex $arg 5] is now an IRC Operator."

enjoy!

Statistics: Posted by awyeah — Mon Sep 27, 2004 1:54 am

bind notc

2004-09-27T01:45:01-04:00

i get

Code:

[08:43:56]  OPER UP: * :*** Notice -- nick (ident@host) is now operator (O)

Statistics: Posted by lsn — Mon Sep 27, 2004 1:45 am

bind notc

2004-09-27T01:28:47-04:00

Show me the output of the server notice, so I can split the correct lindex to get the nick. You have done it wrong. Add this line in your proc:

Code:

putlog "OPER UP: $arg"

Like this:
putlog "OPER UP: $arg"
putserv "PRIVMSG $home :OPERUP: [lindex [lindex $arg 0] 5] is now an IRC Operator."

Trigger the script and check in DCC with the bot the what result you get and paste it here.

Statistics: Posted by awyeah — Mon Sep 27, 2004 1:28 am

bind notc

2004-09-27T01:18:22-04:00

Code:

OPERUP:  is now an IRC Operator.

not recognize

Code:

[lindex [lindex $arg 0] 5]

Statistics: Posted by lsn — Mon Sep 27, 2004 1:18 am

bind notc

2004-09-27T01:13:21-04:00

Define another raw with a new notice variable and a new proc.

If you have many like this you can combine all in one, but you will need a foreach loop and your patterns must be stored in list which you would have to do a string match on for each element in the list. The first pattern to be matched against the notice will trigger your putserv function.

Statistics: Posted by awyeah — Mon Sep 27, 2004 1:13 am

bind notc

2004-09-27T01:10:43-04:00

ok, and for the second one ?

Statistics: Posted by lsn — Mon Sep 27, 2004 1:10 am

bind notc

2004-09-27T01:10:59-04:00

Here you can use it like this. Define a match pattern and do a string match in the proc rather than matching your pattern in the bind itself.

Oh and by the way "return 1" on raw's not 'return 0' or 'return'. Returning 1 will cause no further action to be taken place after your proc has ended. It is the opposite of what is used in other binds. See tcl-commands.doc for more info on 'bind raw'.

Code:

### VARIABLES ###set home "#mychan"set notice "is now operator"### SCRIPT ###bind raw - NOTICE oper:upproc oper:up {from keyword arg} { global home notice if {([string match "*$notice*" $arg])} {  putserv "PRIVMSG $home :OPERUP: [lindex [lindex $arg 0] 5] is now an IRC Operator."   return 1   }}

Statistics: Posted by awyeah — Mon Sep 27, 2004 1:05 am

bind notc

2004-09-27T00:52:40-04:00

Code:

set home "#chan"bind raw -|- "NOTICE *is now operator*" operjoinproc operjoin {from idx args} {    global botnick home set nick [lindex [lindex $args 0] 4] puthelp "PRIVMSG $home :OPERJOIN: $nick is now an IRCoperator" return 0 }bind raw -|- "NOTICE *HACK(4)*" operopproc operop {from idx args} {    global botnick home set nick [lindex [lindex $args 0] 5] puthelp "PRIVMSG $home :OPERJOIN: $nick opmode command" return 0 }

where i can define what notice he will use, because ,like is here he take only the first raw

Statistics: Posted by lsn — Mon Sep 27, 2004 12:52 am

bind notc

2004-09-25T23:55:49-04:00

there is no raw number code for a server notice, it is a keyword... NOTICE... simple as that...

bind raw - "NOTICE" proc_to_call

Statistics: Posted by strikelight — Sat Sep 25, 2004 11:55 pm

bind notc

2004-09-25T09:30:45-04:00

This should be binded to the server notice. The 'bind notc' will not trigger when a server notice occurs. Bind notc only work of private/channel notices sent to the bot.

Yes you will need to bind to raw, if a raw key number is present then it will be better, otherwise just string match the $arg/$text.

Statistics: Posted by awyeah — Sat Sep 25, 2004 9:30 am

bind notc

2004-09-25T04:21:10-04:00

hm... so what can i do then ?

you can bind to raw:

Code:

    (17) RAW (stackable)         bind raw            procname            Description: previous versions of Eggdrop required a special compile           option to enable this binding, but it's now standard. The keyword           is either a numeric, like "368", or a keyword, such as "PRIVMSG".           from will be the server name or the source user (depending on           the keyword); flags are ignored. The order of the arguments is           identical to the order that the IRC server sends to the bot. The           pre-processing  only splits it apart enough to determine the           keyword. If the proc returns 1, Eggdrop will not process the line           any further (this could cause unexpected behavior in some cases).         Module: server

or bind to msgm, as a PRIVMSG.

Statistics: Posted by YooHoo — Sat Sep 25, 2004 4:21 am

bind notc

2004-09-25T03:25:19-04:00

hm... so what can i do then ?

Statistics: Posted by lsn — Sat Sep 25, 2004 3:25 am

bind notc

2004-09-25T02:58:16-04:00

Quoted from tcl-commands.doc:

Code:

NOTC (stackable)         bind notc            procname              Description: dest will be a nickname (the bot's nickname,           obviously) or a channel name. mask is matched against the entire           notice and can contain wildcards. It is considered a breach of           protocol to respond to a /notice on IRC, so this is intended for           internal use (logging, etc.) only. Note that server notices do not           trigger the NOTC bind.

Statistics: Posted by YooHoo — Sat Sep 25, 2004 2:58 am