 |
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
 Posted: Sun May 01, 2011 2:46 pm
Does Gaglog work on "Log Commands"?
|
Another new, possibly interesting dilemma comes up with the "Log Commands" feature in relation to #GAGLOG. I have "Log Commands" toggled on, but, there are SOME commands I'd rather not have logged. I figured a simple oninput trigger would suffice to gag those specific things, but they're still being logged, even with the trigger. I'm unsure of how log commands works, but perhaps it doesn't fall under #gaglog's domain?
|
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4702
Location: Pensacola, FL, USA
|
Posted: Sun May 01, 2011 3:43 pm
|
It should... i think there is an option in preferences that determines if logging i done before r after your triggers fire.
Zugg: Is there a way to set the trigger priority for logging? Say if we want certain changes of the mud output to show but not others, for whatever reason.
(Be a good way to keep cap&gag text still in the log, while still seeing your brief version of things.) |
|
_________________
Discord: Shalimarwildcat |
 |
|
|
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
Posted: Mon May 02, 2011 4:52 pm
|
I already have "log after triggers" or #GAGLOG wouldn't work on anything, presumably. It doesn't seem like #GAGLOG works on Log Commands.
I could turn Log Commands off and just make a trigger that logs everything I input, with a filter in that trigger to take out what I don't want, but maybe there can be some consideration for a way to filter what Log Commands logs? |
|
|
|
|
|
|
|
