I'm sort of in the same situation.

My gearset is a bit odd, but I gain a lot more than that (2226 Shadow, 2388 fire).

To be honest, though, I've poked through a lot of brutallus parses and haven't seen any really impressive fire parses. Hopefully we'll be there next week and I'll take a shot at it myself.

Shadow does give superior scaling with all stats....by the time I get a couple more pieces of gear, this might be different. We do run 0-1 shadow priests, and all our locks are currently fire, so staying fire means CoS doesn't need to be up.

Edit: Is there an option for Judgement of the Crusader on the spreadsheet, or can it be added?

Ok, maybe I've missed something but I'm confused by the "Next Stat" section of the worksheet. I assumed these values were dependent on spec and gear. That is, if you're hit capped, the next hit added should be worthless. The spreadsheet doesn't seem to be working that way - even if I load the t6 set with 221 hit, it still shows one point of hit as being the highest value (1.3) compared to crit, dmg or haste.

Am I simply trying to use this section of the spreadsheet incorrectly? I'm looking for a way to value stats against each other.

Thanks.

Works on my spreadsheet. I'm guessing by "loading up the T6" set you're just doing that in the Gear_Buffs section. The two tabs aren't linked. You either need to copy the data over manually each time or change the input values on the DPS tab so that they are taken from the Gear_Buffs tab totals(which I would suggest as a standard feature for the next release).

The two tabs are linked on my spreadsheet - stam, crit, hit, everything comes over from the gear tab to the DPS one. And they have an effect on the Next Stat section, just not the effect I'd expect.

Weird, I redownloaded 2.2 and it is linked now. Did you notice the comment on the hit tab that says "If not hit capped"?

Ah thanks - I'd missed that. Guess I should just assume that 'if hit capped' there's no value to another point of hit. I can also assume that the other values are accurate in their relative valuation?

Thanks for the help.

The thing is hit is not completely lacking value when capped since it can allow you to reduce other stats. However the way the spreadsheet evaluates hit when you're capped isn't the actual value you should give to hit, but at least it tells you how much DPS you would lose if you drop hit below the cap so I guess that field is still useful. Remember TNS works for negative stat change just as well.

To actually evaluate hit at cap you'll have to look at where you could drop hit to gain other stats if you increase hit above cap (to end up staying at the cap). This is a very complicated task that I wouldn't expect a spreadsheet to do

Using OpenOffice Calc I am getting an error as well Bolche. Here is the error:

OpenOffice.org Error
A Scripting Framework error occurred while running the Basic script
vnd.sun.star.script:Standard.Sort_items_value?language=Basic&location=document.

Message: BasicProviderImpl::getScript: no script!

Let me know if you get a fix for this, thanks!

Feature request:

Can you add in straight +stam gems to the list.

I use a solid star of elune in my wand and have to add in the gem to the list every time I get anew version of the sheet. If you could add in the solid gems that would be great.

Since this doesn't affect your dps, just use none.

I assume he means in a blue socket, thus needing to put a blue in to fill that requirement.. I suppose you could put a spell pen gem in that slot if the spreadsheet has that.. But it probably doesn't have those either.

Just wanted to check with the rest of the spreadsheet users out there whether they've seen +haste TNS outperforming +damage TNS on the DPS tab but not reflecting as such when you tweak those values with item changes to Gear Buffs.

To test this bring up your spreadsheet and look at the Gems tab, sort by value and notice Reckless Pyrestone(RP) beating out Runed Crimson Spinel(RCS) and then doing swaps from RCS to RP in the Gear Buff tab. Compare Quick Lionseye vs RCS as well as Forceful Seaspray Emerald vs Glowing Shadowsong Amethyst. In all cases the haste gem will decrease dps which is contrary to how the values of the gems are in Gem tab which use TNS values.

