egghelp/eggheads community

Help trapping notices from chanserv

2005-03-15T20:43:52-04:00

*/me* glares

I do!

Not that I have much use of it, or use it alot.

Statistics: Posted by awyeah — Tue Mar 15, 2005 8:43 pm

Help trapping notices from chanserv

2005-03-15T11:28:21-04:00

No need to discredit regexp just because you don't understand it

Statistics: Posted by greenbear — Tue Mar 15, 2005 11:28 am

Help trapping notices from chanserv

2005-03-15T08:16:20-04:00

But I don't see the use for regexp here. I mean basically its used for complex matching and here you are just using it to match 2 plain strings combined into one.

{^(Q!TheQBot@CServe.quakenet.org)$} $from]}

If you were to use a complex match for the string ChanServ!service@my.network.net then I would understand, but using this for what it is basically not designed to do, but yet it still can do for it has greater ability and yet it is used for simple tasks, which can be done with simple string manipulation commands is not worth it.

As obviously little red riding hood has 2 ways to grandma's house. One is very long and tiring and one is very short. Obviously why would she walk a far distance just togo to the same place? Why not take the shorter route. The shorter route will make it easier togo, require less energry and she will reach in less time.

My point here is, use something simple to solve something simple. If the problem cannot be solved using simple techniques, then go ahead and use something which can the solve the problem.

Statistics: Posted by awyeah — Tue Mar 15, 2005 8:16 am

Help trapping notices from chanserv

2005-03-15T04:58:43-04:00

I highly doubt anyone cares for the fact that regexp is about 13 ms or something like that slower than string match/equal etc.

For getting responses, It fast enough.

Statistics: Posted by metroid — Tue Mar 15, 2005 4:58 am

Help trapping notices from chanserv

2005-03-15T04:26:55-04:00

Regexp is slow, don't know why you would use it, when you can string match easily. When a network has ChanServ services, even if they are offline those nicks are sqlined, so no one can use them. So we don't bother to use the ident and hostname after the nick, just for security.

If you really want, you can use this, simple:

Code:

if {[string equal "ChanServ!service@dal.net" "$nick!$uhost"]} {

Obviously, replace service@dal.net by your networks services' mask. Also do an exact match 'string equal', no need for the -nocase switch or string match.

Plus in the end you can use:
putserv "PRIVMSG ChanServ@services.dal.net :#your stuff"

Just to be more secure, if you are a security geek.

Statistics: Posted by awyeah — Tue Mar 15, 2005 4:26 am

Help trapping notices from chanserv

2005-03-15T02:51:46-04:00

You could cut off stuff like that by using things like,

Code:

if {[string equal -nocase "chanserv" $nick]} {

EDIT:

Here is a piece of code i made for a script of mine which records the chanlev from Q/L on Quakenet and saves them into an array.

Code:

proc cflags::recordchanlev {nickname hostname handle arguments ****} {  variable flags  set from "${nickname}!${hostname}"  if {[regexp -nocase -- {^(Q!TheQBot@CServe.quakenet.org)$} $from]} {   # do stuff here  }}

You could ofcourse just modify it, replace the Q!TheQBot@CServe.quakenet.org with Chanserv!

Statistics: Posted by metroid — Tue Mar 15, 2005 2:51 am

Help trapping notices from chanserv

2005-03-14T04:47:12-04:00

Thanks De Kus ... sounds good

However, would you expand on your answer a little

How/where do I look at raw server responses

Thanks

if i recall right

Code:

proc raw_server_notice {from key arg} {  #your stuff here  return 0;#required}bind raw - NOTICE raw_server_notice

Statistics: Posted by Ofloo — Mon Mar 14, 2005 4:47 am

Help trapping notices from chanserv

2005-03-12T12:56:34-04:00

Heh, okay.

Rememeber that this code will execute on all type of notices. Private notices sent to the bot, notices sent to channels where the bot is on, and also even on server notices if I am correct.

So you have to check and decide through 'if' statements which type of notices you want and who should be sending these notices, in this case it would be private notices and being sent by ChanServ.

See my 'if' code above and use that one for your script.

Statistics: Posted by awyeah — Sat Mar 12, 2005 12:56 pm

Help trapping notices from chanserv

2005-03-12T12:38:56-04:00

Thanks again Awyeah

Got it working

Differences between what you suggest and my code are :-

mask "*" instead of just *

{dest ""} instead of just dest

I will work backwards to see what breaks it

Thanks again

Statistics: Posted by arfer — Sat Mar 12, 2005 12:38 pm

Help trapping notices from chanserv

2005-03-12T12:18:50-04:00

Try this and see the reply in DCC:

Code:

bind notc - "*" test:noticeproc test:notice {nick uhost hand text {dest ""}} { putlog "CATCHED NOTICE: From: $nick - To: $dest - Message: $text"}

You code looks fine to me, don't know why it doesn't work.

Try typing .tcl set errorInfo in DCC after you execute it maybe it generates a error, which I think not.

Statistics: Posted by awyeah — Sat Mar 12, 2005 12:18 pm

Help trapping notices from chanserv

2005-03-12T12:09:36-04:00

Thanks awyeah

I have now tried to trap all private notices in order to see what $nick, $dest and $arg are, using code as follows :-

# ---------- ADDAOP ---------- #

set vChannelServices "chanserv@services.dal.net"

proc pToolsAddaop {nick uhost hand chan arg} {
global vChannelServices
putserv "PRIVMSG $vChannelServices :AOP $chan ADD $arg"
}

bind NOTC - * pToolsServiceResponse

proc pToolsServiceResponse {nick uhost hand arg dest} {
putserv "PRIVMSG #channel :test succeeded, nick is $nick, destination is $dest, text is $arg"
}

Even this does not work. Can you see what is wrong with it?

Thanks

Statistics: Posted by arfer — Sat Mar 12, 2005 12:09 pm

Help trapping notices from chanserv

2005-03-12T10:26:59-04:00

As far as I know bind notc will definately trigger private notices. Basically you have to check the destination if it is a channel or the bot's nick and if nick is ChanServ, then go ahead and do as you like.

Code:

bind notc - * pToolsAopExists................................................. if {[isbotnick $dest] && [string equal "ChanServ" $nick]} {

For matching:

Code:

 if {[string match "*already exists on the * list*" $arg]} {

Statistics: Posted by awyeah — Sat Mar 12, 2005 10:26 am

Help trapping notices from chanserv

2005-03-12T09:55:27-04:00

How/where do I look at raw server responses

read to manual to enable raw logging in partyline (.help console) or log file.
I personally have an extra file for raw log, because this is best see what the server really writes, because the Texteditors don't phrase any (ANSI, IRC, ...) control codes.

Statistics: Posted by De Kus — Sat Mar 12, 2005 9:55 am

Help trapping notices from chanserv

2005-03-12T09:53:25-04:00

Thanks De Kus ... sounds good

However, would you expand on your answer a little

How/where do I look at raw server responses

Thanks

Statistics: Posted by arfer — Sat Mar 12, 2005 9:53 am

Help trapping notices from chanserv

2005-03-12T09:48:31-04:00

best you check raw server incoming traffic and look for the the keyword/number for the respond and bind it to RAW (remember to return 1 only if it was the message your wanted to trap!).
another possiblilty is that the string contains some false whitespaces or contraol codes (I once had a problem on another network, that nickserv put 2 spaces between and . and the next word, which wasnt been seen in mIRC of course, but for matching the string the bot will matter .

Statistics: Posted by De Kus — Sat Mar 12, 2005 9:48 am