Ah I see. Your script sends the "L" command to the mud and then immediately closes the log (during the execution of the script). Thus the log is closed by the time the mud responds.
If you really wanted to capture something like a "look" output but nothing else, you would need to do it a bit differently. Here is one idea (remembering that the the mud might have stuff queued up to send you before it gets the "look" command).
1. Send a special string that is unlikely to occur normally.
2. Have a trigger that matches on that string and turns logging on.
3. Send the "look" command.
4. Send another special string.
5. Have another trigger that matches on the second string, this trigger turns logging off.
I like the idea of sendIt. The other problem I'm having is that the output from the "l" (look) is not being logged. The log is created, but empty. Should have made that clear in my first post, sorry.
Logging logs output from the mud, and things you type (actually type, not world.send).
The reason logging does not log things in a script is that, if the script wants them logged, it can do it itself. A recent post suggest that if you want that then make your own function to do just that. That would be less typing anyway. eg.
sub Sendit (strText)
world.send strText
world.writelog strText
end sub
Thus you can now call "sendit" to send and log rather than "world.send". You can see that calling "sendit" is less typing, but automatically logs.
With this functionality available it seems unnecessary to worry about whether or not world.send logs in its own right.
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.