-
-
Notifications
You must be signed in to change notification settings - Fork 11
behavior
Dade Lamkins edited this page Oct 15, 2022
·
1 revision
| Applies To | Blish HUD | TacO | |
|---|---|---|---|
| Markers | ✔ | ⚠ |
:::info
Behavior IDs of 100 and above are Blish HUD specific and will do nothing in TacO.
:::
Enables one of several predefined behaviors when triggered.
| Attribute | Data Type | Example | Default Value | Description |
|---|---|---|---|---|
| behavior | integer | behavior="3" |
0 | The behavior ID to use. |
| Behavior ID | Name | Behavior Summary |
|---|---|---|
| 0 | Always visible | The default - the marker has no behavior. |
| 1 | Reappear on map change | The marker hides when triggered until the map is changed. |
| 2 | Reappear on daily reset | The marker hides when triggered until daily reset (UTC+0). |
| 3 | Only visible before activation | The marker hides when triggered permanently. |
| 4 | Reappear After Timer | The marker hides when triggered until the time specified by the resetlength attribute. |
| 5 | Reappear on map reset | Does nothing. Not implemented by Blish HUD or TacO. |
| 6 | Once per instance | The marker hides when triggered until the instance is changed (a combination of map ID + shard ID). |
| 7 | Once daily per character | The marker hides when triggered until the next day but will show for other characters which have not triggered it yet. |
| 101 | Reappear on weekly reset | Resets on the weekly reset (Monday 7:30 UTC). |
Behaviors activate when they are triggered. Triggering a marker can be done by pressing the action key while in-range of the marker or by walking within the TriggerRange if AutoTrigger is enabled.
| Attribute | How |
|---|---|
| AutoTrigger | If enabled, the marker will trigger when the user enters within the TriggerRange. |
| TriggerRange | Determines the range necessary to trigger the marker with the action key. |
| ResetLength | For behavior 4, the time until the marker becomes visible again. |
| InvertBehavior | If enabled, the behavior filter is inverted so that the marker is only displayed after the behavior has triggered. |
Behavior states are tracked by a GUID. Between launches, this information is saved to disk.
| Overlay | File |
|---|---|
| Blish HUD | Stored in \Documents\Guild Wars 2\addons\blishhud\markers\data\states\timers.txt as guid,timestamp pairs. |
| TacO | Stored in activationdata.xml as XML |