Zugg Software :: View topic

Beginner Joined: 21 Mar 2009 Posts: 12

There is no way to change screen width to 0 in this mudd. I can't seem to get the triggers to work without capturing everything in the game or just one line from the tells.

(*) tells you, "It's still not working for you?"
3920/3920h 445/490m 93xp >

You tell (*), "Not really"
3920/3920h 445/490m 93xp >

Those are the two things I am trying to capture and that prompt always follows. Is there a possible way I can make it capture everything to that prompt and then not capture afterwards?

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

give us an example of a multiline tell.

Beginner Joined: 21 Mar 2009 Posts: 12

(*) tells you, "Usually saying something like that to a guy when they
really arent pay attention will work"
3920/3920h 445/490m 93xp >

Like this one?

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

You can use a multistate trigger. Multistate triggers are essentially multiple triggers combined into one setting that CMud internally controls the order of (this means the trigger will never mess up unless something did not match at all).

Beginner Joined: 21 Mar 2009 Posts: 12

So this is what I have so far, Everything seems to work beautiful expect when it captures it only captures my prompt. While @TellMsg captures the whole tell correctly. Just not in the Tells window. I am sorry if I am just doing it incorrectly

Sorcerer Joined: 15 Apr 2011 Posts: 809

Change the #CAP Tells line to #WINDOW Tells @TellMsg.

Beginner Joined: 21 Mar 2009 Posts: 12

That Actually delays the message I receive, till the command prompt pops again. And it also doesn't display the name or in the correct font or color sadly.

Posted: Wed Mar 28, 2012 5:06 pm

Wizard Joined: 22 Mar 2007 Posts: 2320

To get the name and capture colors, make it:

Beginner Joined: 21 Mar 2009 Posts: 12

To clarify the font and color of the tells received is different in the #window Tells than it is in the game. Not a major problem but the two major issues with it is, it doesn't multiline capture.

(*) tells you, "Happy, happy, happy, i'm so happy. City is doing well, can
actually help out with the city."

That tell became
Aurina tells you, "Happy, happy, happy, i'm so happy. City is doing well, can

Also the prompt with my health, needs to pop another time after the one following the tell for it to go to the window. As if it's delayed.

Also @shalimar your trigger actually gives me a ton of errors one about GAG being incorrect characters the incorrect paraphrases.

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

Whoops, set the trigger options for the second state of the trigger to Trigger on Prompt (or perhaps both Trigger on Newline and Trigger on Prompt). Triggers are created with only the Trigger on Newline option set by default, and what this means is that the trigger will suspend execution until the next newline character is received. Most lines sent from the game have this character at the end of their lines so triggers matching on them execute immediately; prompt lines usually don't, and usually incorporate the newline sent with the user command.

Your trigger may also be stuck on this second state, so before testing it out you will want to use the #STATE command from the command line to set this trigger to state 0.