Discord @garg DMed me letting me know he would like to help making this in any way he can.

Need the following information:

• List of all talents (see common/SPELLS_TALENTS
• List of all abilities for CPM_ABILITIES
• List of all abilities on the GCD for dead GCD time
• List of all cooldowns (healing buffs like Innervate, Wings)

HPal: During AM AoS it's interesting to see if you optimally used its effect. E.g. casting LoD is dumb.

DPriest: During Innervate you should spam stuff, I think PW:S (what you need to spam isn't as important as that you spam it).

This necessarily doesn't have to do with anything with your play style. Although it can be interesting to see how much healing this golden trait has contributed to.

What browser are you using?
Chrome Version 58.0.3029.110 (64-bit)

Link to an example report with the issue
https://wowanalyzer.com/#/report/xdYRBNc4WV78Z32p/1/Fizaw

Expected behavior
Mana tea shows "NaNK mana" when the spell is not used. SG also shows NaN stacks. Obvious fix is for me to actually use the spells, but in case I forget, the value of the variables that are used for storing those values should be initialized with a value of 0.

As a healer, check that potion of prolonged, potion of deadly grace or potion of old war was active on_initialize.

Also check that potion of prolonged, potion of deadly grace, potion of old war, leytorrent potion or ancient mana potion has been used in fight.

Otherwise add as suggestions.

Use this issue to discuss features for this spec. Let us know when you're working on something, or plan to work on something.

What browser are you using?
Firefox 53.03

Link to an example report with the issue
https://www.warcraftlogs.com/reports/L18cDC2tgKGpr4z7/

Expected behavior
Hey ! I was hoping to use your tool to analyse my log, but when I try to analyse it, I get "Invalid key specified" - I am an idiot, so very probable I'mn doing something wrong, any chance to enlighten me what :) ?

This includes:

• avgmastery stacks on all heals.
• mastery contribution per heals (especially cultivation + spring blossoms).

WCL shows a tooltip in the graph when hovering showing the mana level at that point and who died. Need to show something similar since users are used to having this information.

Might be hard to do since the mana info is fetched through a separate API call

Refreshing Atonement is usually inefficient.

Shouldn't be hard to do with a custom module listening to refreshbuff. Will have to calculate the expected Atonement duration before hand, but we already do that for one of the talents/legendaries increases Atonement duration so can steal that part. Keep track of 2 statistics: refreshesTotal and refreshesLong where refreshesLong ignores Atonements that would expire within 3 seconds.

The report could not be parsed. undefined is not an object (evaluating 'this.player.id')
For any russian nickname used in report for analysis.

This would be clean but would require either duplicating or passing along a lot of variables. Is it really worth it?

Health pot > warlock cookie this was changed, warlock cookies > health pot now. Check if there's a Warlock in the raid?
Health pot prior to death
Divine Shield prior to death?

It would be great to know how often Plea is being cast inefficiently (i.e. too many atonements up making Shadow Mend the better single Atonement applicator, or % of pleas cast while PW:S is up)

Add a button to "Show less" when expanding "Show more" and "Even more".

As an end user you are most likely only interested in knowing the new stuff for your class. Instead of having the user to search/filter that information (and developers tagging each line with the class name), instead add a changelog for each spec.

Should consists of two parts:

• Healing from spring blossoms
• Healing from increased mastery stack.

Also add suggestions and severity levels:

Example:
Severiity: Minor < 7%, Average < 5%, Major <3%
Suggestion text: "Your healing from Spring Blossoms could be improved, you may considering selecting another talent" x%

Track debuffs on enemies to see dot uptime and stuff. Would be nice to be able to see 2 kinds of uptimes:

• Total uptime where uptime of adds are multiplied (e.g. 100% uptime on 4 mobs = 400%)
• Fight uptime, where uptime is shown during the fight, e.g. if dots were never up on 2 targets at once and target A had 20% uptime and target B 60% it would show 80% uptime. If then there was a target C with overlapping uptime as B it would still be 80%.

Similar to what checkmywow.has.

The amount of healing you did with each ability (not including overhealing), weighed by total mana spent.
A tab for this for all healers would be nice,

Use this issue to discuss features for this spec. Let us know when you're working on something, or plan to work on something.

In order to put a focus on actual issues hiding minor issues behind a toggle by default could help.

For example when loading this log: https://www.warcraftlogs.com/reports/KWbk67LYTwQ29aPt#fight=18&view=events, the player Sèlnèsp has specID: undefined, which results in the following combatant object:

Object
error: true
sourceID: 7
timestamp: 11182049
type: "combatantinfo"
__proto__: Object

Look at the other spec implementations for inspiration.

I think Wasted Judgment of Light statistic would be interesting to see, especially to compare the "cast on CD and forget" and "cast only when debuff dropped" approaches; now that there's no cooldown on the JoL healing the wasted JoL should be low enough for tracking it to be negligible.

Would be great if anyone contributes this ;)

This necessarily doesn't have to do with anything with your play style. Although it can be interesting to see how much this golden trait has contributed to.

Should consists of two parts:

• Healing from cultivation
• Healing from increased mastery stack.

Also add suggestions and severity levels:

Example:
Severiity: Minor < 8%, Average < 6%, Major <4%
Suggestion text: "Your healing from Cultivation could be improved, you may considering selecting another talent" x%

Whenever reviewing PRs I see a bunch of code style choices that bug me, but I usually figure it's pointless to argue requiring changes just because of that. In order to reduce the inconsistencies I'd like to enforce some more eslint rules;

• prefer-const
• no-var
• react/prop-types
• one-var
• order of imports (global/local)
• require semicolons

I looked into using Prettier but it's pretty opinionated in the wrong way. For example it would reformat stuff to this:

const something =
  <div>Hello</div>;

In the first place this should be single line and then it would be ok. But if it was too long because for example the JSX was much longer, then it should be wrapped in parenthesis:

const something = (
  <div>Hello</div>
);

The reason for this is that it is consistent with requiring parenthesis when returning JSX;

return (
  <div>Hello</div>
);

and it makes sense linguistically (you wouldn't put a comma on the next line) and is easier to follow; when I see const something = ( I know the line is to be continued on the next line. Without parenthesis the JSX is just floating somewhere. The same goes for this:

{condition &&
  <div>
    Hello!
  </div>}

I looked into prettier-eslint, but ESLint is currently unable to add back the parenthesis after Prettier removed it, so that doesn't solve it. Ternaries are also messy.
Any solution with Prettier seems to be sub-optimal because of these wrongly opinionated issues, so even though CRA suggests using it instead of stricter ESLint rules, I reckon it is not a viable alternative at this time.

This will probably require ejecting, but I did that in the past and it's not that big a deal. The nice thing is that I'll also be able to remove .env again since the docs for that state it's recommended not to commit it.

Warn on low WG consumption levels.
Warn on low throughput

This legendary is a little bit more complex to calculate throughput.

Use this issue to discuss features for this spec. Let us know when you're working on something, or plan to work on something.

Use this issue to discuss features for this spec. Let us know when you're working on something, or plan to work on something.

Will get soon closed in favor of individual issues and milestones (i just need to create all the issues).

See: https://github.com/WoWAnalyzer/WoWAnalyzer/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20%5BElemental%20Shaman%5D

Rotation-TODO

Lightning Rod / Ascendance

• Falme Shock Uptime
  • Uptime
  • AVG Maelstrom spend [>= 20]
  • Elemental Focus
• Totem Mastery
  • Uptime
  • Number of Recasts
• Elemental Blast
  • Uptime
  • Stat distrubution
• Earth Shock
  • Casts
  • Maelstrom spend ( BoxPlot or only min,max and avg ) [>= 117 or 111]
• Wasted Power of the Maelstrom
• Wasted Stormkeeper Charges
• Lava Burst casts and unspend Lava Surges

Icefury

• Icefury
  • Maelstrom @ cast
  • Missed Frost Shocks
  • Frost Shock Maelstrom spend >= 20

Multi-target

• Liquid Magma Totem (on cd, prio 3-4>)
• Number of Flame Shock targets (1-3 targets)
• Earthquake >= 50 Maelstrom
• Chain Lightning
• Lava Burst only on Proc (3 targets)

Gambling

• Earth Shock at 70-75 if !Ascendance

Overall-TODO

• Detect Number of Targets alive
• Show equiped stat ratios
• Detailed cast sequences for e.g opener or during BL
• Group spec releated infos/statistics

ples

This might be a bad idea since some "bad" talents and talent combination might be considered good/decent in some use cases.

Some encounters may even require you to spec a "bad talent", however this can be solved with checking the encounter ID. However that would in the long term be hard to maintain.

Use this issue to discuss features for this spec. Let us know when you're working on something, or plan to work on something.

• Wasted Judgment of Light statistic
• Devo DR
• 4PT19 healing contribution (from FoL)

If SotF becomes a thing (or legendary ring) we may want to have a sotf analyzer.

Use this issue to discuss features for this spec. Let us know when you're working on something, or plan to work on something.

This necessarily doesn't have to do with anything with your play style. Although it can be interesting to see how much healing this golden trait has contributed to.

This might be a little complex to calculate throughput on.

Should probably primarily look at FoL overhealing. Beacon overhealing can't be helped.

Maybe LoD overhealing and suggesting holding onto it when there's nothing to heal.

Hi, I would love to make translations for spells names but there is no option beside "name" at spells.

Any plan to implement this type of support?

Need a Ilterendi effectiveness calculator that takes overhealing into account pls

Calculate stat weights based on an encounter. This may be implemented for other classes too.

Use this issue to discuss features for this spec. Let us know when you're working on something, or plan to work on something.