Find a WarcraftLogs report you'd like to analyze, copy the URL (or just the report code) into the input box, and press the 'Get' button.
Select the specific fight you'd like to analyze, and press the 'Analyze' button. Analysis may take up to a minute to complete.
Stat Weights
Calculates your stat weights, based on your actual healing done and healing patterns over the course of the analyzed fight. As Tranquility overheals in all reasonable circumstances, it is explicitly disregarded by the calculation.
The 'Relative Stat Weights' section shows the weights normalized so Intellect is always 1. The 'Rating for 1% Healing' section shows the amount of additional stat rating you'll need in order to boost your total healing by 1%.
Crit's stat weight does account for the crit healing bonus on Drape of Shame. However, Warcraftlogs contain no information on the player's race, so we can't also account for the Tauren crit bonus because we don't know if the player is a Tauren. Instead, both values are calculated, and the Tauren's stat weight is presented in parens.
Haste (HPM) accounts only for the additional healing per cast you get from haste (because HoTs tick faster). This is the more valuable stat for raids, where mana is an issue. Haste (HPCT) also accounts for the additional maximum throughput you get by being able to cast faster. This could be more valuable in M+, where you are less likely to OOM.
The Versatility value accounts only for the bonus healing granted. The (w/ DR) value also counts damage reduced due to Vers as additional healing done. The w/ DR value moderately overvalues Vers because unlike healing it can't overheal, but it still can be interesting to see.
Average Mastery Stacks
Calculates the average number of mastery stacks you benefit from when healing. This average is weighted with respect to healing done (before mastery).
The 'All Healing' entry counts the average over all your healing (and absorbs), even ones that don't benefit from Mastery like Ysera's Gift or Prydaz. This can give you a good feel for how much Mastery is contributing to overall healing done.
The 'Druid Spells' entry counts the average only over the healing done by spells that can benefit from Mastery. This is likely the right number to enter into a spreadsheet for calculating stat weights.
Spell Mastery
Calculates how much of your healing can be attributed to each of your HoT's mastery stacks. For example, if you took the talent Cultivation, healing from your other spells on a target with your Cultivation on it will heal for more because of the extra mastery stack provided by Cultivation. This is healing that wouldn't have happened had you not specced Cultivation, but it's completely invisible in basic logs. This analyzer seeks to remedy the issue.
Results are presented as a percentage of your total healing done over the encounter, including from trinkets / legendaries. 'Direct' healing amounts should correspond to the numbers you see in the WCL report itself.
Oh, and yes: Frenzied Regeneration does count towards mastery for whatever reason.
Mastery Procs
Calculates healing attributable to certain mastery stacks, presented as a percentage of total healing. Current Mastery procs supported are the T19 2 piece bonus and the Jacin's Ruse set bonus.
Expected AB Uptime
Uses your actual ability cast times / targets to calculate your expected Ashamane's Rip uptime. Expected uptime is contrasted with actual uptime from logs. Results are presented for every enemy target you used Rip on. All uptimes are a percentage of the total fight time.
The Ashamane's Bite artifact talent can be frustrating because while skill definitely contributes to uptime, the largest factor in an individual fight is pure luck. This analyzer seeks to remove luck from the equation when analyzing logs by letting you see your expected uptime based only on your ability timings.
This analyzer should also allow you to rage at your poor proc luck, something which would no doubt otherwise be in short supply.
SHORTCOMINGS: This analyzer is still experimental, and the code is a mess and needs to be refactored. Calculated Rip uptimes are very slightly off from the WCL reported values and I'm not sure why. Simulated Thrash / Swipe / BrS can proc AB on multiple targets while this can't actually happen in practice. Swiping multiple targets with Rip is uncommon enough that this shouldn't make a noticable difference in sim.
Simulator currently assumes you have t19-2pc, which is an ok assumption but it will need to be updated to check in the future. Simulator currently assumes you don't have t20-4pc, which is a bad assumption. Also needs to be updated.
UI Layout inspired by the Restoration Druid Legendary Analyser, which is another great WCL analysis tool for Resto Druids.
Source available here, and you can contact me with questions or suggestions on Discord : Sref#3865