Big fan of the spreadsheet Landsoul. Please keep up the excellent work.

Found a cosmetic issue with the spreadsheet. Cell E4 is not reflecting the correct ArP when Mace Specialization is selected. Instead of increasing ArP by 3% for each talent point, the cell is only reflecting .3% for each talent point.

The cell used in the actual DPS calculations (C58) is reflecting the correct percentage increase.

Is this the same formula you imploy in your spreadsheet?

This makes me sad. I despise arena, the idea of having to arena for a bis weapon makes me sad. I hope a new weapon somehow magicaly appears in ulduar.

I´d say Algalon will have a say in this

On the first part, aye. There are 73 points spent to get all the ones checked off that are in the default list. The second part isn't true though. Improved Execute is actually a very minor DPS gain; quite a bit less than 4% more strength. They are the first 2 talents you want to drop if you need all the ones in Arms. If you don't need the expertise because you're stuck with too much, then you want to drop Weapon Mastery, not SoA.

I just checked the spreadsheet and yes, you are right SoA > WM. Thank you for pointing that out.

No sure if this has been brought up but it seem as The World of Warcraft Armory is not valid in armory profile window, is it another adress or isent EU version valid?

Im having some trouble with the spreadsheet for excel 97. When I open it, i get an error message saying Microsoft Excel cannot calculate a formula (circular reference?) And if I go to the arms page, My dps does not change as I change gear, or even race. If I run an SEP calculation with all the gear in the default setting (that is, as you open the spreadsheet) All the SEP fields show #DIV/0! Am I missing something (this is version 402c)

Oh, hey there buddy. So Landsoul is the caretaker of 'The Sheet" these days, eh? Good, smart guy if I remember right. I've been kind of thinking about playing a little bit again, so I thought I'd pop in here and say 'hey' and take a look at the state of modern spreadsheet-dom.

I noticed a slight mistake in version 2.4. I havent got the new one because filefront won't work for me so if this was fixed already im sorry.

For the helm [Guise of the Midgard Serpent], the spreadsheet has the socket bonus listed as 16 ap when in live it is actually 32 ap. This is the biggest socket bonus I've ever seen and likely is a mistake, but for now its at 32 ap.

1. When dual-wielding two hand weapons, does it use the 7 or the 3.5 value for a hit in normalized rage generation?
2. Can trinket proc effecs happen off of off-hand whirlwinds? (currently set to no) Weapon enchants, yes.
3. I need some help with a way to organize gem selection better.
4. I would like someone to help with the programming of Arms. There's a lot of conditions where it makes referencing cells messy and there's got to be a better way to organize it than the way I have it now without it breaking all over the place.


1. First, I am operating under the assumption that a 2hO benefits from both DW spec and 2H Spec, yes? I spent awhile effectively writing, and then deleting, an essay on this topic. After a lot of thought on how this part of the system seems to work behind the scenes, I would be shocked if it was anything other than 3.5. Based upon the way they would have had to code various other 2hO interactions to get them to work the way they do, it would be 3.5. My prime example is DW Spec. In order to be flagged for the OH dmg bonus, the MH vs. OH var would have to have priority over the 2h vs. MH var. While it is possible that they could code it the other way around for rage gen, I can't see any reason why they would. Not to mention that 3.5 just makes the most sense. The vibe I get from Titan's Grip is one of adding 2h weapons to DW, as opposed to adding DW to 2h weapons. This leads me to believe that OH rules have priority over 2H rules.

2. Very, very tricky. First, about OH weapon procs, I think the obvious answer is yes. Moving on to OH WW, on the one hand, it is an OH, but on the other, it is yellow. Let's evaluate what we know.
The damage appears as two separate events, both yellow.
Single hit yellow attacks, like Bloodthirst or MS, use the MH proc rate.
OH proc rates are already being calculated in order to support OH weapon and enchant procs, so tracking OH yellows would not require adding too much code or calculation overhead.

What we do not know for sure is if the game tracks an OH WW hit as simply another yellow (MH proc rate), an OH yellow (OH proc rate) or simply considers it the same hit as the MH WW and the 2 displayed #s are for display only (no proc)

When I was working on the old sheet, I went with the second method. I tracked and calculated OH yellow attacks as distinct events, and calculated separate proc rates for them. For things like trinket procs, I combined the MH and OH rates. Remember to use (a1+a2)-(a1*a2) rather than a simple sum.

What I cannot recall for sure is if I based this upon observed data or theory.

3. & 4. I may be able to help out, but I can't commit to anything just yet. It will depend upon if I play again and how serious I get if I do. On the table would be 1) Do nothing, 2) Help out 3) Re-write from scratch using a fully modular design.


Anyway, I hope my ramblings helped in some way.