Zugg Software :: View topic

Beginner Joined: 24 Jan 2011 Posts: 11

Greetings,
May I request some help with a Cmud config?

Basically, the mud outputs 'tells' - on a new line, indented - something like this:
Joram tells you,
"Hello, how are you."

What I would like to do is:
1) Capture all tells I receive - to a separate window.
2) Have a timestamp before the captured text.
3) Auto-log the contents of that window every mud session.

What I would not like to do:
1) Gag the info from my main window.
2) Substitute the text with %time (hh:mm dd:mm:yyyy) - because that will substitute the text in my main window also.

So, the main window would retain:
Joram tells you,
"Hello, how are you."

The capture window would show:
[10.10 22:09:2017] Joram tells you, "Hello, how are you."

And, make it so the contents of the capture window - are logged into a file (not a new file each mudsession, but it should append to the existing file that contains all my "tell logs")

Also, It'd be a great help if someone could also tell me how to customise font/color of a capture window - such that it doesnt affect the global settings for your main window.

I'd appreciate any guidance on this, thanks!

Posted: Sun Sep 17, 2017 11:15 pm

#TR {^(%w) tells you,} {#CAPTURE Tells}
#COND {"*"} {#EXECWIN Tells {#SAYADD { %trim(%line)}}} {within|param=1}

Something like that should do it.
You need a multistate trigger since it has multiple lines.

As far as timestamps, you turn those on for child windows same as any other window:
Click on the window to give it focus.
Open preferences.
Session tab on the left.
Scrollback tab along the top.
Check show timestamps.

Beginner Joined: 24 Jan 2011 Posts: 11

Thanks so much Shalimar, the trigger works perfectly, except for one thing - the capture window is somehow getting 1 extra line in between each "tell" that is captured.

Main Window:
Joram tells you,
'Hello there'

Capture Window:
[9/18/2017 3:51:48 AM] Joram tells you, 'Hello there'
[9/18/2017 3:51:48 AM] Joram tells you,

Posted: Sat Sep 23, 2017 9:17 pm

Did you have a remnant of your own triggers trying to do this still?

Unless you have the trigger in a module (global scope) or another package that is being seen by the child window (which is unlikely), I'm not sure what else could be causing this.