 |
Ceres
Wanderer
Joined: 25 May 2006
Posts: 88
|
 Posted: Thu Jul 17, 2008 2:28 pm
CMUD [2.32] #MXPTRIG and %trigger
|
If a trigger fires from an #MXPTRIG tag the predefined variable %trigger is not set which limits the usefulness of this command.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Jul 17, 2008 4:35 pm
|
That is because %trigger only contains the line that fired the trigger for normal triggers. MXP Triggers are handled specially and are processed before the full line of text is received. The MXP Trigger is fired as soon as the MXP closing tag is received, which is often before the rest of the line is received.
So, there is no way to support %trigger for MXP triggers, sorry.
Perhaps you can tell us more about what you are trying to do with the MXP trigger. There is probably another way to do it. |
|
|
|
|
Ceres
Wanderer
Joined: 25 May 2006
Posts: 88
|
Posted: Thu Jul 17, 2008 6:50 pm
|
No worries.. I was going to use a MXP tag trigger to send the line to a 'Tell' window.
I have already scripted the same functionality using an ansi trigger. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Jul 17, 2008 8:21 pm
|
Is the MXP tag buried in the middle of the line, or does it properly surround the text you want to capture? The %0 argument within an MXP trigger contains the "contents" of the MXP tag. For example, if the MUD sends the text:
| Code: |
| <tag>This is the text</tag> |
and you set up an MXP trigger for the "tag", then %0 would contain "This is the text". |
|
|
|
|
|
|
|
