logging problem?!?

[Remmius]

Hi all,

First of all, please excuse my poor command of English, I am not native, thank you.

Second, please excuse as well if my question is easy answered by reading docs and faqs here or anywhere else easy to find place, but I have done my best efforts to find the answer myself using above cited ways and failed :/

Now the question.

I have eggdrop 1.6.12

It works greatly and have had no problems at all with compiling running and setting it. In fact I am more than pleased with it, save from one thing, namely:

no matter what I do it refuses, and without any indication of it whatsoever, to log its own posts and actions...

I have tried to play with almost all combinations of

...

logfile <logflags> <channel> "logs/logfile"
This setting tells the bot what should be logged, from where, and to
which file.
...

with no success.

I have even installed and ran Kenny's mirclog.tcl but it fails to log bot's deeds (( too

So I am unable to solve this and would appreciate any help regarding this annoying bug err.. feature ;+)

Thank you for your responces in advance.

Regards,

Remmius

[ppslim]

There is no current way to log the bots own output, otherwise, this would have been documented.

There is no native reason for the bot to log it's output, however, some people may want it for scripts they have loaded. As such, it should be up to scripts to provide it.

[Remmius]

Thanks ppslim,

I understand that I sould write my own script in order to catch bot output to channel.

Is that right?

Regards,

Remmius

[ppslim]

You can write a script that will capture all output generated by a Tcl script.

using

Code: Select all

rename puthelp _puthelp
proc puthelp {text args} {
  #CHECK TEXT FOR PRIVMSG AND NOTICE COMMANDS< THEN LOG THEM
  _puthelp $text $args
}

This will replace the puthelp command with your own version. You can log what you wish with this.