You're not reforged optimally in the 2T11 sheet--the chest doesn't have haste on it. This is particularly important because 90 more haste from that reforge would put you over the 2322 breakpoint. Only one of the sets having that breakpoint was part of the discrepancy before. Once you change that the 2T11 is slightly ahead.

In general though, that they're this close isn't that surprising--the 2T11 is very weak (~250 DPS). These days a one-tier upgrade in one slot can typically be worth 150-200 DPS. The chest upgrade you're looking at here is only half a tier, but you're also swapping crit for haste, and the way you had it, you were picking up a DoT tick.

e: whoops, ignore the breakpoint comments, just noticed you don't have DI. The rest is the same though--6ilvl upgrade with an improvement in secondary stats it basically worth around as much the set bonus.

Fixed belt buckles and gems updating from battle.net properly, and spotted that tailoring leg enchants hadn't been allowed for (the sheet just adds them as the regular leg enchants now, but it's the same stats). I'll be adding the battle.net import to Treecalcs this weekend, so if you've spotted anything else that's not quite right, please let me know.

I don't know if this is a bug, but for me the Talent tree parsing doesn't work. Maybe this is because you didn't implement it at this time.

I running Microsoft Exel 2007 on Win7 with all updates.

Resolved, thanks! Fixed version enclosed.

Current issues: 64 bit Excel apparently doesn't work with the method I'm using for storing the armory info, I'm looking into it. Also, some more unusual characters aren't being caught by the internet encoding I'm doing, so I'm also looking into resolving that.

Battle.net armory import function is very nice, thank you for the update.

as an aside, is it generally better to look at a non-haste-breakpoint-inflated value of a gear piece when considering upgrades?
or is it one of those mileage-will-vary situations?

I'll need to figure something out for that, then. Thanks for the input!

In general it doesn't matter since haste is the top secondary stat anyway. In the occasional case where it matters, just compare the pieces in the exact situation you're in rather than trying to come up with an general stat value. The exact value of haste is basically always situation-specific due to breakpoints.

For example, look at my gear now--I have [Valiona's Medallion] equipped over [Heartstone of Rhyolith] in order to get up over 2322 haste.

Note: rename Mindweb Staff to Funeral Pyre.

Again back to that topic:

I discovered in the new versions from Hamlet (20110806), that WrathCalcs is broken, but TreeCalcs (20110806) (again with the broken macros and broken talent saving), shows correct translated Booleans and give me a calculation. I don't remember than this Problem occurs first, but I'll give a look into it, to give you a more details.

The Edit means that I should only edit this article:

Searching now through the whole topic and found where the thing occurs first:
The last Version where everything is alright is: WratchCalcs 20110505b PTR which you find in this post: [Balance] WrathCalcs
The next file WrathCalcs 20110510 PTR is then broken first. You'll find it here: [Balance] WrathCalcs

At a deeper look into the file I see that in "Profiles" sheet only the Booleans from the Hamlet saving is broken. The Tecton saving is alright. That's what I discover then first on the life versions.

Hopefully that helps you a little bit more.

Another Edit again: I really don't think this is a very important bug, but maybe a notice in Guide would be cool, because I get yesterday a whisper from another Druide from my server because he didn't see a problem in the wrong language. So maybe a bug entry maybe help some of the people.

Man, who actually thinks about that Excel is stupid enough not to translate FALSE and TRUE to the right german phrases! :P

And to note that: The "latest" Hamlet version in the main balance thread (07.07.2011) works good when it comes to the right dps output. Strange though

Well I don't think so. Because in the 20110707 as I take a look into the "Profiles" sheet. Again the same: Tecton works. Hamlet and Hamlet T12 have the wrong translation. As I load them Exel doesn't know that these are booleans and doesn't translate them.