druid-eclipse
Latest
Shifting Perspectives: Changing Eclipse
Every week, Shifting Perspectives explores issues affecting druids and those who group with them. This week, we're going to be looking at the most common gripe of the balance druid. That fickle little talent that every balance druid loves to hate: Eclipse. What's really wrong with it? How can we make it better? Why do we misname the procs? Every time that I visit the Damage Dealing or Druid forums, I often feel like I am back in Wrath of the Lich King beta. During that time, every day there was some thread about some balance druid issue that needed to be addressed, usually it was Eclipse. For those that currently take up an issue with Eclipse, I want to personally apologize for the state that it has come to today. Although I am not a design for WoW, nor do I have any direct influence on the design philosophy of any class, I can't help but thinking every day that I, along with several other notable figures, paved the way for Eclipse to become what it is today. For those that do not know what I am talking about, let me explain. During WotLK Beta, Eclipse was a terrible talent. By terrible, I don't mean that it was on par with Genesis. No, it was worse than Genesis. Eclipse was so bad during the early stages of Beta that there was more than several incarnations of the talent where it was a DPS loss to spend any talent points into it. Eclipse started out where you could only gain one proc every minute and the proc was either 10% increased damage to Wrath or 10% increased crit chance to Starfire. I shouldn't say it was all Eclipse's fault that it sucked, at the time the Glyph of Starfire had no extension limitation which certainly complicated the matter as well. Even without that, though, Eclipse simply wasn't worth it. There was no point in proccing Eclipse to buff Starfire at that point because 10% was too at the mercy of RNG to have a noticeable effect, and Wrath did not play well enough with Nature's Grace at the time to make its Eclipse proc viable.
