DDO DPS Calculator!

[Absolute-Omniscience]

Here's an Excel DPS calculator for the community!
Made By:
Absolute-Omniscience and Yargore/Aaxeyu

Download 2.2
http://www.filedropper.com/dpscalcupdate22

Also note, I do not have 100% accurate info on cleave-spam barbarians, so they cannot choose that mode for attacking in the calc currently. If I were to get really accurate numbers for that as well, I would put it in. But for now, it'll have to do with THf or thf-twitch.

Please note that the set builds in there have not been looked at thoroughly. So there might be some errors in their DPS because of some missing numbers in damage, etc. So if you want to calculate your DPS, please look over em and make sure that you've got the correct str, etc.

[mediocresurgeon]

Oooo, shiny! Must try. What type of file is .ODS? I am having a hard time finding the right program.

EDIT:

It would be interesting to see DPS with several targets included in calculations (important for glancing blows, cleave, great cleave, etc) instead of having it restricted to 1v1 combat.

EDIT EDIT:

I see that this will be included in next version. Thanks!

[maddmatt70]

How about a bow with manyshot for both the short term (20 sec fights) and as a weapon swap between bow and twf?

[Yargore]

Oooo, shiny! Must try. What type of file is .ODS? I am having a hard time finding the right program.

You'll need open office. It's free though.

[Roman]

Looks cool, ty!

For those who don't use openoffice and need to convert to .xls go here

[Yargore]

Looks cool, ty!

For those who don't use openoffice and need to convert to .xls go here

Great, we'll add that link to the OP. Thanks!

[Absolute-Omniscience]

How about a bow with manyshot for both the short term (20 sec fights) and as a weapon swap between bow and twf?

We will try to get it included in later versions.

[mediocresurgeon]

You'll need open office. It's free though.
Excell might work.

For those concerned:
Excell does not work. You will need Open Office.

EDIT:
Thanks for the .ODS -> .XLS converter.

[binnsr]

For those concerned:
Excell does not work. You will need Open Office.

EDIT:
Thanks for the .ODS -> .XLS converter.

Just like my spreadsheet character planner doesn't quite work in open office.. it does mostly, but not 100% ..

stupid proprietary formats

[Absolute-Omniscience]

Managed to do a work-around on the Goggle Docs, should work great now for downloading.
Let me know if you can't download it or if you do not get it to work.

The downside is that it's not locked per standard now. So if you want it locked you're gonna have to do it yourself. Same goes for unlocking the marked areas, as they reset while uploading it on Goggle Docs and I can't manage a work-around for that problem.

[TechNoFear]

I only spent a few minutes as I found it hard to use and confusing (no offense intended).

This was mainly due to the way you coded the functions. It is almost impossible to debug (this looks like inexperience as you do not appear to know the higher level functions available).

Look at the 'CHOOSE()' function, much easier than your massive nested IF()'s.

You need to use the advanced features of spreadsheets (ie look-up tables, using $ delimiters for cells in calcs etc)

There is no error checking for OOB values (ie -100% or 200% fort is accepted)

Cells in which data can be entered are not highlighted.

Could you document the constants you are using and where you got them from?

ie swing rates at BAB
You use 83in all calcs (S&B, TWF and THF) and 99.6 if STWF
Did you test these swing rates in BETA over a range of wep types, BABs and styles?

These may not be the same in MOD9 and are extremly difficult to adjust in your xls (you hard coded them into calcs, not drawn from a field as is basic coding practice)

Are the Smites calc correct? (I think you have used the wrong field but not sure)

Does it add an extra Smite for every 90 sec in the time period?

You assume always hit and 100% crit confirm. How can you compare builds with differing 'To Hits'? (ie twitch THF v THF on same build)

[FluffyCalico]

.....

[Yargore]

I only spent a few minutes as I found it hard to use and confusing (no offense intended).

Hard to use? o.O

This was mainly due to the way you coded the functions. It is almost impossible to debug

Look at the 'CHOOSE()' function, much easier than your massive nested IF()'s.

You need to use the advanced features of spreadsheets (ie look-up tables, using $ delimiters for cells in calcs etc)

(this looks like inexperience as you do not appear to know the higher level functions available).

Yea, we're not too experienced with excell sheets. Thank you.

There is no error checking for OOB values (ie -100% or 200% fort is accepted)

I know, but we deemed it not to be necessary.

Cells in which data can be entered are not highlighted.

That's thanks to google docs... Dunno why, but it removes the lock.

Could you document the constants you are using and where you got them from?

