MTS draft 8.2a &ndash Version 1.1

This is a fairly large document and is mostly geared toward scripters that will be implementing theme engines. A smaller file more geared toward themers is also available at the MTS home page. Check it out!

Contents

• Terminology
• Chapter 1 - The MTS Concept
• Chapter 2 - How MTS Works
• Chapter 3 - Basic Format for an MTS Theme File
• Chapter 4 - Format of Events and Raws in MTS Theme Files
• Chapter 5 - Variables Used in Events and Raws
• • All-purpose variables
  • Variables used in events
  • Variables used in raws
  • Variables for Whois, Whowas, and Who events and raws
  • Variables for DNS events
• Chapter 6 - MTS File Format - Settings and Information
• • Color options in an MTS file
  • Nicklist options in an MTS file
  • Font options in an MTS file
  • Image options in an MTS file
  • Miscellaneous options in an MTS file
• Chapter 7 - MTS File Format - Events and Raws
• • Text IRC events
  • Basic IRC events
  • Non-IRC events
  • Whois and Whowas raws and events
  • Other raws
• Chapter 8 - MTS File Format - Sounds (Optional)
• Chapter 9 - MTS File Format - Schemes (Optional)
• Chapter 10 - A Sample Theme File
• Chapter 11 - Scripting Notes
• Chapter 12 - Standard MTS alias names
• Chapter 13 - Future Expansion
• Change Log
• Credits

Terminology

• MTS is mIRC Theme Standard- this document, and any script that uses the concepts within to handle themes.
• script refers to a script that handles theme output &ndash in other words, the theme engine.
• theme refers to an actual theme or theme file that has been loaded.
• event is something that occurs on mIRC that can have it's output reformatted.
• raw is a special type of IRC event referred to by a number from 001 to 999.
• variables are used to store information relating to an event or raw, to later be formatted by the theme.

A MTS script will take IRC events and raws, store relevant data in variables, and use the information in a theme to format them for display.

Chapter 1 - The MTS Concept

Why a theme standard? How is this different from other "standards" people have tried to come up with in the mIRC community?

A theme standard is needed in the mIRC community. There are many themes out there for various scripts, and no way to simply use them in another script. If a themer creates a theme using a standard, then it can be loaded in all scripts supporting that standard- allowing all scripts and users to benefit from the talents of themers.

This standard was created from the input of many scripters and themers, many who have already planned to implement the standard.

Most scripters are aware that there are basically two different ways to implement a theme system in mIRC, although there are a few variations of each type.

The first type of theme is the "scripted" theme system, where basically a script file is /loaded by a theme alias, and this new script file contains all of the code to handle the text processing for the script. The script simply calls aliases in the theme file to handle each event.

Pros: This is very flexible, since everything is scripted.
Cons: It is more difficult for a themer to make a scripted theme because they must know at least a bit of mIRC scripting. It is very difficult to write scripts that modify these themes, such as theme editors. The method used for these aliases also differs wildly from script to script.

The second type of theme is the "keyword" theme system. This is implemented by having a text file or ini file that is read into the script in some manner. The theme system then replaces keywords in the theme lines with correct values whenever an event occurs, and displays that.

Pros: Simple and easy to edit for themers. Theme editors can be made easily for these types of themes.
Cons: You are limited in your flexibility, since there is no actual scripting in the theme files. You're also limited to what the script allows in a theme, and you cannot (usually) do multi-line displays or other fancy themes.

MTS is a combination of both types, for maximum flexibility. It is what you might expect if you started with a text theme system, and then added support for scripted aliases on top.

Chapter 2 - How MTS Works

A basic run down of what happens during an event that an MTS script wants to format or "theme":

1. The script catches the event in mIRC, using a script event or raw
2. The script checks the theme file to see what the theme wishes to do for this event
   If the theme has a simple line of text for this event:
   1. The script replaces special codes (variables) in the line of text, such as nickname, channel, colors, etc.
   2. The script then displays the line of text to the screen

   If the theme instead refers to an alias name:

   1. The script sets a number of mIRC %::variables to values such as nickname, channel, colors, etc.
   2. The script sets %:echo to the command it wishes to use for theme output, such as "/echo -t $chan"
   3. The script calls the theme alias, which formats and displays output using these variables

