Zugg Software :: View topic

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

I am looking for some ideas here. I have my Scripting Impairments Package which only does stuttering. Now I want to also make it a hissing scripts and and old English script.
Now my thought was if I could create a button that has a toggle for the type of speech impairments and somehow to from the command line it knows which alias to run and put in front of the text.

This may not be possible, so for you gurus what do you think and how would you do it. I want to make it modular enough and show of the CMUD capabilities. Wink

Posted: Thu Oct 21, 2010 9:31 pm

Your speech scripts will be changing what is sent to the mud depending on what you type right, like if you type: say I'm stuttering now. The script will convert "I'm stuttering now" into a something else and send it?

If I understand you right you want to end up with a button that will chose one of the X number of speech packages to use? It seems to me like you could set up the module to have the button, then a class for each of the speech packages. You could make the button be multistate, where when one of the packages is selected from the drop down menu, that class is enabled and all others are disabled. So as long as each script knows if you type "say whatever" you want to use the type of speech that package will cause this method should work. I could just not be understanding the question right though.

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Fizgar,
That is exactly what i was thinking, but my question is can you send the alias from the command line without typing it. So let's say I have the stutter class enabled with the button.
I type in the command line the following: say This is the stutter script.
And what is sent to the mud is: stutter say This is the stutter scirpt.
The alias runs and you get: say Th-th-this is the st-st-stutter s-s-script.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Feel like reworking your aliases into functions? I would do that, perhaps retaining the use of aliases for when the user wants to send something from the commandline manually (the aliases would now call the function, however).

Once the functions are working like they should, I'd also create a command-line trigger for your generic speech commands. This would cover the "natural" use of MUD speech, giving you a chance to determine if one/any of the speech functions needs to be used.

A menu button (a multistate is probably similar enough in function that the choice is purely a preferential one) would then serve to let the user pick and choose. Each option caption could incorporate variables to show the on/off state, or if you have lots of screenspace you could make a long main-button caption to show which options are active.

Personally, however, I would probably use a clickable MXP link menu in a user-created window that includes space for a nice always-viewable list. Lots of buttons tends to make for slower scripting due to all the screen-refreshing. Might not be a concern with just one script with a handful of buttons, but with dozens of scripts it gets real laggy for me.

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Err, what's the "it" part? To convert your STU alias to a function, you just create a new Function and paste your alias code there (where you use #SEND, change it to #RETURN or optionally put a #RETURN "" at the end). Any further changes are independent of the conversion from alias to function and would perhaps work equally well if you stayed with the alias. Should you move to a function, however, if you decide to keep the STU alias the new code would then be:

#SEND @stutter(required parameters) <-- use this if you changed #SEND to #RETURN

#CALL @stutter(required parameters) <-- use this if you did #RETURN "" instead

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Matt, I am trying change the script over to a function and it works kind of. Here is the function:

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

You'll need a #noinput command, else you'll get doubled commands sent to the game. That probably won't fix the infinite loop, so try unchecking the Trigger on Trigger option.

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

#oninput I thought that when you choose Command Input type trigger it would make it an oninput trigger. Can you help me understand.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Here's a couple of examples:

#oninput {^test$} {#send look}

#oninput {^test$} {#noinput;#send say test}

The first example should result in two commands being sent to the game--"test" and "look"--while the second example should only result in one command being sent--"say test". This is because command input triggers don't do a single thing with the original command that fires them.

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Okay. I had it correct but the removed the trigger on trigger for oninput trigger. Here is the code, but for some reason it is sending it twice.

Posted: Fri Oct 22, 2010 4:46 pm

You need to add the #NOINPUT command to your Command Input trigger to prevent the original command line from being sent to the MUD.

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Posted: Fri Oct 22, 2010 5:07 pm

Yes, "Command Input" means it is an #oninput type. So that is correct. You should add the #NOINPUT command at the end of your trigger after the #send command. Did you click on the link for #oninput and read the help file?

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Hey I just noticed something. As part of my script you can do emphasis say for instance:

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

If you insist on using parentheses then you have no choice but to put quotes around them to avoid CMud from using them as evaluation.

If you stop using parentheses then you can use some other delimiter so that the user only has to type the text used instead of both the text and the syntax:

stu say, while smiling, You make me laugh.

You will need to remove your named parameters and rework how you assign your variables, and if the game requires the emphasis to actually have () around it you will need to provide for that as well. Here's an example to help you see what I mean:

Posted: Mon Oct 25, 2010 5:06 pm

To deal with the parenthesis, mark your Command Input trigger as a "Trigger on Prompt" and turn off the "Trigger on Newline" option. Making the Command Input trigger a "prompt" trigger will cause it to fire *before* CMUD parses the command line (and converts the parenthesis).