ie swing rates at BAB
You use 83in all calcs (S&B, TWF and THF) and 99.6 if STWF
Did you test these swing rates in BETA over a range of wep types, BABs and styles?

These may not be the same in MOD9 and are extremly difficult to adjust in your xls (you hard coded them into calcs, not drawn from a field as is basic coding practice)

Did not test it in beta, as neither of us plays the beta.
The numbers are from Cforces attackspeed thread.

Are the Smites calc correct? (I think you have used the wrong field but not sure)

I'm pretty sure it's correct

Does it add an extra Smite for every 90 sec in the time period?

Yes.

You assume always hit and 100% crit confirm. How can you compare builds with differing 'To Hits'? (ie twitch THF v THF on same build)

We're going to add tohit, THF and fancy graphs soon.

[TechNoFear]

Hard to use?

You have fallen into the 'I've used it so much I know how exactly it works, so everybody else will understand.' trap.

I see it all the time with graduate software engineers (who are still young enough to think they know everything).

Yea, we're not too experienced with excell sheets. Thank you.

I suggest you RTFM then...

Did not test it in beta, as neither of us plays the beta.
The numbers are from Cforces attackspeed thread.

Which have been 'fixed' in MOD9 according to Eladrin.
Are different at each BAB.
etc

Put these all these constants in a field so the user can adjust them (use $ delimiters) as required (from one spot), not embedded in multiple cell calcs.

I'm pretty sure it's correct

Your calcs are so complex (because you used massive nested 'if's) that it is hard to be sure.

I think you have used normal damage not smite damage in one occassion (but the calcs annoyed me so much I gave up testing).

We're going to add tohit, THF and fancy graphs soon.

How about splitters (to keep the titles in view at all times)?
Grazes?
Doing the calcs on a seperate sheet and displaying the results on one? (much clearer to the user)
Many of the fields (damage adds) you use are the same for all builds. Why include them in the main display (just add a constant)?

[TechNoFear]

The AC calcs appear to be trivial (I am playing with a WIN32 C++ DM tool with ODBC DB access in my spare time).

Treat Range == TR
Crit Muliplier == CM
Wep Base Dam == WD
Crit Mult Dam == CD (all constant damage that is multiplied on a confirmed crit ie Str)
Added Dam == AD (all constant damage that is NOT multi on a conf crit ie spells like DF)
Elem Dam == ED (variable damage added each hit and crit ie Holy)
Burst Dam == BD (var dam add only on crit ie Holy Burst)

Then for the full range (hit on a 1 thru hit on a 20) Total Average Damage (TAD) is always;

TAD=((209-(10.5*TR))+(10.5*TR*CM))*(WD+CD)+209*(AD+ED)+(10.5 *TR)*BD

EDIT: Divide by 400 to get the average per swing.

if;
1 always misses
1 confirms a crit

[Absolute-Omniscience]

Version 1.1 is available for download. For more information and download link check the EU Forums.
http://community.codemasters.com/for...d.php?t=374312

[binnsr]

I noticed that this only has a few of the more popular weapons coded in .. A simple solution to coding in all of the weapons is to keep all weapons in a separate table (can be a hidden sheet if you desire) and then do vlookups off of that for things like average damage, average crit, etc.

You could also convert all of the Yes/No entries to a simple validation selection.

I've done some of the work here but am out of time to play with it.

[Absolute-Omniscience]

I noticed that this only has a few of the more popular weapons coded in .. A simple solution to coding in all of the weapons is to keep all weapons in a separate table (can be a hidden sheet if you desire) and then do vlookups off of that for things like average damage, average crit, etc.

You could also convert all of the Yes/No entries to a simple validation selection.

I've done some of the work here but am out of time to play with it.

I've put up some more weapons in the 1.1 version as well as some other nice features, including a dropdown for the weapon selection.
I plan to add more weapon types in the future, but as I see it now no more are required.

I've thought about changing the yes/no entries to check boxes. Though it would require a **** lot of work, and copying a build would be more of a pain. As those check boxes would be copied with the data.

[Xionanx]

I happen to agree your spreadsheet is complicated and hard to understand. Not to mention I feel like your over complicating things and using confusing language. If your goal is to make this spreadsheet simpler and easier to understand.....

Here's a few suggestions:

Make "Fighting Style" a dropdown selection menu with Unarmed, TWF, THF, and Single Weapon as your selections.

