Fleshripper / LBC is higher dps then Silent Crusader / Widow's Fury; about 5% higher dps output in my gear according to the spreadsheet when comparing Mutilate to Combat, so when comparing SR / WD against CG and WD it wouldn't surprise me it's that high.

Roguecycles use their own notation to give a short identification of the sequence of used finishers.


Keeping to the spreadsheet here:

s stands for Slice'n'Dice,
r stands for Rupture and
e stands for Eviscerate (or Envenom if the "Use Envenom instead of Eviscerate"-box is set to TRUE)

Numbers in front of the finishers represent minimum combopoints at wich you will execute the finisher.

4r would therefore mean: "Use rupture as soon as 4+ Combopoints are reached"

The cycle itself is then build as a repeating sequence of the finishers in the stated order.

3s/5r means "SnD with at least 3 CP then Rupture with 5. Repeat."

4e/4r (CttC) means "Evis (Envenom) with 4+ CP then Rupture with 4+ CP. Repeat. SnD is kept running through CttC."

I get the exact opposite in my gear atm... I run Calamaity's Grasp/Widow's Fury 7/51/13 and according to the SS, I drop in dps by about 300 after changing glyphs, rotation and CP builder. I'm not overly concerned as the other raid members are just starting to catch up in DPS with me and I'm starting to place where I'm 'supposed' to on the charts(according to what I read a rogue shoulndt be top 3 dps on every fight).

I have Sinister's Revenge but not Webbed Death as a Shaman snag it from me, who knew they want all of our weapons now?

Thanks for that. I guess I was thrown off because the macro still includes all the old code I wrote to copy the gear to an upgrade worksheet at the same time as it was populating the cell comment (even though the destination sheet no longer even exists, and it was referencing the wrong origin sheet and locations).

Well, I found that utility useful the first time around, so... I implemented it again.

Roguecraft_LK_0.4.4_dbm_m.xlsm - FileFront.com

Changelog:
* Added a Gear_Upgrades sheet
* Modified the macros to copy any upgrades to that sheet, when you run the macro for a given slot

Notes:
* Will only copy item, slot, and dps upgrade amount. Source (and boss) info isn't included in the existing data, so I just chopped it out.
* There is still some code in there which doesn't do what it was originally intended to do (i.e. it refers to a min. DPS upgrade cell which no longer exists). I just left it all in there because it still works (for the moment at least), and maybe someday one of us will fix it.
* Running the macros will likely be slower now that it is copying items as well.
* I didn't re-implement the "upgrade all slots" functionality or the automatic deletion of old data on the upgrade sheet.

P.S. that sound you hear is me banging my head against my desk, because I accidentally saved over my working copy that I had spent a few hours filling in with all the source and boss info for all my upgrades.

This is a JC only trinket that is not appearing in the spreadsheet.

It adds 84 AP when equipped and is used to summon a fighting boar for 30 sec

I don't give a dam for the summoned boar...it's quite boring!

But the trinket comes with two slots for gems (yellow and blue) and has a 12 AP socket bonus, making it quite powerfull.

Earns some consideration in the spreadsheet, but i dont know how to add items to it.

Question that may have been answered, but I didn't find it by searching the thread:

I began my search by looking at my sub-categories of DPS, and wondering why the percentages don't add up to 100%. I had what I felt was a pretty good raid last night and on a lark decided to compare my WWS to the spreadsheet (for what little it is worth, I was only about 500 DPS behind theoretical maximum).

The white, rupture, and envenom damage matches my spreadsheet percentage, but Mutilate and Poison do not by about 6% each. The spreadsheet ends up adding up to 89%, so accounting for rounding and playing error, it would account for the missing percentages and be right in line with WWS.

I took a quick (not detailed) glance at some of the formulas on the DPS worksheet, it appears that the dps values copied in the DPS list are later modified for the totaldps formula, but are copied unmodified to the top of the other sheets in the spreadsheet. Is there a way to resolve this issue?

I would like to know this as well. What should we be looking at in order to determine that one cycle is better than another (e.g. 4e/5r vs 4e/4r on the Xe/Yr (CttC) cycles)?

On my copy of the spreadsheet, I theoretically do max dps with a 5e/4r cycle than a 4e/4r cycle. However, because of Seal Fate and Ruthlessness, I find that if I go with a 4e/4r cycle, depending on where my HfB I can sneak a second 4-5 point Envenom in before my Rupture ends, and I am confident that improves my DPS more. If I mutilate once more to get a 5th point (wasting one-two points in the process), I lose the time to sneak that extra mutilate. Now I make no attempt to keep a "perfect" rotation, instead I attempt refresh SnD and HfB as soon as there is less than 6s remaining.

Moral of the Story, for Mutilate, use rule one: (Mutilate to 4+ combo points)

It's not listed because it's honestly not very good. 84 AP + 2 sockets at 32 EP each works out to a total value of about 148 EP, which is barely half of what the better trinkets give. Almost anything you can pick up in a 5man or raid will be better.

So for combat cycles, which field (or combination of fields) do you look at on the cycles page to determine which is best?

Added version 1.3 of the AEP calc sheet to the download page.


The only change is added support for OpenOffice 3.0.

The AEP calculation should now work with OO3. I didn't test it in OO2.x, and I doubt it'll work there, but let me know to be sure.


Note:
Until I find a way to include both the Excel (VBA) style macro and the OO (Basic) macro within one file, you will have to enable VBA support within OpenOffice.


To do so:
Choose Tools > Options > Load/Save > VBA Properties and enable the Executable code checkbox.
(Source)


The macro code itself is (seems?) to be OO Basic compatible, but I simply couldn't get it to work with both macro "languages", at least not with one button etc, and so my only option was to save the file using Excel.

Also, please check if it still works in Excel versions other than German 2002 (XP). I had to do really really wonky "Excel detection", which I'm not sure will work with other versions/localizations.
If anybody knows how to differentiate between Excel and OO3 with VBA support enable, please let me know (think of some sort of 'browser sniffer').
After a few hours I just gave up searching and simply hacked that piece of crap into the macro.