egghelp/eggheads community

Channel logging isn't logging chat

2007-07-17T12:14:57-04:00

I am sorry no one felt able to help

I have solved the problem myself by downgrading to a version that worked before.

Statistics: Posted by Swift — Tue Jul 17, 2007 12:14 pm

Channel logging isn't logging chat

2007-07-15T07:38:00-04:00

I am having the same problem and have searched for the file this particular command is in + have searched every information source I can find, but am still unable to correct things

Can you please give me a clue as to where I would find this scipt to change it?

i really have exhausted my expertise

Statistics: Posted by Swift — Sun Jul 15, 2007 7:38 am

Channel logging isn't logging chat

2007-07-09T18:38:12-04:00

Can you tell me where to find that? I don't want to search through every bloody file.

Eggdrop Command Reference

A quick look in ~eggdrop1.6.18/doc would reveal all the information required.

PS: There's a certain amount of self-help required.

Statistics: Posted by Alchera — Mon Jul 09, 2007 6:38 pm

Channel logging isn't logging chat

2007-07-09T05:59:17-04:00

Can you tell me where to find that? I don't want to search through every bloody file.

Statistics: Posted by shiningphoenix — Mon Jul 09, 2007 5:59 am

Channel logging isn't logging chat

2007-07-06T09:37:11-04:00

For example, you have

Code:

bind pubm - * do:stuffproc do:stuff {nick uhost hand chan arg} { # do stuff here}

You simply add 'return 0' at the end of the do:stuff procedure. So it would look like:

Code:

proc do:stuff {nick uhost hand chan arg} { # do stuff here return 0}

Statistics: Posted by Sir_Fz — Fri Jul 06, 2007 9:37 am

Channel logging isn't logging chat

2007-07-06T08:27:05-04:00

How do I do that?

The following link will help:
return - Return from a procedure

Statistics: Posted by Alchera — Fri Jul 06, 2007 8:27 am

Channel logging isn't logging chat

2007-07-05T07:33:32-04:00

How do I do that?

Statistics: Posted by shiningphoenix — Thu Jul 05, 2007 7:33 am

Channel logging isn't logging chat

2007-07-04T07:48:28-04:00

Simply put, if a pub/pubm bind returns 1 then the message won't be logged. What you can do is add 'return 0' in the pub/pubm binds' procs.

Statistics: Posted by Sir_Fz — Wed Jul 04, 2007 7:48 am

Channel logging isn't logging chat

2007-07-04T07:28:34-04:00

http://www.eggheads.org/news/2006/04/03/32 might shed some light on it

That just gives me more to wonder about. I'm new to eggdrop, so could someone please explain to me what to do so that my bot will log everything that happens in the console channel.

Statistics: Posted by shiningphoenix — Wed Jul 04, 2007 7:28 am

Channel logging isn't logging chat

2006-10-12T09:45:33-04:00

nml,

thanks for the clarification. I'll add "return 0" and hope to get rid of that ..

Baerchen

Statistics: Posted by baerchen — Thu Oct 12, 2006 9:45 am

Channel logging isn't logging chat

2006-10-12T09:44:26-04:00

Oliver341,

unless nml confirms my last posting, I'm not sure I really understood the whole issue. However, once I did it should be no problem to fix that.

Unfortunately I cannot remember your suggestion, but having a brain like a sieve, that doesn't mean much. Additionally, my mail archive from that time has disappeared, so I cannot look it up. I can imagine what you mean, but for the moment and the way CHATstats is designed, this is very hard to implement.

I have already fixed some bugs and added new stuff (no biggies, though). I also changed some command names etc. I hope beta testing will be done by the end of October. If you want to test it with your particular problem, send me an email to

baerchen
dot
chatstats
at
yahoo
dot
de

Thanks,

Baerchen

Statistics: Posted by baerchen — Thu Oct 12, 2006 9:44 am

Channel logging isn't logging chat

2006-10-12T09:34:37-04:00

Actally, no:
AS I've understood the patch update, you must make sure your proc returns 0 at all times in order to avoid blocking logs

return and return 0 will produce the same result.
The problem here tho, is that there's no return at the end of cs:count, in which case the return-value of the last issued command (within the proc) is used as return-value.

So, to conclude, you should add return (or return 0) at the end of the proc in order to avoid blocking logs..

Statistics: Posted by nml375 — Thu Oct 12, 2006 9:34 am

Channel logging isn't logging chat

2006-10-12T06:38:08-04:00

Hey baerchen, good to see you posting. I've used your chatstats script for years and it was a shame I had to unload it. A new version which fixes the logging problem would be great!

(Don't know if you remember me, I'm the one who suggested *!*ident@*.host stats logging to you some time ago)

Hope you're well.

Statistics: Posted by Oliver341 — Thu Oct 12, 2006 6:38 am

Channel logging isn't logging chat

2006-10-11T23:11:43-04:00

Thanks nml375.

In other words, any condition that will not run the proc to its end has to be returned 1 in order to make eggdrop log the PUBM. Example:

foreach e $cs(dont) {if {[lsearch $t *$e*] > -1} {return}}

should then be

foreach e $cs(dont) {if {[lsearch $t *$e*] > -1} {return 1}}

Is that correct?

I agree that the last line you quoted will always return a value different from zero. But if it wouldn't, I would also have to finish the proc with "return 1" ?

Thanks,

Baerchen

Statistics: Posted by baerchen — Wed Oct 11, 2006 11:11 pm

Channel logging isn't logging chat

2006-10-11T17:59:56-04:00

Well, up until 1.6.18, the returnvalue from calls made by msgm, pubm, and notc would'nt matter at all..
One thing to bare in mind however, is that if you do not specify an explicit return, but just let the proc run to it's end, it will return whatever was returned from the last command within it.
In this case, it would return the result from this:

Code:

incr csa([strftime "%H" [expr $u + $cs(timebalance) * 3600]]$c) $t

I would guess in most cases this would be non-zero (and although the description says return 1, it actually applies to any non-zero return)

Statistics: Posted by nml375 — Wed Oct 11, 2006 5:59 pm