Quote Originally Posted by Ghishlain View Post
You are indeed correct. My comment was more of an (unfortunate) reaction to the sarcastic nature of post and how it wasn't too conducive to the discussion as a whole. I can understand how someone may misinterpret my comment as indicating how a parser is needed to maximize a rotation given the context of the conversation and that wasn't my intent.

My intent was to indicate the math for determining optimized rotation is a bit more complicated than the poster suggested and required much more thought than adding 100 + 150 = 250, especially when you consider the multitude of different scenarios one could use a DRG when thinking about Chaos Thrust, Disembowel, Heavy Thrust, Blood of the Dragon, and Phlebotomize in their normal string of attacks.
Might be worth noting (I don't know if you actually go to the DPS forums to find Optimal rotations) that theorycrafters still don't use parsers, even if they are more accurate now. The best rotations is determined strictly by highest potency per second, which is done completely with math, not by trial and error or in practice. Whether or not someone is skilled enough to perform the rotation is another story though. But even then, parsers aren't even part of the process, with the exception of stat weights, for ease of statistical mining.

If you aren't doing your rotation correctly, no amount of parsing will fix that. You have to know what you are doing wrong, which frankly looking at a bland number will not tell you that you should be using contation after tri-disaster on the last second of raging strikes to improve output in the opener. Not only is such information impossible for a parser to determine (DoT aren't actually in the log and the ticks are not on the client) but it's also completely obvious without using a parser. People who do not understand the usage of a parser cannot improve from using it. You shouldn't be using a parser to fix your rotation. You should be using a parser to fix your equipment.