Skada is a modular combat meter for damage, healing, threat and other encounter statistics.
Main features
- damage and healing meters.
- current fight, last fight and overall segments.
- multiple display modes and configurable windows.
- chat reporting and data reset tools.
How to use
Open /skada, create the meter windows you need, and switch modes between damage, healing, threat or other modules.
Practical tip
Configure the addon around decisions you actually make during play. A small, readable setup is usually more useful than enabling every optional alert, panel or statistic. After changing settings, reload the UI if the build requires it and verify that the information remains visible at your normal resolution and UI scale.
Reading Skada data
The supplied Skada archive includes the Interface 30300 Skada Improvement module and the classic Skada components used for combat reporting. Skada collects combat-log events into segments and presents actors, spells and totals in movable windows. Depending on the modules present, the useful views include damage, healing, deaths, threat, interrupts and dispels.
Open a Skada window and choose the current segment or a saved encounter segment. Select an actor to drill into spells and targets, or switch to deaths and interrupts when investigating a failed attempt. Reset or start a new segment at the pull so trash and boss data are not mixed. A raid leader can compare the same phase across attempts, but the numbers still depend on combat-log range, pets, absorbs and the modules loaded on that client. The WotLK package is not the current Retail Details replacement; enable only the Skada modules included in this archive.
From total to cause
Use the top-level window to select a segment, then click an actor or spell to move from a total to the cause. For a failed attempt, the deaths and interrupts views are often more useful than the damage ranking. Reset between unrelated pulls and keep the same segment definition when comparing attempts. Skada reports events received by the client; it does not recover events outside combat-log range or infer a mechanic that the log does not contain.
