I searched through the druid forum for this, and since i haven't found it, i'm going to ask if any of you guys experienced this :

Wrath vs. Starfire, how does the damage register? Does wrath damage register on impact, or at the end of the cast?

On starfire it's easy, at the end of the cast, since it doesn't matter what range you cast it from, the animation is the same.

On wrath ... well, this is what's been bothering me for a couple of days, but haven't gotten around to test it. (i'm at work atm, when i'm home, i raid the moment i'm online).

I know for a fact that Nature's Grace procced on several occasions (don't have a screenshot) after the wrath cast ended, but hadn't hit the target yet. So, am i to assume from this that the damage is registered instantly after the cast ends? Since it knows it's going to crit before we see the actual damage on the target. Because if this isn't true, that means that wrath damage in a raid enviroment is directly tied to the range it is cast.

Not really. You're using SF to proc Eclipse, so there's no discrepancy between your cast finishing and it proccing to worry about. After that, if the bonus to Wrath is calculated at cast finish, it doesn't matter how far you are from Patch, you'll still get the same number of casts with benefit.

Normally, I'd say that spamming WWS reports isn't an incredibly useful thing here. There's usually mitigating circumstances, gear differences, etc. that cause disparities between reports, so comparing them isn't going to tell you a whole lot. There are two reasons I'm not taking that stance today.

1.) I also have a parse! Wow Web Stats is my raid from Tuesday. We're nowhere near the top end (just under 4 minutes for a kill), so it gives a look at that perspective for those who're in my situation where gear/guild/etc. are still holding you back.

2.) With so many of you having posted them already, I decided to do some comparisons anyway. Late last week I wrote another spreadsheet with a very specific purpose in mind: Understanding WWS parses. I may drop this in the thread for WC at some point once I get it polished a bit, but the functionality's pretty simple. You input your stats from a Patchwerk parse (actually, any parse works, but for obvious reasons Patch is best), and it gives you a listing of information including %time spent casting, average latency, and IS/MF uptime%. It takes into account haste on gear (not procs), Lust, and Haste talents/WoA. It doesn't care about damage at all, in fact. After running all the parses on this page through (including looking up everyone's armory for haste/talent numbers and using wow-heroes for a sense of gear), here are all the results:

Name	Gear	DPS	Cast%	Avg. Lat.	IS%	MF%
Hamlet	2282	5034	79.5%	.396s	57.5%	82.6%
Dukes	2256	4913	88.0%	.210s	50.1%	90.9%
Eilt	2130	4114	83.5%	.319s	43.8%	90%
Rokaz	2293	4784	84.9%	.289s	24.6%	89.5%
Superku	2234	4508	80.7%	.365s	79.5%	85.7%
Adoriele	1898	3650	96.3%	.084s	80.7%	85.7%
Randomsmo	2312	5868	91.2%	.165s	53.0%	90.9%

Now, %cast adds a default .2s to your cast times for latency, so it's a little incongruous, hence why I added Average Latency to the equation (basically, time you spent not casting/number of casts). And the gear scores are, I believe, just a sum of iLevels, plus a set amount per enchant or so, so it's not really going to check how optimal the gear actually is. But, for example, take Randomsmo vs. Rokaz. Similar gear level, about 20 ilvls difference, but due to Rokaz' abysmal IS uptime and about 5% less time spent casting, there's about 1000 DPS difference (yes, that doesn't factor in luck with crits, eclipse, etc. though if I remember, neither had particularly outstanding luck in either direction).

The sheet's attached if you'd like to play with it yourself.

He did, in fact, though the sheet takes care of that. Really, the sheet's only purpose is to give information about time, not damage. I just included the damage numbers in the chart because they were readily available.