Lpfix5, you'd need to expand on that greatly, right now it doesn't include the nick or timestamp, that chat.log would be useless. But basically this method work (when setup to write correctly) as long as pisg doesn't expert multiple logs (ie dialy/weekly/etc) for each chan, in which case your face with even more scripting to cycle the files and timestamp them correctly.
As a more long term solution, maybe you should suggest to the pisg developers that 'nick filters' would be a nice feature. So pisg can just ignore the msg's from certain nicknames. Or even better, regex filters, so when pisg parses the file it can ignore lines that match the filters.
sorry aboutt hat it doesnt need much expansion this is what and how it should be displayed has i believe is what your talking about
here
on *:TEXT:*:*: { write chat.log [- $+ $time(hh:nntt) $+ -] < $+ $nick $+ > $1- }
or...
on *:TEXT:*:*: { write chat.log [- $+ $timestamp $+ -] < $+ $nick $+ > $1- }
<< $timestamp probably only works if timestamp is enabled tus $time(hh:nntt) probably is a lil better but you get the idea how you can widden a write like Om3n is talking about
you can do same thing for action
as Om3n was also saying that possibly you have multi chans if so you can have a log file for each individual channel something like this
on *:TEXT:*:*: { write $chan $+ . $+ chat.log [- $+ $time(hh:nntt) $+ -] < $+ $nick $+ > $1- }
even to make it more pinpoint is if you have it on multi servers with multi channels some might be same name then...
on *:TEXT:*:*: { write $network $+ . $+ $chan $+ . $+ chat.log [- $+ $time(hh:nntt) $+ -] < $+ $nick $+ > $1- }
point is its fully customizable im sure youll be able to work something off with this if not theres plenty of peeps that are here to help