Chapter 3 - Basic Format for an MTS Theme File

All MTS theme files should have an extension of .mts. MTS files are simple text files, where each line contains one event, raw, setting, or other piece of theme-related information.

You may have blank lines, and any line beginning with a semicolon (;) will be treated as a comment and ignored.

Before any settings, the first line in your MTS file must be "[mts]". This is related to scheme usage (chapter 9). Even though scheme support is optional and not part of every theme, all themes must have the [mts] line to mark the main MTS data section of the file.

Themes may refer to external files such as images or a .mrc file. These files must be in the same directory as the theme .mts file. For example, ultra.mts refers to ultra.mrc and BK.png. These files would be in the same directory as the ultra.mts file.

It is highly recommended that .mts files be put in their own subdirectory so that supplemental theme files do not conflict with other themes.

A script may load a theme and process in any way it desires, as long as it achieves the effects detailed in this document. Some behaviors or events may not apply to a given script and can be ignored. A script may also voluntarily ignore certain features, such as images, if desired, but this may diminish the value of some themes.

Chapter 4 - Format of Events and Raws in MTS Theme Files

Each event or raw has one line in an .MTS file. The line starts with a code that signifies the event or raw. The remainder of the line is the text displayed for that event, but will contain special variable <codes> that will get replaced when the actual event occurs. For example:

TextChan [<nick>] <text>

This is a basic theme line for text in a channel window. When it is displayed, the script will replace <nick> with the nickname of the user, and <text> with what they said.

Some (or all) events may instead refer to aliases or lines of code. For example:

TextChan !Script theme.chantext

