egghelp/eggheads community

joing the kline and kill msgs into 1 proc

2003-02-06T10:06:33-04:00

okay I'm haveing a bit of trouble here, cause in the kill phrase it only sees the kill, but for the k-line part its picking up every and all server msgs, how can i fix this ? here is how the proc goes right now

proc kill_kline_phrase_2 {from key text} {
if {[string match "*KILL*" $text] || [string match "*K-line*" $text]} {
set text [split $text]
set oper [lindex $text 10]
set target [string trimright [lindex $text 8] "."]
set reason [string trim [join [lrange $text 13 end]] "()"]
putserv "privmsg #Smokey :\002New Kill Active\002: Oper:(\002$oper\002) Killed:(\002$target\002) for Reason:(\002$reason\002)"
return 0
} else {
set oper [lindex $text 4]
set target [string trim [lindex $text 8] "[]"]
set reason [string trim [lindex $text 9] "[]"]
putserv "privmsg #smokey :\002New Kline Active\002: Oper:(\002$oper\002) Klined:(\002$target\002) for Reason:(\002$reason\002)"
return 0
}
}

Statistics: Posted by SmokeyOne — Thu Feb 06, 2003 10:06 am

outputing raw server msgs in realtime

2003-01-31T22:17:44-04:00

bind raw - NOTICE kill2_phrase
proc kill2_phrase {from key text} {
global blah(chan)
set oper [lindex $text 10]
set target [lindex $text 8]
set reason [lindex $text 13]
set server [lindex $from 0]
putserv "privmsg #channel :\002OPERKILL\002:$oper Killed $target for $reason on $server"
return 0
}

this will receive all the server msgs, I've tried to just bind it to KILL, still nothing, this looks like the only way i can get the kill msg. I know I would either split the text, or some how only get it to look for "KILL" then output the information

Statistics: Posted by SmokeyOne — Fri Jan 31, 2003 10:17 pm

outputing raw server msgs in realtime

2003-01-31T07:37:16-04:00

okay i have it working, though it now displays ever server msgs, and then Displays in the channel the output style i have. I'm not sure on the right sntax on how to ge it to only look for "KILL"

I was thinking [lindex [split $arg == "KILL" 0]]

would this be right ?

Can you copy and paste the tcl you have written or post a link to it? If you are only interested in KILL's you probably can bind to the RAW with keyword KILL.

Statistics: Posted by egghead — Fri Jan 31, 2003 7:37 am

outputing raw server msgs in realtime

2003-01-31T07:31:21-04:00

okay i have it working, though it now displays ever server msgs, and then Displays in the channel the output style i have. I'm not sure on the right sntax on how to ge it to only look for "KILL"

I was thinking [lindex [split $arg == "KILL" 0]]

would this be right ?

Statistics: Posted by SmokeyOne — Fri Jan 31, 2003 7:31 am

outputing raw server msgs in realtime

2003-01-31T06:34:24-04:00

so in other words, I'll have to make a 40k proc basicly just over retriveing klines, glines, kills, or what ever else is vital information ?

Let us see. You started the thread 4 days ago with:

i need al ittle help with this one, i'm wanting to take raw server msgs and output them to a channel. What would be the best way to go about doing that?

This is a completely non specific and general question. So yes, if you want to catch all raw server messages then you make the RAW binds and call a proc that outputs the messages to your channel. If you need only specific RAW's then you only bind to those specific RAW's. Easy as that.

The answer was already given to you by stdragon. So, why are you re-iterating the answer, instead of starting to just create the Tcl?
How difficult can it be to look up the rfc and create the RAW bindings you need?

Statistics: Posted by egghead — Fri Jan 31, 2003 6:34 am

outputing raw server msgs in realtime

2003-01-31T06:28:51-04:00

Yes and no. It all depends how much, and what information you want.

Some scripts are large yes. I would greatfully love for the programming language that reuires only 3 lines of code, to do everything I ever dreamed of.

But thats silly talk.

First, you should start from the begining, as most of this thread no seems to be bits thrown here and there, then a comment from you, and we don't know what it relates to.

You need to find out how the server sends the information about K, G and whatever information you are beind sent.

