Zugg Software :: View topic

Beginner Joined: 26 Dec 2005 Posts: 21

This should be a simple question, but the solution eludes me:

I have enter.wav, a sound file I want to play when zMUD sees the text "Comm: Preloading data for:". How do I set this trigger up? Where do I set it up? Treat me as a complete newbie, please.

Wanderer Joined: 14 Jul 2004 Posts: 83

Beginner Joined: 26 Dec 2005 Posts: 21

Thanks. :)

For clarification: I don't know WHERE to put things like #play enter.wav and #trigger.

Wanderer Joined: 14 Jul 2004 Posts: 83

Correct the directory name and file name to match your file information then enter it on the command line of your main zmud window. It will create the trigger for you.

Beginner Joined: 26 Dec 2005 Posts: 21

I had tried that too, and just tried it again, but for some reason it just sends #trigger {Comm: Preloading data for:} {#play c:\directory name\file name.wav} to the MUD, with the MUD's response of Huh?

Beginner Joined: 26 Dec 2005 Posts: 21

...rather, I did that with the appropriate directory/file.

Wanderer Joined: 14 Jul 2004 Posts: 83

It sounds like you have parsing turned off. Hit ctrl/r to turn parsing back on and try again... only when you're entering the information, change the "c:\directory name\file name.wav" to match the directory and file you're wanting to play when the trigger fires.

Beginner Joined: 26 Dec 2005 Posts: 21

I verified that parsing is on just now. Thanks for your help so far. Still stuck on this one. The directory information is all set but the command skips zMUD and goes directly to the MUD.

Beginner Joined: 26 Dec 2005 Posts: 21

For the record I'm putting this into the command line: #trigger {Comm: Preloading data for:} {#play enter.wav}

I've read that zMUD looks in the sound folder for the MUD in use, so the full directory isn't necessary. Still, I think the main issue here is the fact that zMUD won't make the trigger at all. I'm receiving the MUD's own response output of Huh? - it looks as if zMUD doesn't catch the pound sign zMUD-based command for some reason.

Posted: Sun Jul 05, 2009 1:14 am

If parsing is on and that 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.