egghelp/eggheads community

Try putting those as separate arguments, like

exec fgkey "/d" "pass"

I suppose you could say "set my-ip 127.0.0.1" and that would make it only bind to that ip address. Then after the listen, set my-ip back to 0.0.0.0 or "" or something. I'm not sure, I've never tried.

Just a note, if you want to watch *everybody* leaving the channel, be sure to bind kick too.

You mean you want to make your own socket, but have eggdrop control it as a partyline socket? Why don't you use "listen" then? I don't think you can do it just in tcl, you'll need to write a module or modify the source. What I interpreted your post as asking was how to make a socket to *co...

Ya something like that.. so does it say v4.user when you type .unprotect, or give a tcl error?

You did type .unprotect first, right? Add a putlog to the uf:unprot to make sure it's all being executed, like after the exec: putlog "unprotected file" Also, I just noticed another error. In uf:unprot it makes a bind with the proc uf:lock, but it should be uf:copy (although the other name...

Probably the only problem is you're using

• with exec. Try getting rid of that part and using exec directly.

It's because you seem to have copied some code from here and thought that your $wordlist (string) is the same as my $fp (file pointer).

no :/

You forgot the part where you download the url. Take a look at some other web downloading scripts for hints.

regexp "<b>(.*)</b>" $text match rank

$text = text of web page
$rank = clan's rank

Use the "socket" command. See the tcl manual for more info.

If you really want it to be every 30 seconds or so you could probably do it like this... (not tested) if {![info exists log_timer]} { set log_timer [utimer flush_logs 30] } proc flush_logs {} { global log_timer set log_timer [utimer flush_logs 30] foreach log [logfile] { foreach {mode chan file} $lo...

You should use the [ code ] and [ /code ] tags.

You should also close your file handle after reading it in.

It's too annoying to go through the code in any more detail without formatting, so I'll take another look when you've reposted with [ code ].

Try regexp with -all, it returns how many matches it made.