 |
Draconar
Beginner
Joined: 26 Dec 2005
Posts: 21
|
 Posted: Sat Jul 04, 2009 8:02 pm
Command line won't take #triggers, passes them to MUD
|
Parsing is on. I'm creating a sound trigger (see other thread) with the following: #trigger {Comm: Preloading data for:} {#play enter.wav}
Instead of creating a trigger, it goes directly to the MUD and returns a "Huh?". Can anyone help me?
(PS - forgive me if this seems like an unnecessary second post from my other thread, but I know I'm more likely to get an answer with a single post than a thread with a number in it) |
|
|
|
|
Taz
GURU
Joined: 28 Sep 2000
Posts: 1395
Location: United Kingdom
|
Posted: Sun Jul 05, 2009 1:16 am
|
If parsing is on and that command is going direct to the mud then the only other thing I can think of is that you have turned the command char off in the special characters preference panel or changed it to something else.
|
|
_________________
Taz :) |
 |
|
|
Draconar
Beginner
Joined: 26 Dec 2005
Posts: 21
|
Posted: Sun Jul 05, 2009 2:04 am
|
Everything's in working order. Thanks for your help guys. :) I must've disabled the special character because I thought it would interfere with ascii art elements or something.
|
|
|
|
|
|
|
|