My stats:
1477 shadow (Crusade+HSH trinkets calculated, no raid buffs)
28.40% crit with devastation
202 hit
2% haste
0/21/40 Shadow
TNS + 1 dmg = 0.8dps gain
TNS + 1 haste rating = 1.08dps gain

Anyone understand this little quirk?

Interesting... I found part of it but there is another part I can't figure out.

First, the ISB uptime for haste was using the crit # on my sheet. Fix #1:
TNS-haste tab, cell L7 should read:
IF(ISB_method="Model 1",L4,
IF(ISB_method="Model 2",L5,
IF(ISB_method="Raid",'Raid ISB'!B28,L6)))

That lowers the DPS gain from haste a little but there is more. The second part I have looked at the full formula and cannot pin down... Basically on sheet DPS cell B56 lines up with cell B40 on TNS-sdmg. However if you compare the number on TNS with the number on DPS (after adding +1 damage to gear) the numbers are not the same. I've looked thru the whole formula and can't see why it's calculating a different number, everything else seems to line up on the sheet.

EDIT: So... I think I found it. I noticed that the ISB uptime goes up by a very small amount when you add one damage (which doesn't happen in TNS-sdmg). Followed it back to the fact that life taps are marginally more useful. So (correct me if I'm wrong, I'm getting spreadsheet-head) I think the TNS sheet is not taking into account the fact that ISB does slightly scale with +damage.

EDIT2: That doesn't cover it... there's still something else. >.<

EDIT3: Hah... kidding, that was it:
Fix #2: on TNS-sdmg, cell N8 should be:
(580+add_s*0.8)*(1+imp_lt/10)
--life tap wasn't getting the +1 dmg

I've noticed something similar to that also. For example, currently it's telling me in the TNS section that 1 damage is equal to 1.21 crit rating.

So when I go to the gear buffs tab and switch my food from 23 damage to 20 crit rating, my DPS actually goes down to 2000 from 2005.

1.21 * 20 = 24.2
1 * 23 = 23

The crit rating food clearly wins using the TNS formula but the DPS value shows the exact opposite. Does anyone know why?

Do you have Raid TNS = 1? That includes increased damage from ISB to the raid in TNS which will not be reflected in your personal DPS.

Thanks for the fixes, been bugging me the last week or* so.

Hmm, I found a strange thing in Next Stat values section.

Here's my setup:

- 0/21/40 shadow destro
- no immolate casted (SB shows as 100% of dps)
- hit cap

Still the mentioned section shows:


+1dmg - Stat cost = 0.7, Profitability = 1.34
+1shadow dmg - Stat cost = 0.85, Profitability = 1.1

What's the reason for +shadow being more expensive stat? Does the spreadsheet take itemization into account (just a wild guess)? Values are constant and not related to any other value in the excel. DPS bonus shown is exactly the same (0.96).

PS. Using latest 2.4 version, downloaded today.

You must have changed something, because the stats cost are :
+dmg : 0.85
+shadow damage : 0.7

There is an error in the way bloodlust is added in the spreadsheet. You cannot add haste as a static value as it is multiplied with your cast speed, it is not converted into haste rating and then added.

It should be calculated like this:

new_cast_time = old_cast_time / ((1 + haste_rating/1576,923)*1,3)

not like this:

new_cast_time = old_cast_time / (1 + haste_rating/1576,923+0,3)

It is rather easy to test. My results:

114 haste rating equipped, got a bloodlust and my shadow bolt cast time was down to 1,79 sec. If it was added it would have been 1,82 sec.

Yes, my bad, I have no idea why these values were exchanged in my sheet, prolly changed by accident.

Still question remains: why is shadow cheaper to get then "normal" damage?

Because it only affects one school of magic.

Any more solid info available on the SSO Exhalted neck item? It would be nice to have each faction (Scryer or Aldor) selectable from the dropdown and the stats (including proc rate DPS, etc) available.

Best data I have seen (or managed to gather myself) is 1.2 PPM with a 45 sec internal CD (roughly equating to +25 dam).

Does that seem close?