Arundor2007-12-14 21:30:05
But is it from the Nexus Client or from MUSHClient? I've been working off the assumption that it's from the Nexus client. I thought so because you're also using Nexus targetting aliases.
But if the echo is from MUSHClient, then do as Mariello says and add your reject statement to the trigger that sends the echo.
EDIT: Actually, upon thinking this through a little, I realize I'm being dumb. Listen to Mariello or Ethelon.
But if the echo is from MUSHClient, then do as Mariello says and add your reject statement to the trigger that sends the echo.
EDIT: Actually, upon thinking this through a little, I realize I'm being dumb. Listen to Mariello or Ethelon.
Unknown2007-12-14 21:43:22
QUOTE(Ethelon @ Dec 14 2007, 09:29 PM) 466017
Issue is you are trying to make a trigger in a system that already has that triggered. For your to work, you need to set its priority lower so it fires first and possibly also enable it to continue to check for other triggers.
so how do i do that..
Arundor2007-12-15 01:19:56
There are a couple of ways to do this.
You already have a trigger that's echoing the text "REJECT", so one method is to search through your existing triggers, find that one, and add the "st target" line to it.
Another method is to create a new trigger, but if you do that your new trigger has to fire before the old one, and has to tell MUSHClient to keep processing so that the old trigger will fire too. For this method, make sure you select "Keep Evaluating" and give it a Sequence number below 100.
You already have a trigger that's echoing the text "REJECT
Another method is to create a new trigger, but if you do that your new trigger has to fire before the old one, and has to tell MUSHClient to keep processing so that the old trigger will fire too. For this method, make sure you select "Keep Evaluating" and give it a Sequence number below 100.
