3.1 Preview Version
by Bakka on Mar.27, 2009, under General
Here’s the current working version for 3.1; I thought I’d let people take a look. There’s a ton of changes and even when 3.1 is official and I release a version, I don’t know what the patch notes will contain other than fixed lots of stuff and changes lots of crap :p.
Currently there is only a single template defined (haunt) and importing talents from armory WILL NOT WORK. DO NOT DO IT. You will probably corrupt the spreadsheet if you try.
So if you see any problems with it, post a comment on here or write up a new bug at www.bakkadps.com/bugs [preferred].
March 27th, 2009 on 2:51 pm
Wow, great work getting this up now. I’m on not on the PTR, but I’m sure some of the folks that are will be able to test some math out for you.
March 27th, 2009 on 6:12 pm
Glad to see you back working on this GREAT sheet. I use it a lot!!!
March 28th, 2009 on 10:18 am
Thanks for keeping the project alive.
March 30th, 2009 on 5:31 am
GREAT WORK, BIG THX !!!
March 30th, 2009 on 10:15 am
Bakka, I went to put in a few bugs I found playing around with the 3.1 beta version. I was going to put them into Bugzilla but it only lists 3.0.8 as a version option. I didn’t want to confuse by choosing 3.0.8. Can 3.1 be added as a version choice?
For now the bugs I have seen and they may just be that you haven’t implemented them yet, but I wanted to make sure they were on the agenda.
1) There is now an option on the dps tab for “Immolation Aura” that can be set to 0/1 for used (at least I don’t remember seeing this before). Changing this option currently does nothing. I do not know if it is counting this or not as there are numbers in that row but the overall dps does not change whether it is set to 0 or 1.
2) Decimation/Soulfire casting after 35% doesn’t seem to be accounted for. Taking Decimation talent doesn’t seem to change values at all and I see no place to set whether or not soulfire is used.
3) Not sure if this is intended or a bug – Demonic Embrace Talent has the values of the talent (4, 7, 10) rather than the number of talent points put into it. This is on the dps sheet.
March 30th, 2009 on 12:34 pm
1. You have to have metamorph enabled for this to work. Can’t do immo aura unless in metamorph state. And currently whether or not you have it set to used or not, it ignores and simply flags off metamorph.
2. Decimation is accounted for. There are new filler spells.
3. By design.
March 30th, 2009 on 1:50 pm
1) Ok so simply having the Meta talent set to 1 on DPS sheet flags this as Used currently? Just making sure I understand since I don’t remember seeing that row in earlier versions.
2) Ahh filler, got it, found it now, sorry for the confusion.
Thanks again for all your hard work Bakka!
March 30th, 2009 on 1:34 pm
Any chance of getting blacksmith sockets supported?
Also, the imp is still simulated as doing much more dps than the succubus for afflction builds, and this is certainly not the case on the PTR, fully raid buffed.
April 1st, 2009 on 2:58 pm
There seems to be something screwy with aftermath, putting either 1 or 2 points into it sent everything in TNS “bonus damage” and “profitability” into the negatives. “+dmg” and “stat cost” were fine
All the item values on the item sheet went negative and the “dps” and “hit” columns on the gear_buffs sheet showed ### on all items except the second trinket slot, which showed negative numbers.
However calculated dps still seemed to work correctly.
April 2nd, 2009 on 8:07 am
Whether I have Aftermath or not those columns are messed up. But for me the only one ok is Stat Cost. The other 3 are all #NA. I didn’t notice before becuase I generally don’t look at this section much. The dps & hit columns on the Gear/Buffs sheet also show #NA for me whether I have Aftermath at 1 or 0. My trinket columns are #NA as well not negative numbers.
April 8th, 2009 on 2:44 pm
First I wanted to say I’m glad this is continuing. Keep up the good work!
I don’t know if this is intended or not but wanted to throw this out as a suggestion…for the named ranges for the Item look-ups they are set as static ranges limiting the list of items to whatever the range is set to.
If the named range for say… “items_back” had the formula:
=OFFSET(Items!$B$4,MATCH(”Back”,Items!$A:$A,0)-4,0,COUNTIF(Items!$A:$A,”Back”),22)
and the named range of “items_back_list” had the formula:
=OFFSET(Items!$B$4,MATCH(”Back”,Items!$A:$A,0)-4,0,COUNTIF(Items!$A:$A,”Back”),1)
then you could add as many back items as you wanted and it would always point to the correct range. (assuming it’s sorted of course) This formula can be repeated for every slot with the correct match and countif search terms and you wouldn’t have to worry about setting the range limits in your named ranges.
Already tested this to work with your dropdowns on the Gear_Buffs tab and also works with your sorting buttons.
I always end up adding more than one “custom” item by replacing lower dps items at the bottom of the list…especially when beta items start being leaked…and wanted to offer this up as a suggestion.
April 22nd, 2009 on 2:43 am
There is still a problem I think with having Office 2003 and having #NAME? errors all over and was wondering if there would be a in-sheet fix for this so I don’t have to go google how to fix it everytime
April 22nd, 2009 on 8:52 am
No there won’t be a fix for 2003.
April 28th, 2009 on 11:54 pm
bakka im using openoffice novell version and im seeing #MACRO? everywhere. i tried fixing it by using the EJ method but it isnt working. pls help?
July 19th, 2009 on 6:42 am
Been trying to fill this out since wrath, every version gives me #NAME? in key cells for actual dps calculation and gear upgrades cells. I’ve filled in my spec, buffs, gear, gems, chants, glyphs to completion…made no new changes…tried downloading it every new version to get it to work…is there an easy fix? Has something significant required beyond what we needed to do with it in BC?
July 20th, 2009 on 9:21 am
2 things:
1> why are you posting this on an outdated version of the spreadsheet?
2> from elitist jerks and kept in my e-mail for fixing the spreadsheet on every new version:
Thanks to Bakka and others that brought us this great tool. If the
following is consolidated elsewhere, please let me know.
I use Excel 2003 and people who have used the the later Warlock
spreadsheets know there is a workaround to use the spreadsheet with
Excel2003. The steps for the workaround exist on different pages on
this thread. It is not difficult to piece together, but a single post
w/ attribution is much easier for anyone with this problem. Below is
what I needed to do to use Bakka’s spreadsheet.
The below is taken from several posts by Trickykid.
1. Basically you’re just adding a macro that defines the function
(that works in Excel 2007). I believe it’s alt F11 by default to pull
up the macro window (or Tools> Macro>VB editor), insert module, and
then paste the following and save:
Function IfError(formula As Variant, show As String)
On Error GoTo ErrorHandler
If IsError(formula) Then
IfError = show
Else
IfError = formula
End If
Exit Function
ErrorHandler:
Resume Next
End Function
2. Okay well that macro makes the function IFERROR work, but
apparently when you open the file and it didn’t know about it it
leaves the functions as “_xlfn.IFERROR”. You need to find/replace
those from that to IFERROR.
They show up on hidden tabs, so you will need to unhide all the tabs
and then do a find/replace. [“ALT”.”o”,”h”,”u”,”ENTER”, repeat until
done. 327 replacements on latest 3.1b]
3. Do you have GoC/NF turned on? Pretty sure this is the source of the
remaining problems. Try turning it off and then back on (set to 0 and
then back to 1).
4. Rehide the appropriate sheets
July 24th, 2009 on 11:32 pm
This has all been addressed in a post on the ‘I have quit wow’ thread… the spreadsheet is being maintained by Duffry, and a link was provided.
-xone