|
Malleus Novice
Joined: 05 Jan 2003 Posts: 45 Location: USA
|
Posted: Mon Feb 24, 2003 9:14 pm
Logging Tells.... |
How would I go about logging all the tells sent to me into a seperate log file(tells.txt most likely)
MUD OUTPUT:
<<Name>> tells you: hey whats up?
Is there anyway I can capture just this tell(even if its multiple lines) into a text file, and makes sure it doesnt continue logging after the tell is recieved...?
thanks
/ Malleus / |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Tue Feb 25, 2003 12:06 am |
You can capture tells to a separate window and run a logfile from that window. To capture tells paste this to your command line. You'll also need a prompt trigger with the command #T- Tells.
#CLASS Tells disable
#CLASS 0
#TR {^~<~<%w~>~> tells you:} {#T+ Tells}
#TR {*} {#CAP Tells} Tells
#AL atconnect {#CAP Tells;:Tells:#LOG tells.txt}
The logfile will start automatically the next time you connect. If you want it to start immediately, just type atconnect. It will record whatever gets sent to the Tells window, but there's no foolproof method of logging EVERY tell, even if it's MULTIPLE lines, and NOTHING else. This should come close.
LightBulb
Advanced Member |
|
|
|
Malleus Novice
Joined: 05 Jan 2003 Posts: 45 Location: USA
|
Posted: Tue Feb 25, 2003 1:52 pm |
Okay, it works...but it keeps logging after the tell has been sent. Anyway to stop it from logging?
thanks
/ Malleus / |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Tue Feb 25, 2003 2:41 pm |
You'll also need a prompt trigger with the command #T- Tells.
LightBulb
Advanced Member |
|
|
|
Deneir Beginner
Joined: 14 Feb 2003 Posts: 19 Location: USA
|
Posted: Tue Feb 25, 2003 8:32 pm |
Ive set up one to log peoples equipment then quit and i had it set a #temp trigger for the next time my prompt shows to Disable the log you could try that
Got Mud?
HTTP://www.angelfire.com/rpg/EssexClan/Necro.html |
|
|
|
|
|