Zugg Software :: View topic

Wizard Joined: 26 Mar 2008 Posts: 1547

Is there a way to set certain text to be gagged only from logs?

things with lines with ooc: in them, my prompt, etc... I know I can formulate the regex and pattern matches if there's such a feature and I was told how to use it. (Though a multi-line pattern quick reference would be nice)

Wanderer Joined: 14 Jul 2004 Posts: 83

http://forums.zuggsoft.com/modules/mx_kb/kb.php?mode=doc&k=2809

If you have things #GAGged and you have the option to Log after triggers are executed checked, they should not appear in your log file.

Help files are your friend. Grok them.

Wizard Joined: 26 Mar 2008 Posts: 1547

But I don't want it gagged in the game, I just want them gagged from the logfile. My prompt, for instance, as wonderful as it is, is not something I need in my logs.

Edit:
nevermind

Adept Joined: 04 Feb 2005 Posts: 246

Actually, I've long wanted the other way around: gagging from the screen, but not from the log. And no, it's important that I log *after* triggers, because I want the log to reflect stuff I modify.

One use: diverting output to chat windows, but still getting in the log. And no, I don't want different logs for each chat window.

Posted: Wed Jun 25, 2008 9:33 am

There's a part of me that wants to say you can't have your cake an eat it - either you want to trigger after you've modified text on the screen, or you don't - but equally, I can think of some great uses for a command that lets you write out text to the log file. It'd be a nice feature to have.

Wizard Joined: 26 Mar 2008 Posts: 1547

Well, I hate falling back on the simpleMU thing, but it did have an option to gag from log, so it's certainly doable. And uses there are plenty. I may not want drink spam in my log, but I may not mind seeing it (some people have some cool decanters) in the game. The prompt is another biggy, I need my prompt to play, I don't need people to see my prompt in the log. I often need to see the ooc chatter, or just like talking in it, but it doesn't need to be in my log either, etc...

Posted: Wed Jun 25, 2008 4:46 pm

It's actually an interesting suggestion. I'll add a #GAGLOG command to the wish-list for a future version. It might actually be pretty easy to implement given the way that CMUD handles the log file. But I'm not going to get into complex substitute commands or anything like that. Just a command to prevent a particular line from being written to the log file is all that I'll probably do.

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

How about adding a #WRITELOG while your adding #GAGLOG?

Posted: Wed Jun 25, 2008 5:34 pm

Good idea :)

Edited: Love easy stuff like this. Both #gaglog and #writelog are in v2.29. Took about 5 minutes.

Wizard Joined: 26 Mar 2008 Posts: 1547

hahaha, awesome. But it would be neat to look into more complex log stuff in the future. However, this is awesome enough. Now I just need to figure out how to match my two-line prompt to be gagged. Very Happy

Adept Joined: 27 May 2008 Posts: 299

put $^ between the lines

Posted: Wed Jun 25, 2008 10:01 pm

Also, it's probably obvious, but in order to use the new #GAGLOG command, you need to make sure you have the preference enabled to Log *after* Triggers (since your #GAGLOG runs in the trigger).

And with #WRITELOG you should be able to do any complex stuff that you want now, especially given the power of the %subregex function for modifying text.

Wizard Joined: 26 Mar 2008 Posts: 1547

Adept Joined: 27 May 2008 Posts: 299

um, its out. and I guess it depends on if your writing it in zscript or regex

Wizard Joined: 26 Mar 2008 Posts: 1547

regex

Posted: Wed Jun 25, 2008 11:00 pm

Personally, I'd prefer to use a multistate trigger than a two-line pattern. It looks like:

#trig {line 1} {#gaglog} "" {regex}
#cond {line 2} {#gaglog} {regex|within|param=1}

Also, anyone know whether #gaglog leaves a blank line in the log file or not? I haven't had time to test that yet.

Wizard Joined: 26 Mar 2008 Posts: 1547

No, it doesn't. It would be nice if it did, but it wouldn't be nice in all instances. For instance, in my two line prompt I would only want 1 blank line. Maybe if it took an argument so you could tell it whether or not you wanted a blank line left behind.

Also, Fiang, I'm not confident enough with multi-state triggers. I'm sure there's ample reading on them?

Posted: Thu Jun 26, 2008 12:50 am

Yes, there is.

The #gaglog command doesn't leave blank lines, so you can gag whatever you want. If you want a blank line, you can use #writelog to print a space or something. Using Toxic's idea with a multiline pattern won't work anyway because only the most recent line is removed from the log, same as with #gag. You can't just use #gaglog;#gaglog to mimic the same behaviour as #gag, either.

Wizard Joined: 26 Mar 2008 Posts: 1547

I'm not sure how write log works. Can I put an argument after it and have it write to the log?

Posted: Thu Jun 26, 2008 9:41 am

Yes, that's the whole point. You do #writelog Hello! and Hello! appears in the log file.

Wizard Joined: 26 Mar 2008 Posts: 1547

Yeah, that's what I thought at first, then I thought it was using Zhiroc's idea. Which is, you take a pattern that is gagged, and have #writelog and it writes it to the log, even though it's gagged.

Adept Joined: 27 May 2008 Posts: 299

You can do that with #WRITELOG %trigger

Wizard Joined: 26 Mar 2008 Posts: 1547

Hmm, writelog didn't add the %cr I asked it to

Adept Joined: 27 May 2008 Posts: 299

Posted: Thu Jun 26, 2008 3:27 pm

Giving a separate ID for a trigger state is pointless, as well. You might find that #writelog " " or something works better, too - I'm not sure how or if #writelog handles %cr. It's something to try, anyway.