Vamp Fatale
Please note: This is a naive implementation which I intend to improve over time. Information on the methodology can be found at the bottom of the page.
The Balance - Melee
Opener:
| Job | Average | Max | Total |
|---|---|---|---|
| Samurai | 1541822 | 2145522 | 224 |
| Ninja | 1460163 | 2226338 | 167 |
| Dragoon | 1372971 | 1961125 | 305 |
| Monk | 1248563 | 1890505 | 218 |
| DarkKnight | 1144278 | 1630946 | 462 |
| Viper | 1085075 | 1538030 | 355 |
| Reaper | 995185 | 1664511 | 205 |
| Paladin | 886539 | 1272720 | 507 |
2M Burst:
| Job | Average | Max | Total |
|---|---|---|---|
| Dragoon | 1077867 | 2113223 | 1325 |
| Samurai | 1074289 | 2195297 | 990 |
| Ninja | 1047722 | 2054832 | 714 |
| Monk | 955541 | 1850928 | 938 |
| Viper | 926243 | 1856894 | 1566 |
| Reaper | 897699 | 1762372 | 904 |
| DarkKnight | 849455 | 1744916 | 2010 |
| Paladin | 650265 | 1397834 | 2189 |
The Spear - Ranged
Opener:
| Job | Average | Max | Total |
|---|---|---|---|
| Pictomancer | 1360650 | 2041775 | 194 |
| Machinist | 1098436 | 1458250 | 204 |
| RedMage | 1078032 | 1637295 | 200 |
| Summoner | 915583 | 1724687 | 130 |
| Dancer | 895173 | 1381226 | 338 |
| BlackMage | 881023 | 1414127 | 345 |
| Bard | 811998 | 1173180 | 241 |
| WhiteMage | 689551 | 993097 | 22 |
2M Burst:
| Job | Average | Max | Total |
|---|---|---|---|
| Pictomancer | 1088267 | 2156153 | 747 |
| Machinist | 898771 | 1571691 | 796 |
| RedMage | 877228 | 1724074 | 769 |
| Bard | 862772 | 2066072 | 930 |
| Summoner | 856960 | 1744976 | 514 |
| Dancer | 813391 | 1665958 | 1313 |
| BlackMage | 786814 | 1536321 | 1347 |
| Ninja | 539874 | 1051495 | 637 |
Methodology:
Windows in a fight are only counted towards the total tracked average if the boss is killed.
If a card is played within thirty seconds of the fight starting, the window is considered a part of the opener.
Every time a card is played, the card calculator checks the damage done during the duration of the card by all players. This is compiled into an average (mean) based on the total number of windows checked. Maximum and averages are currently both being calculated at the moment the card is played. In the future, I will include data from the 'ideal' card uses that the card calculator finds.
Every time the average is updated, it's re-calculated using the following:
new_average = old_average + (damage_from_damage_window - old_average) / (number_of_data_points + 1)
Changes I'd Like To Make:
- Ignore outlier data, specifically if the damage is exceptionally low compared to the existing average. This would help with any windows being ended early beacuse of killtime, or any deaths on clear runs.
- Incorporate the 'true' optimal target which the calculator calculates.
- Consider whether a window has a pot active or not.