Gagging multiple lines

Posted by DragonCharmer84 on Fri 15 Dec 2006 07:13 AM — 4 posts, 18,059 views.

#0
I've got a problem. I've gagged a few things, and I end up getting spammed by stuff that looks like this:

3877h, 2114m exdb-
3877h, 2114m exdb-
3877h, 2114m exdb-
3877h, 2114m exdb-
3877h, 2114m exdb-
3877h, 2114m exdb-

Is there any easy way I can fix this with settings? If not, I was thinking that it out to be possible to set up a scripted trigger that would gag repeats of the same prompt. As a sidenote, the numbers and the letters in front of the dash should all be variables to make the trigger as flexible as possible.
I've tried to find information on such a script. Unfortunately, being very computer illiterate I tend to spend many hours trying to problem solve the simplest of scripts.
The expert programming advice of this board's members is hearby requested.
Australia Forum Administrator #1
One approach would be to simply gag all prompt lines, in the process copying the information on them to the status line, so you can still see your hit points, etc.
USA #2
I have run across a similar issue myself. I know it could be done as you mentioned, Nick, however, I don't want that line to be gagged if hp < 1000. Is there a gag/omit type function that I could add to my trigger body? if %1 > 1000 then _______
Thanks.
Amended on Wed 20 Dec 2006 02:16 AM by Artel
Australia Forum Administrator #3
What you can do is make two triggers, the first with a lower sequence, that enables or disables the second one depending on some condition. The condition might be health low, same as previous prompt, and so on. This might look like this:


<triggers>
  <trigger
   enabled="y"
   keep_evaluating="y"
   match="*h, *m *-"
   send_to="14"
   sequence="90"
  >
  <send>
EnableTrigger ("prompt_trigger", %1 &gt; 1000 )
</send>
  </trigger>

  <trigger
   match="*h, *m *-"
   name="prompt_trigger"
   omit_from_output="y"
   sequence="100"
  >
  </trigger>
</triggers>


In this example the prompt is first tested in trigger sequence 90 (the first one), and this enables or disables the second trigger depending on a test (health > 1000).

If enabled, the second trigger omits the line from output.