Register to post in forums, or Log in to your existing account
 

 Related 
Contents
MXP
  General MXP
  Elements
  Entities
  Tags
Related Links:
  Using MXP
General MXP [[zmud_General_MXP]] 
General MXP


This Preferences page contains options that control how the Mud eXtension Protocol (MXP) is used by zMUD. Most of these preferences are local to the current character.
 

Enable Mud eXtension Protocol
Globally enabled or disables the parsing of MXP commands from the MUD. Default is on.



Report <RELOCATE> Usage
Reports when the MUD uses the <RELOCATE> command to switch you to another server. Default is on.



Expand MXP tags in command line
Determines if Open MXP commands are allowed in the command line. Even if turned on, the < character in the MXP tag will need to be preceded with a ~ character to prevent zMUD from parsing the < character. Default is on.



Underline MXP links
Determines if hyperlinks created by MXP commands should be underlined. Default is on.

 User comments 
Anaristos: Sun Oct 21, 2007 8:11 pm    

Zugg wrote:
Category: zMUD Manual
Type: Reference

Index: zmud_General_MXP

Article Name: General MXP
Author: Zugg
Description:

>>Read Full Article
I would like to know explicitly where does one define the <!ELEMENT> items. Does one put them in an #ALIAS command, for instance? There is no specific Script Editor section for MXP definition entries. That is the question I think is being asked.
Fang Xianfu: Mon Oct 22, 2007 1:16 am    

You shouldn't need to use the !ELEMENT tag yourself. You can use MXP triggers to define your own commands to be executed when a particular tag is received. !ELEMENT is used by the server to define what a particular tag does. If the server hasn't defined it, use MXP triggers. If you must use it yourself, you can use the MXP command:

#MXP 1 <!ELEMENT etc etc
Anaristos: Mon Oct 22, 2007 9:51 am    

So what you suggest is that I use something like this, as an exaple, #TRIGGER {~<send goto} {cmds...}?
The reason I am going through all this is becasue I have a <send goto @loc>xxxx</send>. This won't work. It only works if I do it this way: <send>goto @loc</send>. I wanted to hide the location behind the room name; 'goto' is the alias that sends me there. But I am now forced to say 'goto roomnum'. With this in mind, I thought I could just write an !ELEMENT to take care of the problem. But a trigger makes sense.
Fang Xianfu: Mon Oct 22, 2007 1:54 pm    

<send 'goto @loc'> is what you're looking for. Send has more than one attrib, so it's important to use quotes.

Also, I meant an MXP trigger, not a normal one (which won't fire on the inline tags that aren't displayed). See the help.
Viewer Comments [4 - Post your comments]

Jump to:  

© 2009 Zugg Software. Hosted by Wolfpaw.net