Add-ons/Toolbox/Combat statistics
More actions
The combat tools in Toolbox provide a live HUD and detailed breakdowns of the combat information reported by the game's Lua API. They summarize the current fight or session; they do not perform combat actions or expose statistics the game keeps hidden.[1]
Combat HUD
Enter /toolbox combat to show or hide the HUD. Its standard measurements are:
- fight duration;
- damage per second for the last five seconds and the fight average;
- damage taken and healing per second;
- critical-hit percentage;
- avoided-attack percentage;
- up to eight selected character statistics.
Character statistics are chosen under Combat → Character stats on the HUD. Search by part of a name—such as resist, dodge, crit, or regen—then add a matching statistic. The current value appears in the search results and the list may be changed during a fight.
From chat, /toolbox stats <text> searches names. /toolbox combat stat add <name> and stat remove <name> change the HUD. The exact internal statistic name should be taken from the search result rather than guessed.[1]
In version 1.9.0, the HUD follows the global text size and line spacing on the General settings page. Its Size control under Combat is a percentage of that text size, with 100 percent matching it. The HUD retains its own background-shade control; like the other HUD strips, it starts at 60 percent shading.[1]
Combat Detailed
Hover the combat HUD or enter /toolbox combat detail to open the detailed window. It provides several complementary views:
| View | Contents |
|---|---|
| Damage by skill | Skills ordered by damage, with hit, critical-hit, and damage-over-time counts in tooltips |
| Timeline | The latest minute, with damage dealt above the baseline and damage taken below it |
| Healing | Effective healing and healing that was wasted as overheal |
| Targets | Damage to each creature and the recorded time required to defeat it |
| Damage types | Elemental or physical composition of damage dealt and received |
The dropdown switches between the current fight and the full Toolbox session. /toolbox combat detail session selects the session view. On Lua API 55 or later, Toolbox 1.10.0 adds a Party section with member damage, healing, rates, damage taken, deaths, and the last hits recorded before each member's most recent death. /toolbox combat reset clears both combat scopes; it is separate from the XP and Loot Tracker reset controls.[1]
Fight boundaries and interpretation
Toolbox builds its statistics from the combat events visible to the player through the supported API. Recent DPS uses a short rolling interval, while fight-average DPS uses the current fight's duration. Session totals can span multiple fights and therefore answer a different question.
Avoidance and critical percentages depend on events that the game reports. Target time-to-kill and per-skill results are summaries of observed encounters, not fixed creature or skill attributes. Comparing two builds is most useful under similar circumstances and over enough encounters to reduce the effect of a lucky or unlucky streak.
Block, parry, and dodge alerts
The Block, parry & dodge option displays the corresponding word briefly over the middle of the Toolbelt and can play a separate sound for each result. Enable it in Combat settings or with /toolbox combat shout on.
Text size, color, individual words, and sounds may be changed independently. The visual word requires the Toolbelt to be visible; the sound can still play when it is not. The Test control produces a sample without waiting for combat.[1]
Custom files named toolbox_block.ogg, toolbox_parry.ogg, and toolbox_dodge.ogg can be placed in the game's Lua folder. Sound configuration and volume are covered under configuration and backups.
Troubleshooting combat results
If the HUD is empty, confirm that Toolbox and the Combat feature are enabled, then begin a new encounter. Use /toolbox combat help for the installed version's syntax. When results appear inconsistent, note whether the window is showing the current fight or the whole session before resetting anything.
For persistent problems, record the Toolbox version from /toolbox version, the game build, and a short description of the encounter. See Toolbox troubleshooting for reload and package checks.