Zugg Software :: View topic

Apprentice Joined: 14 Sep 2007 Posts: 167 Location: aztx

This is what i have:

Posted: Tue Sep 18, 2007 7:29 pm

Your second trigger is creating the loop. You're saying if %line=@prompt, to gag it, and say @prompt. In my opinion, that's a bit redundant, since you're just repeating the same exact line. What is it you're really trying to do? There's no reason to gag the line only to show it again. But for the purpose of your question, I'll show you how to make it work.

#TRIGGER "gag" {^~<(*)~> } {#IF (%line=@prompt) {#T- {gag};#gag;#sayp @prompt;#T+ {gag}}

That'll turn off the trigger, finish the commands, and turn the trigger on again. By the way, the $ is to match the end of a line. But it can be tricky:

Apprentice Joined: 14 Sep 2007 Posts: 167 Location: aztx

Yes it's a bit redundant, because it's a newline, and sayp being that it is prompt.. this way your prompt never moves.
so what would a trigger do if it was just #trigger {$} {pattern}. Similiar to #trigger {$} {pattern} {command input}. (%null?)

Having a line break after every line that is displayed as: @prompt(*), that is whenever it's not only your prompt on that line. May help. I had #t- and #t+ in my trigger but it would still fire every line, having a break line after the prompt may
work after i change the code a bit, as the problem here for me seems to be #sub, #sayp, and pattern matching in my opinion.
What I am trying to accomplish is a "fixed prompt".

Examples.. Note: triggers are turned off to show output from the Mud
Before you hit enter you have:

(your prompt here) on the prompt line.

Posted: Wed Sep 19, 2007 11:55 am

Ah, so your MUD doesn't automatically print your prompt after every block of text appears, and you want to create a trigger that'll do what for you?

If it were me, I'd capture and gag the prompt (it doesn't have much info on it) and then use gauges to display the health and v - whatever that is - info.

Also, about your #trigger question - the commands you have there make no sense. The syntax of the trigger command is #trigger id pattern command class options. The commands aren't optional, so #trig {$} {pattern} makes no sense. #trig {$} {pattern} {command} will probably create a trigger whose id is "$".

If all you want to do is trigger on blank lines (perhaps to gag them) then all you need is

#trig {$} {#gag}

If you explain what you were trying to do with your command, we'll be able to tell you how to do it.

Apprentice Joined: 14 Sep 2007 Posts: 167 Location: aztx

In short I am making this script:

Apprentice Joined: 14 Sep 2007 Posts: 167 Location: aztx

This is what I have so far. many times I have felt I was almost there, I don't know to what benefit #cond could give me..

Posted: Wed Sep 19, 2007 3:27 pm

Well, based on what you've stated in this post, it appears that you're wanting to get rid of the blank line beneath the prompt. Understandable - I prefer to have an extra enter, though. :) I have everything in gauges with my prompts gagged. It makes for better eyesight. ;)

However, the following may be the best way to handle it.

#TRIGGER {^~<(*)~>} {}
#COND {$} {#gag} {Within|1}

So it'll check for a blank line received directly below the prompt and gag it. It'll still display your prompt, but instead of

< 1 2 > l

Blah

You'll get

< 1 2 > l
Blah

I hate not having zMUD in front of me to test my own interjections, but if it's wrong, I know someone will correct it. :P

Charneus