| Originally Posted by Spider-Dan |
You forgot to correct for Dual Wield II.
(183 + 183) * 0.85 = 311 delay per DW round
(23+23) / 311 = 0.1479....
The 0.1478 was due to a rounding error on my part (forgot to truncate decimal delay after DW coefficient was applied). The actual damage/delay ratio for dual Misericordes is 0.14790996784565916398713826366559. |
Ahh I see, sorry but never bothered to keep up with the Dual Wield numbers and how it modifies. The point either way that was the whole reason I created this database took me 5 min. to set it up, especially since I excluded the extra attributes to the items. It was just purely taking Damage to Delay and having it ready to calculate any way someone would like.
If you wanted the attributes added to use for the calculations then like I said someone else will have to setup the attributes into a database worthy format for mathmatical use. Meaning you break it down to look something like how
MysteryTour did with the food.
Like I said getting Damage to Delay was easy Somepage provided a functional setup to strip that information to make my database, just their attributes were not formatted in a worthy setup to use and I'm not spending the time to get that info. My two tables are setup in the current configuration:
tBows (Table1)
Name [Primary Index]
Bow Type (Shortbow/Longbow)
Level
Damage [Index]
Delay [Index]
tArrows (Table2)
Name [Primary Index]
Level
Damage [Index]
Delay [Index]
Currently it's processing time clocked at 0.00001 so adding more to this should be no problem. I could easily create a Skill Level Table, Monster potential VIT range, and Monster potential Defense range to add and make an equation out of. Like I said I'm offering this so you guys can get a look at all the bows and see which stick out as an intrest to test or whatever.
If anyone really wants to take advantage of what I'm providing I put in spreadsheet format the data I was using and even added a few columns to help demonstrate the database format I'm looking for. If anyone really wants to takes this further here is the two spreadsheet for the two tables, fill in the data and send back to me with how you'd like me to use the data or what formulas you want me to try out and I'll shoot out results of it.
That way you get potentials to look at to see which bows look to be good or not and then test them in game. Anyway here is the two spreadsheets if anyone is really intrested in doing this, fill out the missing attributes to the Bows or Arrows and return to me and what you want me to do to it and I'll do it and send back the results.
Bows (Table1) Arrows (Table2)
EDIT:
Created a Table for doing Player Stat and Skill tests. Funny pulling just Archery range from 0 to 255 (I know it doesn't reach 255, I just got find what it limit was again) and it created out 507k different variations still processing time was only 0.00001. Like I said I'm giving this as a chance for anyone wanting prove out a equation idea to see if it flies with in game results.
Of course as it gets built more can easily add in logics to keep the data result down to more managable sizes.