From Safe Haven Harbor
Jump to navigation Jump to search

Please feel free to update this page with suggestions for other logging code snippets.

Autologger instructions for MUSHClient

This only works for MUSHClient.

  • File > World Properties
  • General > Logging
  • What to Log - You will want to check Log Output at the VERY LEAST. You may wish to also want to Log Commands, but that is entirely up to you (this will show the text you typed in to execute all commands, e.g. 'n' to go north, 'say Hey guys' to say stuff IC, etc).
  • Under 'Automatically log to this file:' you will want to designate a folder where all logs go. You can use certain code (shown at the bottom) such as %Y for year, %b for month, and %d for day (of the month).

In the below image, as an example, the log will show up as "2011Nov16 The Reach" in my log folder (assuming the log is from Nov 16, 2011). If the image is too small to see clearly, just click on it and you'll get a bigger version.


Autologger instructions for SimpleMU

Okay, so, how to create the autologger. This only works for SimpleMU.

  • Add the following to your @aconnect:

@pemit me=>>> Begin Session Log: Yourcharactername-[mid([edit([time()],%B,-)],0,10)]-[last(time())]

  • If you don't have anything set in your @aconnect already, simply enter this line of text:

@aconnect me=@pemit me=>>> Begin Session Log: Yourcharactername-[mid([edit([time()],%B,-)],0,10)]-[last(time())]

  • So if your aconnect already has you reading bboards it will look like this:

@aconnect me=+bbscan;@pemit me=>>> Begin Session Log: Yourcharactername-[mid([edit([time()],%B,-)],0,10)]-[last(time())]

  • Then, go to Tools > Events, and add an event as shown below (MAKE SURE IT IS A GLOBAL EVENT):


  • To test this, you'll need to disconnect from the M* and reconnect. If you are successful, you'll see a message like this:

Logging started to file c:\program files\simplemu\logs\Glasgow-Sun-Sept-24-2011.txt
>>> Begin Session Log: Glasgow-Sun-Sept-24-2011

Et voila! Autologger! You can fine-tune what dumps into the log by excluding channels and such by further using events, but that's the basics.

CMud Logging

  • Go to package editor Click on show events (yellow flag, left hand side)

  • Make a new event called: onConnect

  • Put something along the lines of

#LO PATH\CHARNAME_%time( dd-mm-yy)

E.G. #LO C:\Users\User\Documents\Logs\TheReach\Bronwyn_%time( dd-mm-yy)

  • For PATH put the directory you want it to log to (I have mine split by mush, then character), and CHARNAME is the character you are using if you have separate logins for each.

Zmud Logging

#lo PATH\INSERT YOUR NAME HERE%time( yyyymmdd)}

TinyFugue Logging

To tell TinyFugue to set up logs named by world, which automatically rotate at midnight to log with the new date, use the following steps:

  • Make a directory that you want it to stick all of the logs into. For this example we'll use ~/rplogs
mkdir ~/rplogs
  • Edit your .tfrc file (in your user's home directory) and add the following, then save:
/def -p1 logger = /log -w%1 OFF %;  /log -w%1 ~/rplogs/%1.$[ftime("%F")].log %; /at 00:01 /logger %1
/def -p0 -hCONNECT log_all = /eval /logger ${world_name}
/def -p1 -mglob -h'CONFAIL|ICONFAIL *' recon_on_failure = /log -w%1 OFF%; /repeat -30 1 /connect -b %1

Potato Logging

Instructions for how to set up a daily logroll in Potato can be found here.