Just for posterity's sake, I will continue to record my efforts. I don't know why mIRC makes these extra, out-of-order files, but my solution is the same for my efforts with the default text: Throw in a bunch of remote scripts and write my own. ^^ The main script (EXIT event) is below. This way of logging has the additional benefit of not showing the timestamp twice for events in which I've halted default text to display the text my own way.

Of course, I'm going to have to halt default text for the ACTION event to keep the color, though that won't add color to my own ACTIONs... =/

A bigger problem, though, is that the buffer can only be so long, so I'll often end up missing the beginning where it gets cut off...

As explanation: The text I don't want to log starts out with a color-15 background or doesn't start with a timestamp.
Code:
ON *:EXIT:{
  /window -c @temp
  /var %loopServ = 1, %loopChan = 1
  while (%loopServ <= $scid(0)) {
    /scid %loopServ
    while (%loopChan <= $chan(0)) {
      if ($istok(#chan1 #chan3 #chan9,$chan(%loopChan),32)) {
        /window -h @temp
        /var %file = $+($network,.,$chan(%loopChan),.,$asctime($calc($ctime - $uptime(mirc,3)),yyyy-mm-dd),.log)

        /write %file ====Session Start: $asctime($calc($ctime - $uptime(mirc,3)),ddd mmm hh:nn:ss yyyy)
        /filter -wwxg $chan(%loopChan) @temp ^[0-15],15*
        /filter -bwfg @temp %file ^\[
        /write %file ====Session End: $asctime($ctime,ddd mmm hh:nn:ss yyyy)

        /window -c @temp
      }
      inc %loopChan
    }
    %loopChan = 1
    inc %loopServ
  }
}

Thoughts?

Last edited by CitizenKane; 20/01/07 01:50 AM.