This tells the script that, when a text event happens for a channel, to call the /theme.chantext alias (in the theme's .mrc file, specified by the Script line - see chapter 6). When this alias is called, it will then handle the echoing of the text, using the %:echo variable (see chapter 5), as well as theme variables that have already been set by the calling script. For example, %::nick will be the nickname, and %::text will be what the text was from the event. Notice how these correspond with <nick> and <text> above &ndash this is true for all theme variables.

A special variable, %:echo, contains the command the alias should use to display it's text. A short example alias that could be part of a theme's script file:

alias theme.chantext {

  %:echo ( $+ $lower(%::nick) $+ ) %::text

}

These aliases are stored in a separate .mrc file (this file is mentioned on the SCRIPT line in the .mts file &ndash see chapter 6 for details). When the script sees the "!Script" prefix, it should take the remaining text and run it as if it were an alias name, but it should $eval() it first, so that it runs as an actual line of mIRC code (see chapter 9 for details). In other words, something such as "!Script %:echo %::text" should be allowed to work.

Note that "!Script" by itself should not be an error- it should simply "do nothing", essentially preventing any output.

This covers the basics of how a script should handle a theme: check the line, and either replace <variables> and display it, or set %::variables and call the listed alias. Note that when replacing <variables>, you should also replace <lt> and <gt> with < and > so a theme can use those characters (see chapter 9 for details).

Chapter 5 - Variables Used in Events and Raws

The variables listed here should be set by the script before calling a theme alias. Note that all variables, other than %:echo and %:comments, have a corresponding <variable> that should be replaced when processing normal theme lines. Some variables may not apply to a given event or raw, of course. Some variables are listed multiple times when they have different uses in different situations.

All-purpose variables

These must be set in all events and raws.

Variables used in events

Variables used in raws

Note that if a raw only uses ONE of %::value, %::nick, or %::chan, then the script is allowed to place the SAME VALUE in all three, for simplicity. A theme should not rely on this behavior.

Variables for Whois, Whowas, and Who events and raws

Note that there is no Who event, just RAW.352, but it is listed as Who below for clarity. A script is only required to use these variables in Whois/Whowas/Who events and raws &ndash they do not need to work in other events and raws.

Variables for DNS events

Other than %::nick, a script is only required to use these variables in DNS events &ndash they do not need to work in other events and raws.

List of all variables without duplicates:

Chapter 6 - MTS File Format &ndash Settings And Information

.mts files contain more than just events and raws &ndash they contain other lines with information and settings. These settings are covered in this chapter.

Remember that all entries in an .mts file take up one line. Actual events and raws are in the next chapter. Also note that the setting names are not case sensitive.

Note that MTSVersion and Name are the only required fields. The [mts] line is also required. Everything else is optional, and a script should use default values or no values for missing items.

Informational items in an MTS file:

Color options in an MTS file

These items allow a theme to change mIRC and theme colors.

BaseColors help keep a theme "modular" &ndash if you use them throughout a theme, you can then change the colors of your entire theme just by changing one or two color lines (more details in chapter 9 - schemes).

Scripts may also choose to use the colors in BaseColors for their own specialized echos and displays. For that reason, the order of the four BaseColors is recommended to be as close to the following as possible:

Text color, Nickname color, Text highlight color, Bracket color

These are merely recommendations &ndash a theme can use these for anything it wishes. The reason for the recommendation is so a theme contains reasonable colors that a script can use for it's own purposes as well. All four colors should ideally produce readable text on the selected background color.

Nicklist options in an MTS file

The first set of items are single numbers representing the color to use for nicknames in the nicklist. Each line either corresponds to a channel mode (OP, etc.) or a special status, such as IRCOP. Not all scripts will use all colors (or even use nicklist colors at all) and remember that themes do not need to include all colors. A script should ideally not use any colors that are not present. In other words, if a user is both an OP and an IRCOP, but the theme does not define an IRCOP color, use the OP color.

For scripts that can use /aline for custom windows (such as multiserver scripts), MTS provides for you to be able to change the mode character and color for each type of user. Keep in mind that CLineCharRegular probably wont use a character, but if the theme wants one, then you should accomodate for it. The syntax is the exact color and mode character to be prefixed before the above CLine colors. Note that, like the other CLine lines, you should not include the color control code itself (Ctrl+K).

Example:

CLineCharOwner    12.

CLineCharOP       11@

CLineCharHOP      10%

CLineCharVoice    09+

CLineCharRegular

Font options in an MTS file

These options define the fonts to use for windows. A script may ignore these but the theme may not look correct. Some fonts apply to multiple windows or types of windows. Each font line is a font name, followed by a comma and a font size. The size should be a positive or negative number. To make a font bold, put ,B after the font size.

Image options in an MTS file

These options define image files to use for backgrounds and other areas of mIRC. A script is free to ignore some or all of these. The first word of each line defines the way to apply the background &ndash center, fill, normal, stretch, tile, or photo. This is followed by the filename of the image. The ImageButtons item does not have a style. The ImageToolbar and ImageSwitchbar should include a style (although mIRC currently only supports the fill style for these, this may change in the future).

Miscellaneous options in an MTS file

Chapter 7 - MTS File Format - Events and Raws

All possible theme events, and all common raws, are listed below. A script is not required to use all events, but most should be used for full effect. Note that if an event or raw is missing, a script should use some sort of default display. A missing event or raw does NOT mean to hide that event or raw.

Whenever an event or raw refers to a variable in %::var format, remember that the same value will be in <var> format when processing normal theme lines. Note that only some %::vars are mentioned- others like %::nick are assumed.

Text IRC events

Basic IRC events

Non-IRC events

These events are not directly related to an IRC connection.

Whois and Whowas raws and events

/whois (and /whowas) replies are handled a little differently in MTS. Each raw is called normally as expected &ndash and if this is enough for a script (displaying the /whois line-by-line) then nothing more is needed. Some themes, however, like to wait until the entire whois reply is collected and then display it, for formatting purposes. In this case, leave the /whois raws blank, and add Whois and Whowas events. These will be called after the data for a full /whois or /whowas is collected. Since a /whois may reply on multiple nicknames, this event will either be called right before the end of whois raw (RAW.318) or right before the start of the next whois (RAW.311). Most themes will use either the line-by-line raw method, or the Whois method &ndash but a theme is allowed to use both if it needs to for any reason.

If a theme does not have a Whois or Whowas event, then a script should use default /whois or /whowas behavior if the raws are also not present. Otherwise, hide output even if a specific /whois or /whowas raw is not found.

Note that any unrecognized raws seen between RAW.311 and RAW.318 should be treated as part of a /whois, and stored in or appended to %::text. This isn't a requirement, but suggested for ideal /whois operation (if not done, %::text will be blank in the WHOIS or WHOWAS event).

Other raws

This is not a comprehensive list of raws. ANY raw can be listed in a theme. Simply use RAW.nnn, where nnn is the three digit raw number. If a raw is not found, RAW.OTHER should be used, if present. If not, the script can display the raw however it pleases. If you wish to hide the output from a raw, you should just write "!Script" for the event, with nothing to run. This will essentially "do nothing".

Any raw not listed here should have $2 in %::nick and %::chan, $3 in %::value, and $3- in %::text if $2 is a nickname or channel, or $2 in %::value and $2- in %::text otherwise.

Note that if a raw only uses ONE of %::value, %::nick, or %::chan, then the script is allowed to place the SAME VALUE in all three, for simplicity. A theme should not rely on this behavior.

Chapter 8 - MTS File Format - Sounds (Optional)

This chapter describes a method of adding sound events to a theme. Support for this in a script is entirely optional. Scripts are encouraged to have their own sound events not listed here.

Sounds can be defined for events by simply making another line in the theme in the form of:

SndEventName filename.wav

"EventName" should match a MTS event or a mIRC event or command, if possible. An event that matches an IRC event affecting you should include the "Self" suffix. Some more commonly used sound events:

Ideally, the theme engine should determine the type of file the theme is trying to play (whether mid, mp3, or wav), and use the appropriate command. MTS does not standarize on a sound format. The simplest way to implement sounds is to add a line in /theme.text that checks for SndEventName and if it exists, play the sound. This will not catch many of the more common events, however, such as SndOpen or SndConnect. This is up to scripter preference.

Chapter 9 - MTS File Format - Schemes (Optional)

This chapter describes a method of supporting multiple color sets in a theme, hereafter referred to as "schemes". Support for this in a script is entirely optional. Themes do not need to contain any schemes.

The concept of schemes is to allow a theme to have a few things that change for each scheme, and let the rest remain the same across all schemes. Usually, the items changing will be Colors, RGBColors, and similar items, but this is not required. For example, a theme could contain a "red" scheme, a "blue" scheme, and a "green" scheme, which would contain different Colors lines; however, everything else would remain the same.

Schemes prevent having to create entire new themes just to change minor things such as colors.

For each scheme included in a theme, you need to add a SchemeN line to the main theme section, containing a description or name for that scheme. Then, add a [schemeN] section to the theme containing all items that are changing in that scheme. Here is a short example:

[mts]

Name This is an example theme.

MTSVersion 0.97



; (normal theme lines would go here)



; We include a default colors line for scripts that

; don't support schemes.

Colors 1,2,3,4,5,6,7,8,1,2,3,4,5,6,7,8,1,2,3,4,5,6,7,8,1,2



; These are our schemes

Scheme1 Red

Scheme2 Green



[scheme1]

; Colors for the 'Red' scheme

Colors 8,7,6,5,4,3,2,1,8,7,6,5,4,3,2,1,8,7,6,5,4,3,2,1,8,7



[scheme2]

; Colors for the 'Green' scheme

Colors 9,1,6,5,4,7,3,2,3,5,1,3,5,9,3,8,4,5,2,7,3,2,4,1,0,5



; We also change the prefix for this scheme

Prefix [*]



; (end of file)

When a script (that supported schemes) were to load this theme, it would first load everything in the [mts] section. Then, it would grab all of the scheme names from the SchemeN lines, and prompt the user for the scheme to load. Then, it would load the associated [schemeN] section, overriding anything in the original theme.

Note how the theme includes a Colors line in the main section. This is so that a script that doesn't support schemes will still load the theme properly.

Chapter 10 - A Sample Theme File

;------------ultra.mts-------------File start:-----

[mts]

Name Ultra

Author Variant

Email variant@variantrealities.com

Description Ultra is a lightweight, sleek, dark, blue theme.

Version 1.0

MTSVersion 1.0



Load <pre> Ultra theme loaded.

Unload <pre> Unloading Ultra theme...



Prefix 2ù12x2ù

Timestamp OFF

TimestampFormat [HH:nn]

ParenText (<c3><text><c1>)



Mode <pre> <c1>Mode(<c2><chan><c1>) [<c3><modes><c1>] by: <nick>

ModeUser <pre> <c1>Mode(<c2><nick><c1>) [<c3><modes><c1>]

Join <pre> <c1>Join(<c2><chan><c1>) <nick>[<c3><address><c1>]

JoinSelf <pre> <c1>Joined <c2><chan>

Part <pre> <c1>Part(<c2><chan><c1>) <nick>[<c3><address><c1>] <parentext>

Kick <pre> <c1>Kick(<c2><chan><c1>) <knick>[<c3><kaddress><c1>] by: <nick> <parentext>

KickSelf <pre> <c1>You were kicked by: <nick>[<c3><address><c1>] on <c2><chan><c1> <parentext>

Quit <pre> <c1>Quit <nick>[<c3><address><c1>] <parentext>

Topic <pre> <c1>Topic(<c2><chan><c1>) [<c3><text><c1>] by: <nick>

Nick <pre> <c1>Nick <nick>[<c3><addres>s<c1>] is now known as <newnick>

NickSelf <pre> <c1>You're now known as <newnick>

Invite <pre> <c1>Invite(<c2><chan><c1>) by: <nick>

ServerError <pre> <c1>Error: <c2><text>

Notice <c2>-<nick>-<c1> <text>

NoticeSelf <c1>ù<gt> <c2>-<nick>-<c1> <text>

Rejoin <pre> <c1>Rejoining <c2><chan><c1>...

TextChan <c4>[<c1><cmode><c3><nick><c4><gt> <text>

TextChanSelf 12[<c2><cmode><c2><me>12<gt> <text>

ActionChan * 03<cmode><nick> <text>

ActionChanSelf * 03<cmode><me> <text>



DNS <pre> <c1>Looking up <c3><nick><address><c1>...

DNSError <pre> <c1>Unable to resolve <c3>(<address>)<c1>.

DNSResolve <pre> <c1>Resolved <c3><address> <c1>to <c3><raddress>



TextQuery <c4>[<c3><nick><c4><gt> <text>

TextQuerySelf 12[<c2><me>12<gt> <text>

ActionQuery * <nick> <text>

ActionQuerySelf * <me> <text>

TextMsg <c4>*<c3><nick><c4>* <text>

TextMsgSelf 12-<gt> <c4>*<c3><nick><c4>* <text>



Ctcp <pre> <c2>[<nick>] <c1><ctcp> <c3><text>

CtcpSelf <c1>ù<gt> <c2><nick> 12<ctcp> <c3><text>

CtcpChan <pre> <c2>[<nick>/<chan>] <c1><ctcp> <c3><text>

CtcpChanSelf <c1>ù<gt> <c2><chan> 12<ctcp> <c3><text>

CtcpReply <pre> <c2>[<nick><chan>] <c1><ctcp> reply <c3><text>

CtcpReplySelf <c1>ù<gt> <c2><nick> 12<ctcp> [REPLY] <c3><text>



Whois <pre> <c1>Whois: <nick>[<c3><address><c1>] <realname>

Whowas <pre> <c1>Whowas: <nick>[<c3><address><c1>] <realname>



Echo <pre> <text>

EchoTarget <pre> [<target>] <text>

Error <pre> <text>



RAW.001 <pre> <c1><text>

RAW.002 <pre> <c1>Host: <c2><server> <c1>running version <c2><value>

RAW.003 <pre> <c1>Server created on: <c2><value>

RAW.005 <pre> <c1>Protocols supported by this server: <c2><text>

RAW.250 <pre> <c1>Total connection(s): <c2><value>

RAW.251 <pre> <c1>Users: <c2><users> <c1>Invisible: <c2><text> <c1>Servers: <c2><value>

RAW.252 <pre> <c1>Operator(s) online: <c2><value>

RAW.253 <pre> <c1>Unknown connection(s): <c2><value>

RAW.254 <pre> <c1>Number of channels formed: <c2><value>

RAW.255 <pre> <c1>Local clients: <c2><users> <c1>on <c2><value> <c1>server(s)

RAW.265 <pre> <c1>Local users: <c2><users> <c1>Max: <c2><value>

RAW.266 <pre> <c1>Global users: <c2><users> <c1>Max: <c2><value>

RAW.302 <pre> <c1>Userhost: <c2><nick><c1>[<c3><address><c1>]

RAW.315 <pre> <c1>End of /WHO list for <c2><chan>

RAW.324 <pre> <c1>Modes(<c2><chan><c1>) [<c3><modes><c1>]

RAW.332 <pre> <c1>Topic<c3>(<c2><chan><c1>) is <c3>'<text><c3>'

RAW.333 <pre> <c1>Set by: <c2><nick> <c1>on <c2><text><c1>.

RAW.341 <pre> <c2><nick> <c1>has been invited to <c2><chan>

RAW.352 <pre> <c1><cmode><c2><nick>[<c3><address><c1>] <c1><realname>

RAW.353 <pre> <c2><chan>: <c3><text>

RAW.366 <pre> <c1>End of /NAMES list for <c2><chan>

RAW.375 <pre> <c1>Message of the day:

RAW.372 <c3><text>

RAW.376 <pre> <c1>End of /MOTD command.

RAW.391 <pre> <c1>Date: <c2><value>

RAW.401 <pre> <c1>No such nickname <c2><nick>

RAW.403 <pre> <c1>No such channel <c2><chan>

RAW.404 <pre> <c1>Unable to send message to <c2><chan>

RAW.421 <pre> <c1>Invalid command:<c2> <value>

RAW.433 <pre> <c1>Nickname<c1>(<c2><nick><c1>) is already in use.

RAW.471 <pre> <c1>Can't join <c2><chan> <c3>(its full +l)

RAW.473 <pre> <c1>Can't join <c2><chan> <c3>(its invite only +i)

RAW.474 <pre> <c1>Can't join <c2><chan> <c3>(you're banned +b)

RAW.475 <pre> <c1>Can't join <c2><chan> <c3>(requires key +k)

RAW.482 <pre> <c1>You're not opped on <c2><chan>



RAW.Other <pre> <text>



Colors 1,3,9,5,0,10,3,10,10,12,10,15,5,2,6,0,3,2,12,5,15,1,15,1,15

RGBColors 255,255,255 28,29,89 0,0,168 0,147,0 255,0,0 127,0,0 156,0,156 252,127,0 255,255,0 0,252,0 4,107,191 61,165,250 52,55,170 255,0,255 127,127,127 210,210,210



; Regular text, nickname or channel, highlighted text, and brackets

BaseColors 10,11,14,2



CLineOwner 16

CLineOP 16

CLineHOP 15

CLineVoice 15

CLineRegular 46

CLineMe 16



ClineCharOwner 12.

ClineCharOP 12@

ClineCharHOP 18%

ClineCharVoice 34+



;You can use Font name,size (can be negative to correspond with mIRC

;font size dialog), B (for bold)



FontDefault IBMPC,13

FontChan IBMPC,13

FontQuery IBMPC,13



;Note that this theme does not use images, sounds, or schemes.



;------------ultra.mts-------------File end-----

Chapter 11 - Scripting Notes

Some important notes that apply to the script processing the theme files:

1. If using $replace to replace text, always replace <text> last, as it might contain other <codes>. <chan>, <ctcp>, <away>, and <realname> should also be replaced as late as possible, as they could also contain <codes>. Note that there are ways to process theme lines that do not have this limitation, but $replace is the simplest to code.
2. To allow the use of < and > in a theme line, a script must replace <lt> with < and <gt> with >. If using $replace, you should do this last- after everything else. It's possible for text already replaced to contain these values, but this is an unavoidable side effect- worse side effects could occur if replaced earlier.
3. When setting %::variables, you should probably use /set -u so the variables unset automatically. Be careful with /whois variables, as you will need to have them properly set for the final WHOIS event as well. (you may wish to store them in a more permanent location until that event)
4. When setting %::value, %::nick, and %::chan in a raw event, you can set all three to the same value if you're not sure which one applies for a given raw, as the important value is usually in $2. You SHOULD NOT do this for any raw that uses more than one of these variables. A theme should not rely on a script doing this.
5. <variables> are written with those characters to better support future expansion and avoid conflicts that could be caused by other methods of writing variables.
6. A script is free to define it's own <variables>, events, settings, etc. Other scripts should ignore lines in a theme file that it does not recognize. If possible, a script should also remove <variables> it doesn't recognize, but this is not required behavior.
7. Remember to reset /timestamp when mIRC starts, as otherwise any control codes will be removed.
8. When reading a !Script line, be sure to $eval() it, not just run the command as-is. This allows for single-line scripting without having to create separate aliases. For example, the following line should work, and will work properly if you simply use $eval() on the line when running it:

   TextChan !Script %:echo ( $+ $lower(%::nick) $+ ) %::text

9. When loading a theme, remember to use /loadbuf or some other method that only gets the [mts] section. Even if you don't actually support schemes, this will make sure you don't accidentally load settings from one.
10. If your script supports schemes, make sure to load the scheme lines (overriding any parts of the theme) before handing SCRIPT and LOAD lines, just in case they are changed by the scheme.
11. If your script uses %:comments, you should simply add them to the end of a normal text line. There is no <comments> code to replace. !Script should handle %:comments on it's own.
12. Regular expressions are very powerful. pai has come up with some really great example code on www.mircscripts.org/mts.php for speeding up your engines, so make sure to check it out.
13. If the channel or nickname returned from the server in an event is *, then the respective %::chan or %::nick should be set to $null.
14. In an event that sends text to multiple windows (such as Nick and Quit events), remember that the theme ENGINE is what does the looping, not the theme. The theme is only for formatting the text.

Order of items in a Colors line:

Background, Action text, CTCP text, Highlight text, Info text, Info2 text, Invite text, Join text, Kick text, Mode text, Nick text, Normal text, Notice text, Notify text, Other text, Own text, Part text, Quit text, Topic text, Wallops text, Whois text, Editbox, Editbox text, Listbox, Listbox text, Grayed text.

Default mIRC colors for a Colors line:

0,6,4,5,2,3,3,3,3,3,3,1,5,7,6,1,3,2,3,5,1,0,1,0,1,15

Default mIRC RGB values for an RGBColors line:

255,255,255 0,0,0 0,0,128 0,144,0 255,0,0 128,0,0 160,0,160 255,128,0 255,255,0 0,255,0 0,144,144 0,255,255 0,0,255 255,0,255 128,128,128 208,208,208

Important notes for theme files:

1. A theme alias should never use /halt. Use /return instead.
2. A theme alias should never modify (or unset) %::variables.
3. A theme file should not contain the mIRC ON LOAD and ON UNLOAD events. Use the MTS LOAD and UNLOAD events instead.
4. A theme that contains schemes should still include all settings (that it uses) in the main [mts] section, in case a script that doesn't support schemes tries to load it.
5. Remember to begin your theme with the [mts] line. This is required so that scripts can ease theme (and scheme) loading (even if your theme or script does not support schemes, all themes must still use this line for compatibility).
6. Do not worry about %:comments for normal text lines, but when you !Script an event, you should display it. This doesn't apply to raws.
7. Color codes should ALWAYS BE DOUBLE DIGIT. Although, most people still aren't used to doing this, so a theme engine should IDEALLY try and compensate for a theme that doesn't have double digit color codes and adjust accordingly.
8. !Script can not be used on ParenText, Prefix, Timestamp, or TimestampFormat (doesn't make sense to do this).
9. Themes should NOT USE /echo. They should only use %:echo.
10. <variables> are not to be used on !Script lines - use the correct %::variable instead.
11. An item in a theme file with no value, such as TextChan by itself, should do nothing. This especially applies to schemes - a scheme should have the capability to override (or remove) a setting in the main theme.

Chapter 12 - Standard MTS Alias Names

The following are required aliases for the theme engine. These are standardized so that addons can easily detect and use an MTS-enabled script.

/theme.text <event>

For calling the theme engine to do the theme text (variables already set)

$mtsversion

Returns the MTS version supported by the theme engine. Can be used by an addon to see if the script supports MTS.

$theme.setting(<setting>)

Returns a line from the theme without any processing.

The following are suggested aliases, that a script will probably want to have.

/theme.load

Loads a theme

/theme.scheme

Changes the scheme used in the theme

/theme.unload

Unloads a theme, returning to default display

Chapter 13 - Future Expansion

Some things that are not included that may be desired in future versions of MTS:

1. Line separator support - still not sure how this could be implemented in a theme engine. Recommend outputting - as the text for an event. Would be much easier if mIRC supported /linesep -f.

Change Log

9-27-2001: Draft 8.2a changes (Kamek)

No changes to the standard, only minor changes.

1. Changed format to HTML.
2. Fixed numerous small errors and typos.

9-24-2001: Draft 8.2 changes (Variant)

1. Fixed numerous typos, SELFNICK - NICKSELF, SELFKICK, etc. Also there were a couple instances of "send" left, they should have been "self."
2. Added quite a few more notes to chapter 11, both for scripts, and for themes. Please read it to make sure you haven't made any of these common mistakes.
3. Added <timestamp> and %::timestamp. Timestamp format is now on the appropriately named TimestampFormat line, and now Timestamp is simply ON or OFF.
4. MTSVersion is now 1.1 due to the <timestamp> addition.

8-20-2001: Draft 8.1 changes (Variant)

1. Typo <addres>s fixed in ultra.mts example theme.
2. Standardized on "Self" instead of "Send" &ndash no point in having both... CtcpSelf instead of CtcpSend, etc.

8-17-2001: Draft 8 changes (Variant)

1. Fixed typos, <b1> to <c1> etc...
2. Few other small typos.
3. Added some wording in some places.
4. Changed FontStatus to FontDefault.
5. MTSVersion is now 1.0.

This draft is largely unchanged from draft 7, but it needed a few small tweaks here and there to be called "final".

8-16-2001: Draft 7 changes (pai)

1. Some reformatting changes, not as extreme as blue-elf but should be a bit more readable now.
2. Changed "ChanText" to "TextChan". Similar changes for all Text and Action events. All of the events have similar naming schemes now.
3. Changed %::comments to %:comments. Single-colon variables are those that do not have a corresponding <variable> code.
4. Moved sound support to it's own chapter, clarified it as optional, added some recommended events.
5. Readded scheme support as it's own chapter, clarified it as optional.
6. Themes must contain an [mts] line to allow scheme support to function properly (even scripts/themes not using schemes should include this line).
7. Clarified BaseColors so themes have a better idea of which colors can or should go there. Sample theme now uses BaseColors.
8. Changed () addition to usage of ParenText and <parentext>. See %::parentext and chapter 6 for details.
9. Some other minor corrections.
10. MTSVersion is now 0.97. This draft will probably become the final draft except for grammatical fixes. MTSVersion 1.0 is still pending.

8-15-2001: Draft 6 changes (Variant)

Too many changes to mention all.

1. Naming for all events has been updated to be more organized.
2. .mts files are now recommended to be in the theme's direct