 |
Troublemag
Wanderer
Joined: 14 Jul 2004
Posts: 83
|
 Posted: Fri Mar 13, 2009 5:15 am
[CMUDPro 3.05] #mxp trigger issues
|
Here's what the trigger pattern should show:
| Code: |
<trigger priority="15120" id="1512">
<pattern>an ancient portal made of stone is here covered in grime</pattern>
<value>#mxp <send 'portal|portalqm|portaltear|portalkore|portal2rivers|portalblight|portalstedding|portallugard|portaltv|portalamador|portalaiel' 'Portal List|Quest Master|Tear|Caemlyn|Two Rivers|Blight|Stedding Shanjing|South of Lugard|Tar Valon|Amador|Aiel Waste'>Right Click to pull up a list of destinations</send></value>
</trigger>
|
In the XML tab of the editor, the < and > around the send and /send commands do not show as the symbols. Instead, the gt; and lt; (with & before each) have replaced them. Changing them to the < and > in the XML tab generates an error msg
| Code: |
| File: . Line: 3 Col: 21 Error: Expected String: '=' |
When the pattern is matched, the following is displayed instead of the hyperlinked command expected:
| Code: |
| <send 'portal|portalqm|portaltear|portalkore|portal2rivers|portalblight|portalstedding|portallugard|portaltv|portalamador|portalaiel' 'Portal List|Quest Master|Tear|Caemlyn|Two Rivers|Blight|Stedding Shanjing|South of Lugard|Tar Valon|Amador|Aiel Waste'> |
The first group in the send is a series of aliases to activate the portal stone.
This worked in 2.37 but not since upgrading to 3.05 |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Fri Mar 13, 2009 12:57 pm
|
Replacing < and > with the lt and gt codes is correct behaviour for XML - the <> characters do stuff in XML and, as such, can't be part of strings inside XML. It's the same with HTML. Changing them will cause an error, yes, which will cause you problems. CMUD's internal database will correctly store them as <>, don't worry.
|
|
|
|
|
Troublemag
Wanderer
Joined: 14 Jul 2004
Posts: 83
|
Posted: Fri Mar 13, 2009 2:35 pm
|
That's well and good, but the trigger isn't functioning correctly. When the triggering pattern is matched, the send command, with both strings, is displayed, not the clickable hyperlink.
|
|
_________________
CMUDPro 3.22 |
 |
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Fri Mar 13, 2009 3:01 pm
|
Go to your MXP options and check the Force Remote MXP option.
Wait, does the MUD use MXP or are you just using it for your own purposes? |
|
|
|
|
Troublemag
Wanderer
Joined: 14 Jul 2004
Posts: 83
|
Posted: Fri Mar 13, 2009 4:28 pm
|
The MUD is still very ROMesque and hasn't gone into using any MXP. They've added MSP at some point in the past, but it's not implemented well.
I'm using it for my own purposes and to add to a growing body of triggers and things I'm compiling for other CMUD users who play there. |
|
_________________
CMUDPro 3.22 |
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Fri Mar 13, 2009 8:13 pm
|
Yeah, Force Remote MXP. I tested your trigger offline and without it forced, I got the same result you did. Once I selected the option, it gave me the proper response.
|
|
|
|
|
Troublemag
Wanderer
Joined: 14 Jul 2004
Posts: 83
|
Posted: Sat Mar 14, 2009 1:29 am
|
Thanks! Works perfectly now.
|
|
_________________
CMUDPro 3.22 |
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Sat Mar 14, 2009 6:50 pm
|
This happens with just plain ol' mxp color tags too. For example, using mxp color tags in a #print command printed the whole thing to screen with tags and all instead of coloring said text.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Mar 16, 2009 5:36 pm
|
OldGuy2: I'll add that to the bug list. The #PRINT command is using the same low-level code as the #SHOW command, which causes CMUD to think the text is received from the MUD, and thus applies the remote MXP option to restrict MXP. Using the #MXP, #SAY, #ECHO, etc commands work fine. I'll fix the #PRINT command to also work in the next version. But this issue will always continue to happen if using the #SHOW command, since #SHOW is intended to mimic text received from the MUD.
|
|
|
|
|
|
|
|
