In Options > Sounds, the Startup, Connect, and Disconnect .wav files I selected from the Windows > Media folder on my Windows 10 PC were all accepted and work OK. The Beep sound, however, defaulted on the Windows Background file and refuses to accept the file I want for it, which is one of the generic ring files in the same folder. I got a little annoyed and decided to delete the Windows Background file, thinking the software might then accept something else. Instead, it's completely mute and beeping doesn't produce any sound no matter what I choose. This doesn't happen with MUSH or the other programs I've run. Any suggestions on a fix? I love CMUD but being alerted via beeping is essential as I'm often connected while at work and IAW.

the hashtag shortcuts as you call them, are the actual calls to the client commands.

If you want to create a trigger, you use the #TRIGGER command, same for #ALIASes and so on.

For the scenario you point out you would type the following on the command line:

#TRIGGER {You are being BEEPED} {#PLAY groovy.wav}

If you are entering it via the GUI, then you have to fill in the various text boxes.
On the pattern line you would stick:
You are being Beeped

Then down below you would need to ensure you are on the 'Script Text' tab and stick:
#PLAY groovy.wav

Right, I only use the GIU when creating aliases and triggers.

If I were doing it the way I usually do, I would’ve put the beep line in the pattern field and then entered #PLAY soundfilepath.wav in the first command line. I’m assuming this is not how this would be done since it would be asking CMUD to execute a play command rather than a basic one like ‘stand’ or ‘reply xyz’ etc.

I've got an unrelated question but didn't want to make a new thread for it. If anyone has any insight, feel free to contribute.

I was wondering if there's a way to see your session's password anywhere in the client, as it's currently set to a typical autologin that displays the character name but not the PW. When I open the autolog folder in the triggers medium (the tree), it simply shows the value as #PW. I don't remember the password and am concerned that if ever I can't use the software or accidentally delete the session or the package, I won't be able to log in again. Getting assistance for it within the world I play is slow and inefficient. The password isn't gagged when used in-game (that box is unchecked).

I'm trying to create a trigger that would activate something on my end in the session window.

The pattern is this:

[YOUR INFO]: %1 has just moved to %2!

Problem is the square brackets turn light green in the pattern light and the trigger doesn't work. Removing them doesn't, either. Brackets aren't by default special characters in this client. Any suggestions on how to deal with this wildcard?

This version doesn't even care who is doing the telling, or what the command is.
You don't have to match the entire line for a trigger to fire.
Ideally, you would want some form of error checking, or else you could end up being easily abused.

#TR {{@trustedPeople} tells the group '({@autoCommands})'} {%1}

This would be checking against two variable lists @trustedPeople and @autoCommands.
Nothing will happen unless you get a match on both of them, but you have to populate the lists yourself.

This version doesn't even care who is doing the telling, or what the command is.
You don't have to match the entire line for a trigger to fire.
Ideally, you would want some form of error checking, or else you could end up being easily abused.

#TR {{@trustedPeople} tells the group '({@autoCommands})'} {%1}

This would be checking against two variable lists @trustedPeople and @autoCommands.
Nothing will happen unless you get a match on both of them, but you have to populate the lists yourself.

Thanks for the response.

The safeguard against abuse is indeed the asterisk, as non-leaders don't generate that output when they tell something to the group. I therefore prefer to use the symbols than add people on a case-by-case basis.

e.g. *Royalty* tells the group 'sleep' would cause all non-leaders to sleep. I make all my triggers in the GUI menu as mentioned in earlier posts. Any suggestion on how to make this type of trigger work while using the format I mentioned? I'm sure it's a similar problem to the [] issue I described in another post.

The issue in your example is that you were trying to use the variable references (%1 %2 etc) in the pattern before they had had a chance to be defined. You need to use the pattern matching symbols I pointed out to you in earlier posts.

The issue in your example is that you were trying to use the variable references (%1 %2 etc) in the pattern before they had had a chance to be defined. You need to use the pattern matching symbols I pointed out to you in earlier posts.

Might I add that I changed ' (*)' to '(%1)' and your trigger worked like a dream. I know %w works as a variable, but I usually just use like %1 tells the group '%2' and that kind of thing seemed to work in, for example, ZMUD. Your replacement of the tildes is also different in that I had placed the first one before the asterisk and the second one after it, rather than both before the symbol. My apologies for returning to the GUI paradigm but I'm still too novice to understand making triggers with hashtags and brackets/parentheses.