Standard MXP tags

Eg.

<bold>This is in bold</bold> and this isn't.

Eg.

<b>This is in bold</b> and this isn't.

Eg.

<underline>This is underlined</underline> and this isn't.

Eg.

<u>This is underlined</u> and this isn't.

Eg.

<italic>This is italic</italic> and this isn't.

Eg.

<i>This is italic</i> and this isn't.

Eg.

<em>This is emphasised</em> and this isn't.

eg.

<color fore=cornsilk back=blue>This is cornsilk on blue</color>

or, to achieve the same effect:

<color cornsilk blue>This is cornsilk on blue</color>

You can specify just one or the other:

You can also use RGB codes:

The colour names and RGB use is described on MXP Colours.

Colour names are the same as for <color> above.

Style can be one of;

• blink
• italic
• underline
• bold
• inverse

eg.

<font color=cornsilk,bold,italic back=blue>This is bold italic cornsilk on blue</font>

The colour names and RGB use is described on MXP Colours.

Creates an underlined hyperlink that the player can click on to either go to a web page, or send an email. The HREF argument must start with either "http://" or "mailto:".

eg.

<a href="http://www.gammon.com.au">Go to Gammon Software Solutions Home Page</a>

<a href="mailto:nick@some-email-address.com">Send an email to Nick</a>

Creates an underlined hyperlink that the player can click on to carry out some action.

The default behaviour is for the action to be sent to the MUD (eg. "go north"), however if PROMPT is specified the action is placed in the client's command window for modification before sending (eg. "tell Nick ...").

This is a very powerful feature, which allows MUDs to provide hyperlinks for clicking on, rather than players having to memorise lots of commands.

In the simple case, <send> without arguments merely sends whatever is between <send> and </send> to the MUD. eg.

<send>West</send>

In the above case, clicking on the hyperlink sends "West" to the MUD.

You can send different text to what the player sees by using HREF. eg.

<send href=West>West - The Second Floor Landing</send>

In this case, the player sees "West - The Second Floor Landing" as a hyperlink, however if they click on it the word "West" is merely sent to the MUD.

You can set up a "mouse-over" hint that appears if the player moves the mouse over the hyperlink. eg.

<send href=West hint="Go to the second floor landing">West - The Second Floor Landing</send>

In this case, the player sees "Go to the second floor landing" in a little popup window if they move the mouse over the hyperlink.

You can also create a pop-up menu that appears if the player right -mouse clicks on the link. You do that by separating the various possible words to be sent to the MUD by the vertical bar character - "|".

If the player left-mouse clicks the first item on the list (the default) is automatically sent. This will also appear in bold in the menu if you right-mouse click.

By using HINT you can also specify the text of each item in the menu. If you also want a mouse-over hint then you need to provide that first. For all this to work properly, the number of hint items should be equal to, or one greater-than, the number of commands to be sent. eg.

There is currently a limit of 30 items that you can put into the menu. Additional ones will be ignored.

By using the keyword PROMPT you can cause the text to be not sent immediately, but rather to be put into the client's command buffer. This would be useful for things like player names, where you might want to send them a "tell" or similar.

This example also illustrates use of the special entity "&text;". If you use that inside an element's arguments, the word "&text;" is replaced by the text between <send> and </send>.

What this means is that if the player clicks on the menu link with the right-mouse button they would see (in this example):

• Tell Gweonnyn something
• Send mail to Gweonnyn
• Whisper to Gweonnyn

Because the player's name is not inside the definition itself, then you can simplify life for yourself by defining your own element, like this:

The element definition only needs to be sent once, at the start of the session.

Now, all you have to do (for example, in a WHO list), is use the newly defined tag "player" like this:

eg.

This is one line</br>
This is another one.

This is a "command" tag, thus there is no </br> tag.

Sends the current player's name to the MUD.

The player name is defined in the "Connecting" configuration screen.

This is a "command" tag, thus there is no </username> tag.

This is intended for the MUD server to automatically find out your character's name at logon time.

Same as <username>.

Sends the current player's password to the MUD.

The password is defined in the "Connecting" configuration screen.

This is a "command" tag, thus there is no </password> tag.

This is intended for the MUD server to automatically find out your character's password at logon time. The password must be sent in the first 10 lines of text sent to the MUD, otherwise this command is disabled as a security precaution.

Same as <password>.

This is a "command" tag, thus there is no </version> tag.

This is a "command" tag, thus there is no </reset> tag.