Without this, it's pointless even attempting to make a bind. It's simalar to not knowing how to cook baked beans, so you turns the deep-fat-fryer on in preoperation (note the trend on food here).

Now you need to know what format each of the lines come in. One could have a totaly different set of text ot the next. This is needed, so we know how to parse out the information we need to forward.

Depending on the two above, we can now think about the design of the script. Can it be one proc? Does it have to use multiple procs everywhere? Is there any common ifnormation? Howe do we want it displayed, and can we use one format for this?

Wihtout this sort of information, we aint gonna have a clue what sort of sized script is needed.

Statistics: Posted by ppslim — Fri Jan 31, 2003 6:28 am

outputing raw server msgs in realtime

2003-01-31T06:14:27-04:00

so in other words, I'll have to make a 40k proc basicly just over retriveing klines, glines, kills, or what ever else is vital information ?

Statistics: Posted by SmokeyOne — Fri Jan 31, 2003 6:14 am

outputing raw server msgs in realtime

2003-01-30T15:23:18-04:00

Easiest way is to modify the eggdrop source code. If you want to make this tcl-only, it will be pretty hard. Use the raw bind, but you have to bind every single irc message type. Numerics too. It's not hard, really, but it is time consuming!

bind raw - 001 yourproc
bind raw - 002 yourproc
...

proc yourproc {from key text} {
putlog "$from $key $text"
return 0
}

Based on that you should be able to do whatever you want! To output them to a channel, change the putlog line to, putserv "privmsg #sheep :$from $key $text" (notice the : before $from, it's important).

Statistics: Posted by stdragon — Thu Jan 30, 2003 3:23 pm

outputing raw server msgs in realtime

2003-01-30T09:12:52-04:00

i don't think that will work, and I'm still haveing trouble trying to get any or all server msgs from the server =/

Statistics: Posted by SmokeyOne — Thu Jan 30, 2003 9:12 am

outputing raw server msgs in realtime

2003-01-29T10:56:00-04:00

lying??? what part of my posts was i lying? do I know you or something?

Statistics: Posted by SmokeyOne — Wed Jan 29, 2003 10:56 am

outputing raw server msgs in realtime

2003-02-01T03:29:01-04:00

[edit]heh, wrong smokey :/[/edit]

Statistics: Posted by Guest — Wed Jan 29, 2003 1:34 am

outputing raw server msgs in realtime

2003-01-28T23:52:41-04:00

so i would have to use [lindex [split $arg == "KILL"] ]

and make a bind raw - NOTICE

or something to that effect

Statistics: Posted by SmokeyOne — Tue Jan 28, 2003 11:52 pm

outputing raw server msgs in realtime

2003-01-27T10:03:53-04:00

The RAW code you have seen, is the reply sent to the OPER.

Eggdrop will not see this.

From what I understand, messages like these are sent in a SNOTICE

Statistics: Posted by ppslim — Mon Jan 27, 2003 10:03 am

outputing raw server msgs in realtime

2003-01-27T09:11:19-04:00

from what i read in the rfc this is the only thing about kill msgs i can find
361IEUDRPL_KILLDONE

the out put after a oper issuses a /kill username [reason] the server should send a msg like
Recived kill msg from blah. From operman path irc.someserver.com! irc2.someothererver.com!balh!operman (reasonhere)

what I'm wanting is to extract this information into something shorter like : Userkill for $victum from $oper reason : $reason

and outputing this to the channel i have setup. I'm not sure on the code I'm woundering if its just like
bind raw 361 kill_phrase
proc kill_phrase { from key text} {
set $victum [lindex $arg 5]
set $oper [lindex $arg 6]
set $server [lindex $arg 10]
set $reason [lindex $arg 16]
putchan $chan "Userkill for $victum from $oper reason :$reason"
}

Thi sis my thought on how it would go

Statistics: Posted by SmokeyOne — Mon Jan 27, 2003 9:11 am

outputing raw server msgs in realtime

2003-01-27T08:36:18-04:00

It's all dependent on the command you are seding to the server.

The RFC will not just give you the RAW codes, but also the format of any data returned.

Unless we know what code you are expecting, and what details from it you need, we can't help further.

Statistics: Posted by ppslim — Mon Jan 27, 2003 8:36 am