Understanding Attributes
Attributes are used to modify the behavior, appearance, and functionality of markers, trails, and categories.
TacO attribute names are case-sensitive. Our documentation reflects the attribute names exactly as TacO would expect for non-exclusive attributes.
Exclusive Attributes
Be mindful that there are some attributes exclusively supported by Blish HUD.
Blish HUD exclusive attributes will be silently ignored in TacO. That means that any behaviors or other effects they would normally provide in Blish HUD will not occur at all in TacO. Packs using Blish HUD exclusive attributes will still otherwise run in TacO without issue.
If you need assistance or would like to provide suggestions for future attributes in Blish HUD, join our Discord channel!
| Attribute | Summary |
|---|---|
| Bounce | Allows a marker to "bounce" or rise up out of the way when triggered. |
| CanFade | Allows a marker or trail to ignore fade features such as those which hide trails around the player or between the user and their camera. |
| Cull | By default markers and trails are rendered without culling meaning that both sides are rendered at all times. Alternative culling settings allow you to enable culling for one side or the other. For example, a trail can be made to be visible when viewed from below. |
| Festival | Hides the marker or trail if one of the specified festivals is not active. |
| InvertBehavior | If enabled, the behavior filter is inverted. By taking advantage of duplicate GUIDs on a second marker you can have markers which are displayed only while the triggered marker is hidden. |
| IsHidden | Prevents the category from being displayed in the category menu. |
| IsWall | If the trail should be displayed on its side as a wall instead of a flat trail. Good for indicating a boundary. |
| MapType | Hides the marker or trail if the current map is not one of the specified map types. |
| Mount | Hides the marker or trail if the player is not currently riding one of the specified mounts. |
| Occlude | Allows a marker to occlude the 3D Pathing elements behind it. If enabled, the marker does not require a texture. |
| Profession | Hides the marker or trail if the player is not currently one of the specified professions. |
| Race | Hides the marker or trail if the player is not currently one of the specified races. |
| Rotate | Allows you to statically rotate a marker instead of it automatically facing the player. Value is in degrees. Rotation is applied first to the x axis, then to y, and finally to z. |
| Schedule | Hides the marker outside of the specified schedule. Good for showing markers only during their associated scheduled meta event, day of the week, etc. All scheduling is based on UTC. |
| Script | Allows you to trigger Lua functions or determine if a marker is visible using a Lua function. |
| ShowHide | Allows showing or hiding a specified category when triggered. Similar in behavior to the Toggle attribute. |
| Specialization | Hides the marker or trail if the player is not currently one of the specified specializations. |
| Tip | Allows you to display a tooltip on markers on the minimap or categories in the category dropdown. |
Attribute Prefixes
Blish HUD supports prefixed attributes. This is to say that any attribute prefixed by bh- will be stripped of its prefix and used as a normal attribute. This allows you to create markers, trails, and categories that differ in functionality depending on if the pack is loaded by Blish HUD or TacO. This works because TacO will ignore these attributes entirely as they don't match any of its supported attributes.
Example:
<MarkerCategory name="overlay" displayname="You're using TacO!" bh-displayname="You're using Blish HUD!" />
When using prefixed attributes, ensure they are specified after the attribute you wish you override. Anything that inherits attributes can still override a prefixed attribute if it itself defines its own overriding attribute, prefixed or not.
Attribute Values
As the marker pack format is XML based, there are limitations to what characters can be used as an attribute value. The table below indicates the values that must be escaped in order to be considered proper XML. Both Blish HUD and TacO have forgiving XML parsers which will do their best to interpret the value, but not all libraries or overlays are capable of this. For the best result, you the table below when using any of the specified characters.
| Character | Escaped Value |
|---|---|
< | < |
> | > |
& | & |
' | ' |
" | " |
| New Line | 
 |