UI escape sequences

Many UI elements that display text on the screen support a special escape sequences starting with the pipe character (|).

Coloring

 * |cAA RR GG  BB : Sets text color. Text following this escape sequence will be drawn in this color. Each pair of digits represents a color value (plus the alpha value, however the alpha value is currently ignored and should always be FF) as a hexadecimal number.
 * |cFFFF0000 - Red text
 * |cFF00FF00 - Green text
 * |cFF0000FF - Blue text
 * |cFFFFFF00 - Yellow text


 * |r: Ends the current color change. The color will return to the previously set color (e.g. |cFFFF0000 Red |cFF00FF00 green |r and back to red. |r).

Links

 * |Hlinktype:linkstring|hLinktext|h: for hyperlinks: when linktext is clicked, a widget handler is invoked.


 * |Hitem&#x003A;ItemString|hLinktext|h: for Item Links (ItemString must be the full ItemString, ie. d:d:d:d:d:d:d:d style)


 * |Henchant&#x003A;EnchantID|hLinktext|h: for Enchant links


 * |Hplayer&#x003A;Name:ChatID|hLinktext|h: for Player links (Click to whisper, CTRL-click to select and shift-click to do a /who Name. ChatID here refers to spam reporting


 * |HBNplayer&#x003A;??|h: Placeholder

/run print("\124Hunit:"..UnitGUID("target")..":"..UnitName("target").."\124h["..UnitName("target").."]\124h")</tt>
 * |Hunit:GUID:Name|hLinktext|h</tt>: for Unit Links. Implemented by the Blizzard CombatLog


 * |Hquest&#x003A;QuestID:QuestLevel|hLinktext|h</tt>: for Quest links.


 * |Hspell&#x003A;SpellID</tt>: for spell links.


 * |Htalent&#x003A;TooltipID:Points</tt>: for talent links.
 * TooltipID seems to be a global talent id, not quite sure how it's encoded or stored.
 * Points is how many points you've spent in that talent, zero based (3 points in it means '2') and -1 for no points.


 * |Htrade:TradeSpellID:CurrentLevel:MaxLevel:PlayerID:Recipes|hLinktext|h</tt>: for Trade links. Note that the TradeSpellID corresponds to the spell id from the spell found in the spellbook (e.g. "Cooking" has id 33359). See also TradeSkillLink.
 * CurrentLevel: the current level of the player in the given trade-skill
 * MaxLevel: the highest currently achievable skill (an apprentice will have 75 as max level, a grand master 450)
 * PlayerID: API_UnitGUID of the player, stripped of all the leading zeroes (unlike GUID for Achievement below where the leading zeroes are included).
 * Recipes: Base64-encoded list of learned recipes.


 * |Hachievement:AchievementID:GUID:Completed:Month:Day:Year:Unknown1:Unknown2:Unknown3:Unknown4|hLinktext|h</tt>: for achievement links.
 * GUID is the API_UnitGUID of the player, without the starting '0x'.
 * Completed is 0 for uncompleted achievements and 1 for completed.
 * Month/Day/Year is the date the achievement was completed or 0 if not completed. Year is -1 if not completed.
 * Unknown1-4 are unknown fields. They're often 0 for non-completed achievements.


 * |Hinstancelock:guid:mapID:difficulty:defeatedEncounters|hName|h</tt>: Instance lock links
 * GUID: Unit GUID of the player
 * Map ID: self explainatory - 650 for ToCh, 649 for ToCr ETC.
 * Difficulty: Difficulty id of the instance lock (heroic/nonheroic, 10/25)
 * Defeated Encounters: Bitfield indicating the encounters that have been defeated. E.g. 7 means that the first 3 encounters have been done but the subsequent ones have not.

Grammar

 * number |1singular;plural;</tt>: Will choose a word depending on whether the digit preceding it is 0/1 or not (i.e. 1,11,21 return the first string, as will 0,10,40). Note that unlike |4 singular and plural forms are separated by semi-colon.
 * |2text</tt>: Before vowels outputs d' (with apostrophe) and removes any leading spaces from text, otherwise outputs de  (with trailing space)
 * |3-formid(text)</tt>: Displays text declined to the specified form (index ranges from 1 to ). Processed by C code, data used for parsing isn't available to UI, all events fire with the data already processed.
 * number |4singular:plural;</tt> -or- number |4singular:plural1:plural2;</tt>: Will choose a form based on the number preceding it. Client locale dependant. More than two forms (separated by colons) may be required by some locales (i.e. Russian requires 3 forms), if too many forms provided they are ignored, if needed form isn't provided empty string will be used instead. Note that unlike |1 singular and plural forms are separated by colon. (added with 2.4.2)

