The current implementation for thresholds has a massive amount of repeated code across every spec. Refactor this to:
Have a single entry point for managing active ability thresholds (not passive -- this will happen elsewhere/later)
Pass in the spells, snapshot, and talents objects
Pass in a snowflake() function that handles specific cases about each snowflake for that spec
Include everything currently within the for loop
There are some specific modification calls made for getting resource required. This will need to be standardized and/or have another function passed in to handle it.
Do the same high-level priority checking for positioning+coloring+visibility with existing logic.
QUESTION: Does there need to be an extra super special case for stealth ability things for Rogue + Feral?
The current implementation for thresholds has a massive amount of repeated code across every spec. Refactor this to:
spells,snapshot, andtalentsobjectssnowflake()function that handles specific cases about each snowflake for that specforloop