Hey all,
I just downloaded a client called WinTin++; because it's free, and it supports VT100. Now, I've gotten it to connect to FK, but I can't begin to figure out how to get my logging script to work in it.
Does anyone know enough about it to help me?
Thanks!
p.s. I'm also open to suggestions on easier-to-use free clients that support vt100.
WinTin++ client
Re: WinTin++ client
Two commands:
#config log html
#log append FK.htm
Gives you a beautifully-colored HTML log of your session. Is this what you're looking for?
#config log html
#log append FK.htm
Gives you a beautifully-colored HTML log of your session. Is this what you're looking for?
Kalahani Ka'uhane
Gottschalk, Witchdoctah
Gottschalk, Witchdoctah
Re: WinTin++ client
Partly. My MUSHClient setup actually has adaptive log names fed off of a trigger. "You have chosen to play..." will actually cause a new logfile (if it didn't exist yet, otherwise it appended) to spawn in my logs directory with today's date (in YYYY-MM-DD-<day>-<charname>) format.Grenwyn wrote:Two commands:
#config log html
#log append FK.htm
Gives you a beautifully-colored HTML log of your session. Is this what you're looking for?
#config log html gave me the first part of what I needed.
Thx.
Re: WinTin++ client
If you figure out how to set this up, let me know, because I want that. Lol. =)Lystianna wrote:Partly. My MUSHClient setup actually has adaptive log names fed off of a trigger. "You have chosen to play..." will actually cause a new logfile (if it didn't exist yet, otherwise it appended) to spawn in my logs directory with today's date (in YYYY-MM-DD-<day>-<charname>) format.Grenwyn wrote:Two commands:
#config log html
#log append FK.htm
Gives you a beautifully-colored HTML log of your session. Is this what you're looking for?
#config log html gave me the first part of what I needed.
Thx.
Kalahani Ka'uhane
Gottschalk, Witchdoctah
Gottschalk, Witchdoctah
Re: WinTin++ client
Actually, I think i've got it now... but HTML doesn't seem to like VT100 output. >_>
Still... here're instructions, since ya said you wanted'm.
Add this line to your Main.tin, which will cause this to autoexecute on program start (note: Only do this if, like me, FK is the only MUD you play on ;D):
#event {PROGRAM START} {#ses Forgotten_Kingdoms forgottenkingdoms.org 4000;<account name>;<account pw>; #read Logging.tin}
#action {^A strange voice says, 'We await your return, %0...'}{#zap}
The first will result in the client autoconnecting to FK automatically on program execute, and activate Logging.tin, which will allow you to autocreate logs on character login... complete with date and username.
Then create a second file as a text-only formatted file. I named mine 'Logging.tin'
LOGGING.TIN CODE:
#var {charname}{blank}
#var {logpath}{/WinTin++/Logs/}
#var {logfile}{blank}
#var {logging}{off}
#action {^You have chosen to play %0.$}
{
#log off;
#var {logging} {off};
#var {logging} {on};
#var {charname}{%0};
#format {logfile} {$logpath/%t.html} {%Y-%m-%d-$charname};
#config log html;
#log append $logfile;
#showme Logging is now active to $logfile.
}
#nop This alias is designed to turn logging on, based on last entered character name.
#alias {+log}
{
#if {"$logging" != "on"}
{
#format {logfile} {$logpath/%t.html} {%Y-%m-%d-$charname};
#config log html;
#log append $logfile;
#showme Logging is now active to $logfile.
};
#else
{
#showme {Logging is already active. Please disengage via '-log' before trying to '+log'}
}
}
#nop This alias is designed to turn logging off, without condition.
#alias {-log}
{
#showme {Logging is now disabled.};
#log off;
#var logging off;
}
Now I need a nap. Enjoy!
Still... here're instructions, since ya said you wanted'm.
Add this line to your Main.tin, which will cause this to autoexecute on program start (note: Only do this if, like me, FK is the only MUD you play on ;D):
#event {PROGRAM START} {#ses Forgotten_Kingdoms forgottenkingdoms.org 4000;<account name>;<account pw>; #read Logging.tin}
#action {^A strange voice says, 'We await your return, %0...'}{#zap}
The first will result in the client autoconnecting to FK automatically on program execute, and activate Logging.tin, which will allow you to autocreate logs on character login... complete with date and username.
Then create a second file as a text-only formatted file. I named mine 'Logging.tin'
LOGGING.TIN CODE:
#var {charname}{blank}
#var {logpath}{/WinTin++/Logs/}
#var {logfile}{blank}
#var {logging}{off}
#action {^You have chosen to play %0.$}
{
#log off;
#var {logging} {off};
#var {logging} {on};
#var {charname}{%0};
#format {logfile} {$logpath/%t.html} {%Y-%m-%d-$charname};
#config log html;
#log append $logfile;
#showme Logging is now active to $logfile.
}
#nop This alias is designed to turn logging on, based on last entered character name.
#alias {+log}
{
#if {"$logging" != "on"}
{
#format {logfile} {$logpath/%t.html} {%Y-%m-%d-$charname};
#config log html;
#log append $logfile;
#showme Logging is now active to $logfile.
};
#else
{
#showme {Logging is already active. Please disengage via '-log' before trying to '+log'}
}
}
#nop This alias is designed to turn logging off, without condition.
#alias {-log}
{
#showme {Logging is now disabled.};
#log off;
#var logging off;
}
Now I need a nap. Enjoy!