Might of Leviathon has its hit and arp in the wrong place on the spreadsheet.

X110, the Mjolnir Runestone uptime cell still references Grim Toll:
ArP Values for Grim Toll and Mjolnir are hard-coded. C59 isn't anything like the Grim Toll cell.

Ah, AD78 still references AD108 instead of AD110.

Cloak gem and socket bonus cells are busted, as well as only doing a lookup on the first socket for the bonus.

Gear totals don't have a 2nd socket for cloak yet.

Mjolnir runestone is actually 655 ArP even though its tooltip says 612, Mjolnir Runestone - Spell - World of Warcraft

Ok so looking at this spreadsheet, for arms is it 100% safe to say that ArP > Strength? as i resocket the gems from Strength to ArP my dps goes up on the spreadsheet. So before i resocket i just want some input and any kind of confirmation anyone can give me because its a lot of Gold id rather not waste. So if anyone could give me some input thatd be great. Thanks

After messing with it for a bit, shouldn't there be an ArP sanity check? I was trying to calculate the proper effect of Grim Toll when the proc is shooting you over the cap and noticed that it showed me gaining DPS off ArP even when the base ArP% was over 100%, which is a bit... odd. I haven't used Excel in forever or I'd try to suggest a way to do this, but unless I'm completely missing something it should be in there somewhere.

Yeah I forgot to fix the 2nd cape socket so it's broke. Sorry about that.

In order to import my caracter's armory, i wanna know how to put "é" with accent for the realm, please. Thx

Few more comments with the latest version:

Armory import is broken at the moment, as it looks like the XML format has changed to accomodate dual-spec. New XPatch search term seems to fix it:

Talent import also misses Juggernaut in arms, and so throws the rest of the parse out - adding 1 to each talent subsequent to Imp Slam (and carrying through to fury/prot values too) fixes this.

With the Armory being flaky at the moment, sometimes an enchant lookup fails, and this causes a runtime error in the macro. Perhaps ValidateEnchant() could be skipped where getTooltipValue fails to return a value (user already gets a msgbox in this case, but rest of scrape could potentially continue).

Runeblade of Demonstrable Power (yeah, sucks to be me) has a typo in the lookup sheet ("Demostrable").

And a few more cosmetic comments:

Unbuffed HP calculation still missing neck lookup.

Wouldn't mind The Severed Noose of Westwind (yeah, really sucks to be me) being added, though I can always add that myself, or go out and get a proper necklace or something.

Have come to really enjoy working with this sheet - been ages since I did any spreadsheet programming, and this is one of the most pleasurable WoW-related ones to work with. So always happy to suggest tweaks/fixes as I come across them. If I overstep the line, please feel free to give me a slap on the wrist - I am not 100% sure of the etiquette here.

Does anyone know how reliable Rawr is compared to the spreadsheet? (The DPS Warrior module is definitely less sophisticated and has way less options compared to other modules like tanks or mages)

I've been messing around with both, but the two give slightly different results such as gem choices on a couple of my pieces (rawr seems to favor hit/exp a BIT more than the spreadsheet does)

Hey Guys, I have a little question.
I am working on an own Arms DPS Calculation Spreadsheet (don’t worry, it won't be able compete with yours, landsoul ) and for that I also need to know about the arpen mechanics.
Now the fog is lifted and we all know that it isn't a bug, but a wanted thing, how it works now, I investigated a bit, to get proof how I have to deal with it in my spreadsheet.

Now the little question:
Are you 100% sure about the 10643 boss-armor?
To get to the numbers I collected from the Heroic Training Dummy, the armor would have to be something about 11620 to 11640.
I found out that after arpen affected the "(armor + C)/3"-part, all other debuffs have influence on the whole armor that arpen left back inclusive the "armor-(armor + C)/3"-part.
So like that:
x = sum of arpen buffs(mace spec/battle stance/gear arpen)
y = product of arpen debuffs(sunder/ff) (1 - 0.95 * 0.8)
(armor - (armor + C)/3 + (armor + C)/3 * x) * y

For C = 15232,5 and armor = 10643 I get all correct percentages I collected and calculated through the tests.
But don't I have to use for C = 16635 for bosses? Or do I have there an error in reasoning?
If not, I only get correct numbers with the mentioned 11620 to 11640 armor.

The complete formula I used:
x = sum of arpen buffs(mace spec/battle stance/gear arpen)
y = product of arpen debuffs(sunder/ff) (1 - 0.95 * 0.8)
C = 400 + 85 * targetlevel + 4.5 * 85 * (targetlevel - 59) (out of the blue post for the half armor value)

% damage done = C/(C + (armor - (armor + C)/3 + (armor + C)/3 * x) * y)

Thanks in advance for all response!

Edit:
Sorry, I made a mistake in typing the formulas. I accidentally took a version of the formula I used to "play" with, for investigation. So also the text is wrong, too.
It should be:
x = sum of arpen buffs(mace spec/battle stance/gear arpen)
y = product of arpen debuffs(sunder/ff) (1 - 0.95 * 0.8)
C = 400 + 85 * targetlevel + 4.5 * 85 * (targetlevel - 59) (out of the blue post for the half armor value)

armor after buffs/debuffs = armor*y - (armor*y + C)/3 + (armor*y + C)/3 * x

and

% damage done = C/(C + (armor*y - (armor*y + C)/3 + (armor*y + C)/3 * x)

For some reason the entire spreadsheet, of the latest version, is broken for me. It gives #div0! values for the SEP values, probably because it doesn't decently seem to calculate the effect of +1 stat on the DPS (as in that column all the DPS values stay the same.)

When pressing the "calculate SEP" button I can see it adding +1 to each stat temporarily, but it doesn't seem to write down how this affects the DPS in the end. Or maybe it doesn't calculate it decently. I've no clue why it's suddenly broken compared to the previous versions.