Hunter Spreadsheets -- In development - Page 51

QuiggyB · 09/16/07, 10:29 AM

The sheet doesnt seem to be calculating anything for that card. You can set the trinket slot to none, set your off-hand to custom and put 120 atk power in the custom offhand slot. When I do that I get a 4.5 dps upgrade which isnt even remotely worth the cost of the card. Bloodlust broach shows the same dps upgrade over hourglass.

Cheeky · 09/18/07, 12:02 AM

A couple quick fixes that I found annoying:
- Fixed averaging out The Beast Within for Open Office.
- Removed potential rounding errors that I may have had in the "+1 Attribute yield X DPS" Feature.
- Expanded the "+1 Attribute = X DPS" feature to include Intellect, Haste, and Armor Penetration.
- Have [Darkmoon Card: Crusade] operate fully stacked for modeling purposes.
- Fixed cell locking preventing some of the save sets being used.

• vank · 09/18/07, 12:17 AM

Using Open Office version and none of the gems can be selected from the drop down lists.

Cheeky · 09/18/07, 9:09 AM

Originally Posted by vank

Using Open Office version and none of the gems can be selected from the drop down lists.

Using OO version 2.2.1 from Sun it is working fine. What version are you using (and which gem locations)?

SiRk · 09/18/07, 11:06 AM

- Provided the user the ability to select 2.1 or 2.2 Haste Rating conversion rates. (This will be removed when 2.2 goes live.)

I have the version 30 of the spreadsheet, but changing the Haste Rating setting doesn't seem to influence the shot timer at all. (I manually added 400 haste rating to check for this)

Keep up the good work for the rest!

edit: using excel 2007 if that's any help

Cheeky · 09/18/07, 11:18 AM

Originally Posted by SiRk

I have the version 30 of the spreadsheet, but changing the Haste Rating setting doesn't seem to influence the shot timer at all. (I manually added 400 haste rating to check for this)

Keep up the good work for the rest!

edit: using excel 2007 if that's any help

Could it be that 400 haste rating at 2.1 (~38%) and 2.2 (~25%) both have you bumped up against the GCD in your rotation? I am seeing the values change. Check cell H19 on the 'Calculations' tab to see the effect of the haste rating -> haste % conversion.

SiRk · 09/18/07, 11:26 AM

Originally Posted by Cheeky

Could it be that 400 haste rating at 2.1 (~38%) and 2.2 (~25%) both have you bumped up against the GCD in your rotation? I am seeing the values change. Check cell H19 on the 'Calculations' tab to see the effect of the haste rating -> haste % conversion.

Using my current gear (no haste), and adding 400 static haste rating in R89 on 'Gear' tab (steady shot rotation all the way, bm 41/20 build):
- 2.1 setting: H19 = 138%
- 2.2 setting: H19 = 138%

I see the 'Calculating...' message appearing in the status bar when changing the setting, but nothing seems to be changing for some odd reason.

Cheeky · 09/18/07, 11:31 AM

Originally Posted by SiRk

Using my current gear (no haste), and adding 400 static haste rating in R89 on 'Gear' tab (steady shot rotation all the way, bm 41/20 build):
- 2.1 setting: H19 = 138%
- 2.2 setting: H19 = 138%

I see the 'Calculating...' message appearing in the status bar when changing the setting, but nothing seems to be changing for some odd reason.

Hmm. That's odd. If you change the haste rating after changing the setting does it update cell H19? I've tested with Excel 2000 and 2003 (all I have access to.) I also tested in Sun's Open Office and it's working there too.

• vank · 09/18/07, 12:01 PM

I am using OO 2.2. I guess I'll update to 2.2.1 when I get home and check it out.

SiRk · 09/18/07, 12:13 PM

Originally Posted by Cheeky

Hmm. That's odd. If you change the haste rating after changing the setting does it update cell H19?

Yes it does, but it keeps calculating using the 2.1 haste rating no matter what setting I choose.

SiRk · 09/18/07, 12:22 PM

Something strange I noticed tho: when I first opened the freshly downloaded version 30, the setting was at '2,2', while in the list the only allowed values are '2.1' and '2.2', so with point instead of comma. If I manually change it to '2,2', it does show a different value in M3 on the Settings tab, but it gives an error saying I can only enter a value from the list.

Fola · 09/18/07, 1:51 PM

Selecting:
Midnight Chestguard (The Leather Chest)

brings up the stats for:
Merciless Gladiator's Chain Armor

Is it possible that the Midnight Chestguard is not in the lookup array and it is just finding the closest match? I just made the adjustments in the hand adjustments, thought you might like to know though.

SiRk · 09/19/07, 8:56 AM

I reproduced the problem I posted earlier on a Office 2002 environment. The first time I open the spreadsheet, the setting is at 2,2 (with comma), and the haste rating uses the correct modifier. But whenever I change the setting, I can only choose from 2.1 and 2.2 (with a point instead of a comma), and then whatever I choose, it keeps using the 2.1 haste rating modifier.

Cheeky · 09/19/07, 10:37 AM

Originally Posted by SiRk

I reproduced the problem I posted earlier on a Office 2002 environment. The first time I open the spreadsheet, the setting is at 2,2 (with comma), and the haste rating uses the correct modifier. But whenever I change the setting, I can only choose from 2.1 and 2.2 (with a point instead of a comma), and then whatever I choose, it keeps using the 2.1 haste rating modifier.

Is this a European version of Excel? I am positive I store the result as 2.2, but if the number gets converted to display as non-U.S. it might show up as 2,2 - which means that Excel isn't treating the list values I provide for validation as numbers (and converting them too) but as text strings.

I'll convert the whole thing to text strings later tonight. That should solve the problem.

Trohck · 09/19/07, 11:13 AM

Originally Posted by Trohck

Cheeky, can you please add [Messenger of Fate]? Thanks.

edit:
Also, [Balanced Shadowsong Amethyst] is listed incorrectly. It has the correct stats in the math portion (10 AP, 7 stam) but the item name says 3 stam, 4 crit.

Repeating this post from page 23, assuming it got lost in the shuffle.