Textures

 * |TTexturePath: size1 : size2 : xoffset : yoffset |t</tt>


 * |TTexturePath:size1:size2:xoffset:yoffset:dimx:dimy:coordx1:coordx2:coordy1:coordy2:red:green:blue|t</tt>
 * Will insert a texture into a font string. Parameter  size2 </tt> is optional (see below). The offsets are optional and will shift the texture from where it would normally be placed. <tt> TextHeight </tt> is based on size of the font used - this is used to automatically scale icons based on the size of the text.
 * <tt> size1  == 0;  size2  omitted: Width = Height =  TextHeight </tt> (always square!)
 * <tt> size1  > 0;  size2  omitted: Width = Height = size1 </tt> (always square!)
 * <tt> size1  == 0;  size2  == 0  : Width = Height =  TextHeight </tt> (always square!)
 * <tt> size1  > 0;  size2  == 0   : Width =  TextHeight ; Height = size1 </tt> (size1 is height!!!)
 * <tt> size1  == 0;  size2  > 0   : Width = size2 *  TextHeight ; Height =  TextHeight </tt> (size2 is an aspect ratio and defines width!!!)
 * <tt> size1  > 0;  size2  > 0    : Width = size1 ; Height = size2 </tt>
 * <tt>xoffset yoffset:</tt> Offset for the rendered image, in pixels
 * <tt>dimx dimy:</tt> Size of the source image, in pixels
 * <tt>coordx1 coordx2 coordy1 coordy2:</tt> Coordinates that identify the left/right/top/bottom edges, in pixels
 * <tt>red green blue:</tt> Color values in the range 0-255 that are used to tint the texture
 * Notes:
 * When you need to display square icon in the string (spell/item icon), use only <tt>|TTexturePath: 0 |t</tt>
 * When you need to display rectangular image in the string (Blizzard logo), use aspect ratio version: <tt>|TTexturePath: 0 : aspectRatio |t</tt>
 * To prevent potential abuse, raw texture links cannot be sent to other players.


 * <tt>{tag}</tt>: This markup offers the only way to send textures to other players. There is however a limited set of parsed values. Currently you can only send Raid target icons using texture tags:
 * {star}, {rt1} - [[Image:IconSmall RaidStar.png]]
 * {circle}, {rt2} - [[Image:IconSmall RaidCircle.png]]
 * {diamond}, {rt3} - [[Image:IconSmall RaidDiamond.png]]
 * {triangle}, {rt4} - [[Image:IconSmall RaidTriangle.png]]
 * {moon}, {rt5} - [[Image:IconSmall RaidMoon.png]]
 * {square}, {rt6} - [[Image:IconSmall RaidSquare.png]]
 * {cross}, {rt7} - [[Image:IconSmall RaidCross.png]]
 * {skull}, {rt8} - [[Image:IconSmall RaidSkull.png]]
 * Note that the named raid target markup (star, circle, diamond, etc.) is localized, so {star} for example will not be replaced by the star texture on a german client, but {rtX}-style markup works on all clients.

Other

 * <tt>|K[gsf][0-9]+|k[0]+|k</tt>: New in 4.0 - Represents a Battle.net friend's name. The 3rd character indicates given name, surname, or full name. The number which follows it represents the friend's Bnet Presence ID. The zeros between the |k form a string of the same length as the name which will replace it. E.g. if your first name is John and your presence id is 30, your given name (John) would be represented by the string <tt>|Kg30|k0000|k</tt>.


 * <tt>|n</tt>: Newline, if the widget supports it.


 * <tt>||</tt>: Output "|" regardless of if whatever follows it looks like a valid escape.


 * <tt>|</tt>: A "|" followed by something that is not a valid escape sequence will be displayed as-is.


 * <tt>%T</tt>, <tt>%F</tt>: Name of the player's target and focus, respectively; can be used in macros (eg. "Sheeping %T"). Outputs <tt>&lt;no target&gt;</tt> or <tt>&lt;no focus&gt;</tt> if nothing is targeted.

Gotchas
If you are using an in-game text editor, it is not wholly unlikely that the editor is trying to being "helpful" by replacing "|" with "||" for you without you seeing it. If you are trying to use escape sequences and just keep getting pipe chars, that's why. Try using <tt>"\124"</tt> instead of <tt>"|"</tt>. 124 is the ascii code escape for the pipe character, and will work regardless of what your editor is trying to do.