Change "Weapon Type" to Weapon Dice. Ie 1d4, 1d6, 1d8, 1d10, 1d12, 2d4, etc.. so it covers ALL weapons in the game and possibly new weapons added later. (as you have it now I have no idea if DA is a regular or greensteel version of the Dwarven Axe? What if I want to see my DPS gain when compared between the two?) This change would also let you get rid of all your if's and simply do the 1Dx conversion math. IE.. for a 1d6, the average is, 1/6 + 2/6 + 3/6 + 4/6 + 5/6 + 6/6 = 21/6 = 3.5 or in Open Office "X*(MEDIAN(1;Y))" where X= Number of Dice (1) and Y=Die Type (D6). This will make your life a LOT simpler!

Change "Extra Critical Threat Range" to simply be "Critical Threat Range" where you type in 20, 19-20, 18-20, so on and so forth.

Change "Extra Critical Multiplier" to simply be "Critical Multiplier" where you type in the multiplier.. 2, 3, 4.. so on and so forth.

You currently have an examply next to "Extra Critical Multiplier" that reads (19-20) *** does that mean?

You have TWO YES/NO selections for both Elemental Burst/Alignment Burst. Why two? Where is this associated with elemental damage? It doesn't follow a logical progression at all. Why not simply have 2 boxes: One for "Extra Damage Dice" and one for "Extra Damage on Crit"

You then proceed to break down each and every single source of +Damage for the base weapon, though I cant figure out why? Why not simply have One space for "Bonus Damage on Hit" and be done with it?

Personally I have to agree with Tech.. you guys are making it/using it so much you cant see how someone who sees it for the first time might be confused or find it cumbersome.

I recommend you look at DDO Melee Damage Tool for inspiration on useability.

I would love to see it updated and working for mod 9 or something just as easy to use/figure out.

[Absolute-Omniscience]

I happen to agree your spreadsheet is complicated and hard to understand. Not to mention I feel like your over complicating things and using confusing language. If your goal is to make this spreadsheet simpler and easier to understand.....

First of all, thanks for the feedback.

Question; are these complains about the 1.1 version or the 1.0 version?

Here's a few suggestions:

Make "Fighting Style" a dropdown selection menu with Unarmed, TWF, THF, and Single Weapon as your selections.

Yes, this is planned to be implented in the future.

Change "Weapon Type" to Weapon Dice. Ie 1d4, 1d6, 1d8, 1d10, 1d12, 2d4, etc.. so it covers ALL weapons in the game and possibly new weapons added later. (as you have it now I have no idea if DA is a regular or greensteel version of the Dwarven Axe? What if I want to see my DPS gain when compared between the two?) This change would also let you get rid of all your if's and simply do the 1Dx conversion math. IE.. for a 1d6, the average is, 1/6 + 2/6 + 3/6 + 4/6 + 5/6 + 6/6 = 21/6 = 3.5 or in Open Office "X*(MEDIAN(1;Y))" where X= Number of Dice (1) and Y=Die Type (D6). This will make your life a LOT simpler!

Actually, you have a point. But still not, I think having to know what crit range and what crit multiplier a weapon has requires more knowledge than knowing what DA stands for.
I will however add "GS" or "Greensteel" before the weapons, so it's easier to understand.

Change "Extra Critical Threat Range" to simply be "Critical Threat Range" where you type in 20, 19-20, 18-20, so on and so forth.
Change "Extra Critical Multiplier" to simply be "Critical Multiplier" where you type in the multiplier.. 2, 3, 4.. so on and so forth.

Works, but once again seems easier to just use the dropdown and select a weapon and all things regarding it (dice, crit range, crit multipier) is automatically done for you. Will take it into consideration though.

You currently have an examply next to "Extra Critical Multiplier" that reads (19-20) *** does that mean?

Ah, thought it was obvious. Well it's the barbarian extra cititicals, might change 19-20 till something like "Frenzied Berserker bonus".

You have TWO YES/NO selections for both Elemental Burst/Alignment Burst. Why two? Where is this associated with elemental damage? It doesn't follow a logical progression at all. Why not simply have 2 boxes: One for "Extra Damage Dice" and one for "Extra Damage on Crit"

Not everyone knows the exact forumal for how elemental damage or alignment damage is done. So just typing Yes to either is a lot easier, imo.
Elemental damage for exampel is 5,5*(Crit multiplier-1). And Alignmnent is 3,5*(Crit multiplier + 1).

You then proceed to break down each and every single source of +Damage for the base weapon, though I cant figure out why? Why not simply have One space for "Bonus Damage on Hit" and be done with it?

This is a MUST in my book. If you don't break down the +damage the viewer will never know what he have missed. And if posted on the forums, the viewers will never know if he has forgotten anything or "cheated" with the calculation to make it biased.