In addition to the lack of expertise food buff, I have discovered another expertise-related bug.

The racial expertise section is off: it adds 3*L24 expertise, but that doesn't apply to every race. Orcs at least get +5 instead.

Consider making it a dropdown box for 0, 3 or 5, and taking out the multiplier.

The value in the proc column refers to the corresponding average stat gain in the 'Procs' area in the Item Selection page. I suppose you could manually calculate the SEP based on that value.

Weapons have different SEP based on which hand they are in because weapon speed and damage produce different results accordingly. For example, the bigger deep wounds ticks provided by a slow weapon would be more beneficial if the weapon is in the main hand, whereas the benefit is lesser if it's in the off hand. You can see this effect in the spreadsheet SEP where the REALLY slow weapons have a much higher SEP value when in the main hand.

Fast weapons in the offhand provide consistent rage that is not affected by heroic strike usage, which probably accounts for them having a higher SEP when in the offhand, though I am not sure if this is modeled in the sheet.

Polearms are there in case I start working on Arms models. Please save all your questions until the next version, which will be done within the week. Remember it's still in BETA form so it's not entirely a finished product yet.

Thanks for a great spreadsheet! For the next update i wonder if it would be possible to implement two rows with stats, unbuffed and fully buffed? Bit like there was in dr_Allcom's spreadsheet so it was easy to see the benefit of the different buffs one got. Right now what can be seen is unbuffed stats but not the result after buffs (and talents)?

I know the way this spreadsheet calculates racial expertise has been brought up before but I still haven't been able to figure it out. If the boxes under Racial Expertise is supposed to be binary (values 0 or 1 only) and the values under Spec Activator-Axe-Sword-Mace is supposed to be the amount your racial expertise gives, then it's not working for me. Entering any values under Spec Activator result in no change. The only way I can get the numbers to change is to enter values 1-5 under Racial Expertise. Below is an example:

I'm an orc. I get +5 to axes. If the expertise cap is 209.856 (6.4% base dodge * 32.78998947) untalented, 144.276 (2 * 32.78998947) with weapon mastery, and 103.2885 (5 * 8.1974973675) with the axe racial, then I should see exactly zero dps increase if I set my gear to have >= 104 expertise rating with both Racial Expertise boxes set to 1 and Activator boxes set to 5 while wielding axes. This is not the case. I have tried it with all sorts of weapons, buffs, gem settings, with no effect. The closest approximation to getting it to work was when I set Racial Expertise boxes to 2 with still came out to be lower than what I would get if I had 5 expertise (but 3 resulted in too large of an expertise bonus).

In summary: Spec activator boxes don't work for me, and Racial Expertise boxes are off target. Please help/fix.

Plugging in your gear the value of exp drops to to 0 because you are at cap. 4.5% + 2% from talents I am assuming thats where your confusion is coming from. And i really cant answer your other question haven't been using the sheet long enough.

I've got a question about how you do enchant uptime... maybe I'm just missing something here. You currently have: 1.2/(1/T143)/100 which simplifies to 1.2*T143/100 for the chance to proc berserking for example. 1.2 being the enchant's PPM, and T143 being the base attack speed of the weapon, this is for MH.

With a 3.5 speed weapon, this is a 4.2% chance on hit to proc and gives around a 45% predicted uptime for zerking. I thought though that the chance on hit for a wep enchant to proc was: PPM/AttacksPerMin which is 1.2/(60/T143) which simplifies to 1.2*T143/60 = 7% chance to proc on hit. This gives an uptime of 60-65%.

Attacks per min * chance to proc = PPM. (60/3.5) * .07 = 1.2. It all checks out.

Check the front page for the massive update. Finally done with it!

@Mightbeast: Actually the Titansteel Destroyer is a pretty crappy weapon for it's level, while Runeblades are most excellent. It may not be worth the small DPS gain to switch and regem the hit back in and lose the stamina. You have to take everything with consideration. Also, for the 1000th time on these forums, the dodge cap is above 6.25 and below 6.5% percent. Just because you don't ever realize yourself get dodged doesn't mean it doesn't happen to you or other people.

@Rallik: The uptime is derived from its 1.2 PPM yes, but it has to take into account special attacks, as well as the proc refreshing itself. The formula is of the form:



Where D is the duration of the buff and v is the amount of attacks per second that can proc the buff.

Nice interface changes. There's a bug with ring sockets though, when I switch a ring to Greatring of Collision it says "16" where it should say the socket color.

Also, the SEP macro seems broken on the .xls version. When I press the button I get the error "Run-time error '1004': This operation requires the merged cells to be identically sized." Clicking debug says the error occurs on the line:

Selection.PasteSpecial Paste:=xlPasteValues, Operation:=xlNone, SkipBlanks _
:=False, Transpose:=False

in the SEP() function. In addition, the error occurs when cells AM-AN on row 29 are highlighted.

Sigh.. Are you kidding me.. Anyone with '97 able to get a crack on the solution? There's no way I can check it since I don't have the older excel. Is it only because AM:AN are merged for formatting reasons?

Quick fix for the Ring Socket bug: in AA14 and AA16 the code should say:
AA14: =IF(VLOOKUP(T14,Lookup!FN2:GA222,12,FALSE)=0,"",VLOOKUP(T14,Lookup!FN2:GA222,12,FALSE ))
AA16: =IF(VLOOKUP(T16,Lookup!FN2:GA222,12,FALSE)=0,"",VLOOKUP(T16,Lookup!FN2:GA222,12,FALSE ))

I accidentally put 14 instead of 12 in the first Vlookup Argument.

I understand how it all works, but the only part I'm concerned with is the center of that formula which should be the percent chance on every attack for the enchant to activate. What I'm asking is, why are you dividing by 100 and not 60? (PPM*WepSpd)/100 is a meaningless number. (PPM*WepSpd)/60 is by definition the percent chance a proc would need to activate per hit to come out to an expected value equal to the PPM.

With real numbers, 1.2 PPM and a 3.5 speed weapon. 1.2*3.5/100 = 4.2%. 60/3.5 ~= 17.14 attacks per minute. Attacks per minute * chance on hit to activate = expected PPM. 17.14 * 4.2% = .72, when it should be 1.2.

Or to put it another way, if you had an enchant with 60 PPM and had a 1 speed weapon, it should be obvious as hell that your chance on hit to activate would be 100%. Using: PPM*wepspd/100 will give 60% instead.