 |
snoogans
Novice
Joined: 28 Oct 2001
Posts: 43
Location: USA
|
 Posted: Wed Nov 19, 2003 1:22 pm
problem with logging to a file
|
I have a trigger that logs output to a file, when the output is from a mud the trigger works fine, when I #echo the output it triggers on it gives the opened/closed file messages even though the option is off, anyone know why its behaving this way? using v6.16 if that makes a difference.
|
|
|
|
|
Cuttlefish
Apprentice
Joined: 28 Oct 2003
Posts: 164
|
Posted: Wed Nov 19, 2003 4:50 pm
|
It sounds like I bug. I recommend upgrading to the current version.
|
|
|
|
|
LightBulb
MASTER
Joined: 28 Nov 2000
Posts: 4817
Location: USA
|
Posted: Wed Nov 19, 2003 6:10 pm
|
Even though what option is off?
Triggers fire on
a) MUD output
b) #SAY output
c) #SHOW output
d) #ECHO output
e) command input to MUD
As far as I know, only the last has a preference which allows it to be disabled. The behavior you cite, triggering in response to an #ECHO, is normal. |
|
|
|
|
|
|
|
