Damage Formulas / Percentiles

• hero0712 wrote on 2011-01-07 17:56
  what about magic critical chance?
• SozenCratosFocker wrote on 2011-01-10 08:02
  Does the group you got this from have any information or exactly how long attacks take at different character heights?(I want to know if tall chars have the same DPS as short chars, but don't want to test the time myself if someone else already did it)
• Andy-Buddy wrote on 2011-01-10 08:36

  Quote from SozenCratosFocker;284811:

  Does the group you got this from have any information or exactly how long attacks take at different character heights?(I want to know if tall chars have the same DPS as short chars, but don't want to test the time myself if someone else already did it)

  
  
  I'm not sure if they tested it, but it has been tested for a Sword Fiona. I'm guessing the rest of the classes would remain proportional.
  
  The results of the testing are at the bottom of the first post in Bakuryu's own Fiona Guide.
• idefiler6 wrote on 2011-01-10 17:12

  Quote from SozenCratosFocker;284811:

  Does the group you got this from have any information or exactly how long attacks take at different character heights?(I want to know if tall chars have the same DPS as short chars, but don't want to test the time myself if someone else already did it)

  
  
  It actually doesn't effect attack speed per se, it's recovery from an attack you landed that is sped up. Honestly having the longer reach is more advantageous than speeding up normal attacks (many of which will never land anyway).
• fantom wrote on 2011-03-18 04:57
  The damage tables would be a lot easier to read if you expressed them in whole numbers.
  
  Think like a batting average, when you take it literally it's 0.356, but when speaking announcers and fans often refer to a player as "batting three fifty six" / "batting 356".
  
  Just a readability suggestion! The tables are already small, and if I want to do some comparisons between different attacks and characters, I have to remember a lot of decimal places in my head, whole numbers would be much easier to keep track of mentally.
• Andy-Buddy wrote on 2011-03-18 05:57

  Quote from fantom;376785:

  The damage tables would be a lot easier to read if you expressed them in whole numbers.
  
  Think like a batting average, when you take it literally it's 0.356, but when speaking announcers and fans often refer to a player as "batting three fifty six" / "batting 356".
  
  Just a readability suggestion! The tables are already small, and if I want to do some comparisons between different attacks and characters, I have to remember a lot of decimal places in my head, whole numbers would be much easier to keep track of mentally.

  
  
  Whole numbers wouldn't work, as you'd have to keep track of 0s in front, distinguishing .1 and .01.
  
  Percentages may work, since these are percentiles, but you can always do this on your own.
• whocares8128 wrote on 2011-03-18 18:08

  Quote from Andy-Buddy;376835:

  Whole numbers wouldn't work, as you'd have to keep track of 0s in front, distinguishing .1 and .01.
  
  Percentages may work, since these are percentiles, but you can always do this on your own.

  
  
  Whole numbers would work fine. All that's required is determining how precise these numbers are and deciding if the numbers should represent thousandths, ten thousandths, millionths, etc.
  
  Most of the numbers only go out to 3 decimal places, but if we chose thousandths, then we'd have to round Lann's Gliding Fury, among others. But honestly, are we certain it is truly 0.13435 and not 0.13437 or 0.13429? The way the number is represented may be providing a false sense of precision.
  
  If we are so confident in the accuracy and precision of the data, we could even represent them in millionths. In that case Gliding Fury would be 134350, while Windmill would be 4000, and Counterattack would be 100000. Don't forget that 0.02 = 0.020 = 0.0200000 and so on.
• fantom wrote on 2011-03-18 22:20

  Quote from Andy-Buddy;376835:

  Whole numbers wouldn't work, as you'd have to keep track of 0s in front, distinguishing .1 and .01.
  
  Percentages may work, since these are percentiles, but you can always do this on your own.

  
  
  No you wouldn't.
  
  .01 is 10, .1 is 100
  
  And yea it's doable by anyone, it would just be better for quick referencing if it was done in thousandths.
• xJac wrote on 2011-03-19 16:17
  Why bother? The number is in decimal, deal with it. Even putting it into numbers, that means more work when someone wants to calculate the actual damage he is dealing.
  
  It's not like people can't tell which number is bigger as soon as they are put into decimals. And it's not like those numbers are so similar that you have to remember the actual numbers. No one, in the midst of battle, will think, "oh, two normal attacks are around 0.24, and normal mastery r6 gives 40% of bonus damage, comparing to sprint smash, which is....".
  
  The table are there for people to calculate the difference between attack when they are not in the battle, so they somewhat know which has higher damage than another; in better words, it's there for you to use it, not memorize it.
• tai wrote on 2011-05-04 09:01
  Are there values for damage caused by secondary weapons and environmental objects?
  I would look at the guild site myself but i can't seem to load the page.
• dotbeige wrote on 2011-06-07 22:36
  There are new values up for Fiona, Evie, and Karok.
  
  Karok
  
  Fiona
  
  Evie
  
  It'd be nice if it was translated
  
  :2thumb:
• foreignreign wrote on 2011-06-08 02:03

  Quote from dotbeige;471854:

  There are new values up for Fiona, Evie, and Karok.
  
  Karok
  
  Fiona
  
  Evie
  
  It'd be nice if it was translated
  
  :2thumb:

  
  
  Looked at the Fiona chart, particularly hammer since that's the Fiona I know and love and have been wondering about what they did to her after her buff. Numbers look to be:
  
  Honeybee Sting c0: .042
  Honeybee Sting c1: .1
  Honeybee Sting c2: .14
  Honeybee Sting c3: .24
  
  Grand Slam Calla #1: .08
  Grand Slam Calla #2: .1
  
  Orchid Strike: .132
  
  Butterfly Swing 1: .2
  Butterfly Swing >1: .15
  
  Stigma c0: .26
  Stigma c1: .31
  Stigma c2: .38
  Stigma c3: .48
  
  HSC: .024
  
  Normal attacks are the same as before.
  
  So, with a 0 attack speed weapon, it seems like charging Honeybee Sting is actually good (takes about the same amount of time to fully charge a Sting as it does to do a BSwing). However, since attack speed doesn't effect charge speed (unless they changed that), Butterfly Swing reigns supreme with higher speeds, moreso than before, since in the amount of time it takes to Stigma, you can BSwing twice. Which would put you up at .35, while Stigma is still only at .26.
  
  Honestly looks like Stigma sucks based of that, since even if you fully charge up the thing, that's only .48, which is just 3 swings of Butterfly Swing, although I guess the stamina cost of repeated BSwings sucks.
  
  What also has me wondering is that they say that HSC hits three times, yet I've definitely noticed it hitting four times. Downward Counter doesn't have a number, but I think that's because it's so pathetically weak that they weren't able to actually find a number that stuck.
  
  As for sword skills, it looks like a fully charged Rose Thorns is as strong as an Amaranth, however, Rose Thorns has a lower rank cap so Amaranth is still stronger.
  
  Oh, and apparently the second hit of Shield Charge does .06 damage. Which is much better than I previously thought it was.
• Andy-Buddy wrote on 2011-06-08 06:55
  ^^^ About Stigma Vs. Butterfly
  
  Both very situational. If you have a chance to pull off a combo at a distance and wait for him, so you can strike at any time, Stigma is definitely nice. A good combo for following a boss? Butterfly wins for sure.
• tai wrote on 2011-09-27 15:17

  Quote from dotbeige;471854:

  There are new values up for Fiona, Evie, and Karok.
  
  Karok
  
  Fiona
  
  Evie
  
  It'd be nice if it was translated
  
  :2thumb:

  
  
  they have been: http://mabination.com/threads/36079-Damage-Charts
  
  maybe the two threads should be merged?