I, like many others, have come to rely on Aldriana's combat (and now mutilate) sheets to help evaluate gear and plan for upgrades.

I still miss some of the functionality which was built into earlier versions of the many spreadsheets which have appeared on this site. I had helped write some macros that copied all upgrade gear to a new "upgrades" sheet. It also included information on the boss who dropped each piece, and let you filter to only show pieces which meet certain criteria (a given slot, or a give boss' drops which are still upgrades, e.g.).

Anyway, I reworked some of that functionality into a standalone sheet that connects up to the combat sheet. The benefits of the standalone sheet is that I don't have to keep re-applying all my changes every time a new version of the combat sheet comes out.

When you click on the upgrade buttons, it will cycle through the various gear choices, and copy any that are an upgrade onto a filterable sheet.

The latest version of the Companion sheet can be found here: Download Ald Combat and Mutilate Companion_3.3.3.xls

Aldriana's combat and mutilate sheets can be found here: http://elitistjerks.com/f78/t39136-c...updated_3_3_a/

---

Usage notes (as of initial release):

* As this sheet uses VBA, it is only compatible with Excel, not with OpenOffice. It may also be incompatible with some Mac versions of excel.
* This version is compatible with version 1.1 of the original combat sheet.
* Put this companion sheet in the same directory as the combat sheet. If you rename it, you can adjust the name on the options tab.
* You can also set an option for how much of a DPS upgrade an item needs to be in order to get copied over.
* The third sheet is just a look-up table which contains all the source location, plus some additional notes.

Hopefully someone else finds this useful. If anyone has suggestions, feel free to propose them, though I don't make any promises.

This is untrue, Aldriana's sheet works just fine in Open Office.

Edit: That said, this tool is not only incompatible with Open Office, it is also, as are other sheets dependent on VBA macros, incompatible with recent versions of Microsoft Office for Mac OS X as well. Just a heads up for those that might not be aware.

Hmm, I wonder why I thought otherwise. I'll edit the initial post.

New version 1.1.2: Ald Combat Companion_1.1.2.xls Combat Companion_1.1.2.xls

Features added:

* Added a Pawn string generator
* Added a sort button to upgrades sheet

Yee, thanks, not that it is that hard to make the pawn string manually, but automated one is awesome, especially calculating sockets

Well, the sockets actually aren't automatically calculated at the moment, I have them in the "manual adjust" section.

I suppose I could automate the color sockets, based on knowing that 32 AP gems are best for most people. I had trouble finding a way to calculate the EP of the 3% damage to crits in Ald's spreadsheet, though, so I ended up just back calculating the EP amount that caused my gemmed pawn calc to equal out. It's a pretty big hack, to be honest.

Version 1.2.1: Ald Combat Companion_1.2.1.xls

* Corrected a few source errors, changed ToC Heroics to use their own sources, added some previously unknown and missing source and type data
* Added a separate axe type
* Updated Pawn to generate socket values automatically and intelligently
* Added this usage notes and changelog page

It's probably worth mentioning that there is no combination of current software that allows VBA execution on a Mac. The older versions Microsoft Office (v.X, 2004 - both PPC code so intel users will be running in Rosetta emulation, thus slow as hell) had VBA capability, but Microsoft removed it in the current Office:Mac 2008.

OpenOffice has never supported VBA, so that's a no-go there. Ald's sheet works fine in both Excel 2008 and the OpenOffice variants on Mac OS X.

Mostly posting this to try to head off the "omg doesn't work on my mac" responses you are likely to get.

Thanks. I do have that documented both in the first posthere and in the new Usage Notes and Changelog tab, for the record, since Feist-Mok mentioned it above.

I wish there was something I could do about it, but the sheet makes extensive use of VBA, so I don't know that I would ever be able to get around it.

Take a look at the link in my signature, I somewhat hacked together a working macro for both Excel and OpenOffice.
It's ugly as hell and it was (and is) my first approach in VBA or whatever, but maybe you can extract some useful information or routines out of it.

Hey, thanks. As you might have guessed, I used your sheet as a springboard for when I created mine in the first place (vis-a-vis putting it on a separate sheet rather than hacking it into the base release and including Pawn strings). I just seem to have forgotten that you built it to be OO capable as well.

I just took a quick look, and see how you have things broken into to sections. Since this basically means writing the OO version of my sheet from scratch, I guess I'll need to take a crash course in OO scripting. I don't suppose you had any particular resource you preferred online?

So, apparently I failed pretty hard. There was a bug in the macro and a typo in the Replace section. This caused there to be 2 T9 helms equipped while only 1 was equipped. This naturally really inflated dps by providing twice the stats(more, actually since it was the heroic version) as well as an automatic T9 2pc for just the helm. Really sorry guys. Here's the corrected version.

Ald Combat Companion_1.2.1_Replace2.xls

When you look up the Name Manager, a ton of the formulas are referencing a "Combat_1.1.xls" workbook, rather than the workbook listed on the options sheet.

I'm not sure whether you mean the edited sheet or my original. I'll give it a look when I get a chance. I'm a little behind because of RL at the moment.

It's the "Ald Combat Companion_1.2.1_Replace2.xls" version, and several versions behind that as well.

>>>>>>>>>>>ignore<<<<<<<<<<<<<<

Thanks for mentioning this in the other thread, it will help me immensely when preparing for a raid night because I can only show the upgrades from what we will be raiding.

EDIT:
I noticed there are two death verdicts that come up in both 25 man ToC and Heroic 25 man ToC each with a different DPS gain listed. Why is this?

Hey dinesh, will there be a version for the final one of 1.3 or shall we use 1.3.1b4? Thanks

Nothing important changed, so you can continue to use b4. I will probably release a 1.3 version at some point which has just a few minor things touched up.

Sorry, didn't see this before. When there is an issue with the name matching, it sometimes causes items to be listed incorrectly, but usually they all show up with the same DPS. Is this still happening for you? I don't see it in my sheet. Perhaps I'll push out the minor 1.3 release sooner rather than later to see if it corrects things for you.

Version 1.3.2: http://www.filefront.com/14906445/Al...nion_1.3.2.xls

* Compatible with v1.3 of Combat sheet (no substantial changes from v1.3.1b4 to this sheet were necessary)
* Minor data fixes

What I'd really like to see in a companion sheet would be an armory import. Much like darkcube has done it directly in Aldriana's sheet.
However, an implementation in a companion sheet is so much more preferrable, for the very reasons you outlined: no need to alter the sheet each and every time a new version is published by Aldriana.

I'm thinking about adding this myself I you don't feel the need to, when and if I find the time (and can persuade myself to deal with the crappy Excel VBA again).

Sounds like a good idea. It is preferable to me that either I do it (though I don't know when that would be, with holidays approachig), or we coordinate some way to have you or darkcube or someone else do it in such as way that we don't end up with two version (i.e. I hand it off to you for some definable period of time), but if you would rather branch off your own version, that's cool. Just don't be surprised if I steal it again later.

As a starting point, I don't think I have made any changes since I released the last version, so now would be a great time if someone wanted to take a crack at it.

(If you're feeling really generous, feel free to hack in the OO code, too, since I haven't really made the time to do so.)