Jump to content

10 warzones of hits (data)

Highcommander

By Highcommander
in PvP

 Share

Recommended Posts

Highcommander

Highcommander

Posted
Posted (edited)

Here is 10 warzones of hits:

 

This was recorded from my Jedi Sage which has about 1300 expertise for this test (mostly WH gear with a few EWH parts, and using a PVE belt with 63's). The Sage is a PvE hybrid spec (1/12/28) - http://www.torhead.com/skill-calc#600oZfcM0bZfMfRs0krc.2

 

My goal here was not a focus on damage or capabilities, but rather just to gather some general data on damage taken ("realworld" data) from opponents. I wanted a sample that was indicative of what I face on a normal day to day while solo queing for pvp.

 

Here is the torparse data. http://www.torparse.com/a/119422

 

 

And here I have compiled just hits from the data (damage taken):

https://docs.google.com/spreadsheet/ccc?key=0AoBwfmxohbZLdDdmQ0VCaWhSU3JVSHIwQ1piVncwWlE&usp=sharing

 

Top 50 Hit size in order:

(EACH ATTACK TYPE CAN HAVE ONLY 1 SPOT IN THE LIST, for example if I got hit with 25+ smashes for well over 5k only the biggest is listed)

 

  1. 5994 Smash
  2. 5335 Fire Trap Burn
  3. 4882 Ambush
  4. 4725 Blade Storm
  5. 4537 Rail Shot
  6. 4354 Force Scream
  7. 4153 Thermal Detonator
  8. 4147 Merciless Slash
  9. 4076 Takedown
  10. 3892 Vicious Throw
  11. 3839 Heatseeker Missiles
  12. 3609 Hidden Strike
  13. 3602 Followthrough
  14. 3598 Shock
  15. 3431 Death Field
  16. 3426 Backstab
  17. 3418 Explosive Probe (Tech)
  18. 3134 Rocket Punch
  19. 3093 Annihilate
  20. 3068 Master Strike
  21. 2982 Maul
  22. 2971 Shoot First
  23. 2914 Orbital Strike
  24. 2881 Snipe
  25. 2735 Back Blast
  26. 2728 Assassinate
  27. 2527 Tracer Missile
  28. 2515 Dispatch
  29. 2513 Blade Rush
  30. 2436 Ravage
  31. 2365 Vicious Slash
  32. 2348 Shiv
  33. 2348 Telekinetic Wave
  34. 2311 Explosive Dart
  35. 2299 Project
  36. 2261 Unload
  37. 2196 Force Push
  38. 2134 Crushing Darkness
  39. 2077 Shocked
  40. 2013 Flame Burst
  41. 1922 Saber Throw
  42. 1920 Crushed (Force)
  43. 1853 Impale
  44. 1834 Wither
  45. 1826 Mind Crush
  46. 1777 Fusion Missile
  47. 1773 Obliterate
  48. 1771 Series of Shots
  49. 1722 Crippling Throw
  50. 1696 Crushing Blow

 

Here is a graph plot which illustrates the size of a hit (bubble size) vs total damage and number of hits (Y and X axis):

 

http://oi48.tinypic.com/5wq37.jpg

 

Here is a list of total damage for top 25 sorted by highest:

 

Total Damage / Action

 

  1. 107866 Burning (Tech)
  2. 102247 Flame Burst
  3. 92960 Shocked
  4. 85483 Smash
  5. 85297 Rail Shot
  6. 77435 Shock
  7. 71929 Poisoned (Tech)
  8. 65553 Crushed
  9. 65328 Ambush
  10. 64649 Crushed (Force)
  11. 57725 Snipe
  12. 55332 Series of Shots
  13. 50136 Unload
  14. 46633 Ravage
  15. 41045 Blade Storm
  16. 38756 Thermal Detonator
  17. 32525 Heatseeker Missiles
  18. 31380 Tracer Missile
  19. 30595 Cull
  20. 27754 Takedown
  21. 27325 Explosive Probe (Tech)
  22. 27254 Ion Pulse

 

Here is a pie chart showing biggest hits:

 

http://oi50.tinypic.com/2qda5p5.jpg

 

And finally here is a graph that shows hit size VS total damage:

 

http://oi48.tinypic.com/t9bal3.jpg

 

 

The idea here isn't to make any assumptions (I am sure you guys will draw many conclusions from the data.) I would however like to say that I do realize a 10 game sample size is pretty small and this is clearly illustrated by the fact that I was only hit around 3000 times total. Of those 3000 hits I would estimate that only about 20% of all abilities were used on me (attacks from all classes).

 

I do think that about 90% of "normal situation" pvp attacks were accounted for in this data. Interestingly enough, only 32 attacks hit me for 5k. 1 was a fire trap burn in a huttball (as i ran across), 1 was a "kill" for 75k damage (I was knocked off of the upper platform onto the ball spawn and died instantly) and 30 were Smash. Of importance is also the fact that no attack hit me for more than 5994!

 

I would also add that if you look at the attacks on the graph, SMASH accounts for only 0.01% of all attacks done to me. Of total damage it accounts for only 0.04% of damage rendered. Now, I am not saying Smash isn't something to look at however from my perspective it rarely affects my day to day warzone ques.

 

As requested here are the top 100 hits (allowing individual hits to make the chart more than once):

 

  1. 78464 [Kill {2852850421989376}]
  2. 5994 [smash {807801743998976}]
  3. 5404 [smash {807801743998976}]
  4. 5314 [smash {807801743998976}]
  5. 5246 [smash {807801743998976}]
  6. 5171 [smash {807801743998976}]
  7. 5164 [smash {807801743998976}]
  8. 4918 [smash {807801743998976}]
  9. 4892 [smash {807801743998976}]
  10. 4882 [Ambush {814781065854976}]
  11. 4725 [blade Storm {1191698805817344}]
  12. 4631 [blade Storm {1191698805817344}]
  13. 4614 [Ambush {814781065854976}]
  14. 4553 [blade Storm {1191698805817344}]
  15. 4537 [Rail Shot {814278554681344}]
  16. 4513 [Ambush {814781065854976}]
  17. 4508 [smash {807801743998976}]
  18. 4428 [Ambush {814781065854976}]
  19. 4414 [Ambush {814781065854976}]
  20. 4405 [Rail Shot {814278554681344}]
  21. 4358 [smash {807801743998976}]
  22. 4354 [Force Scream {998270658674688}]
  23. 4353 [blade Storm {1191698805817344}]
  24. 4336 [Ambush {814781065854976}]
  25. 4283 [Ambush {814781065854976}]
  26. 4188 [Rail Shot {814278554681344}]
  27. 4153 [Thermal Detonator {2027100009660416}]
  28. 4147 [Merciless Slash {1261715362676736}]
  29. 4085 [Thermal Detonator {2027100009660416}]
  30. 4076 [Takedown {987683564290048}]
  31. 4071 [Rail Shot {814278554681344}]
  32. 4066 [Takedown {987683564290048}]
  33. 4065 [Rail Shot {814278554681344}]
  34. 4042 [blade Storm {1191698805817344}]
  35. 4039 [blade Storm {1191698805817344}]
  36. 4003 [smash {807801743998976}]
  37. 3981 [Takedown {987683564290048}]
  38. 3903 [Rail Shot {814278554681344}]
  39. 3892 [Vicious Throw {2145542322782208}]
  40. 3884 [Rail Shot {814278554681344}]
  41. 3864 [smash {807801743998976}]
  42. 3863 [Takedown {987683564290048}]
  43. 3839 [Heatseeker Missiles {814592087293952}]
  44. 3794 [Heatseeker Missiles {814592087293952}]
  45. 3781 [Thermal Detonator {2027100009660416}]
  46. 3781 [smash {807801743998976}]
  47. 3721 [Rail Shot {814278554681344}]
  48. 3686 [Takedown {987683564290048}]
  49. 3632 [blade Storm {1191698805817344}]
  50. 3609 [Hidden Strike {2200792782077952}]
  51. 3608 [blade Storm {1191698805817344}]
  52. 3602 [Followthrough {2300994369093632}]
  53. 3598 [shock {808308550139904}]
  54. 3529 [Heatseeker Missiles {814592087293952}]
  55. 3509 [smash {807801743998976}]
  56. 3485 [Thermal Detonator {2027100009660416}]
  57. 3479 [Rail Shot {814278554681344}]
  58. 3468 [Thermal Detonator {2027100009660416}]
  59. 3460 [Heatseeker Missiles {814592087293952}]
  60. 3436 [blade Storm {1191698805817344}]
  61. 3431 [Death Field {808433104191488}]
  62. 3429 [Thermal Detonator {2027100009660416}]
  63. 3426 [backstab {814789655789568}]
  64. 3418 [Explosive Probe (Tech) {814815425593688}]
  65. 3385 [Thermal Detonator {2027100009660416}]
  66. 3374 [Death Field {808433104191488}]
  67. 3370 [backstab {814789655789568}]
  68. 3353 [Followthrough {2300994369093632}]
  69. 3314 [shock {808308550139904}]
  70. 3279 [Explosive Probe (Tech) {814815425593688}]
  71. 3249 [Rail Shot {814278554681344}]
  72. 3239 [shock {808308550139904}]
  73. 3228 [Explosive Probe (Tech) {814815425593688}]
  74. 3226 [shock {808308550139904}]
  75. 3223 [shock {808308550139904}]
  76. 3213 [shock {808308550139904}]
  77. 3193 [shock {808308550139904}]
  78. 3189 [Obliterate {1009763991158784}]
  79. 3143 [Force Scream {998270658674688}]
  80. 3134 [Rocket Punch {814300029517824}]
  81. 3124 [Rocket Punch {814300029517824}]
  82. 3118 [smash {807801743998976}]
  83. 3093 [Annihilate {808123866546176}]
  84. 3068 [Master Strike {812139660967936}]
  85. 3066 [Force Scream {998270658674688}]
  86. 3050 [smash {807801743998976}]
  87. 2991 [Death Field {808433104191488}]
  88. 2982 [Maul {808269895434240}]
  89. 2971 [shoot First {807256283152384}]
  90. 2951 [Rocket Punch {814300029517824}]
  91. 2914 [Orbital Strike {2145301804613632}]
  92. 2886 [Explosive Probe (Tech) {814815425593688}]
  93. 2881 [snipe {814892735004672}]
  94. 2879 [Rail Shot {814278554681344}]
  95. 2876 [Master Strike {812139660967936}]
  96. 2856 [Hidden Strike {2200792782077952}]
  97. 2821 [Ambush {814781065854976}]
  98. 2793 [Explosive Probe (Tech) {814815425593688}]
  99. 2767 [snipe {814892735004672}]
  100. 2764 [Vicious Throw {2145542322782208}]

Edited by Highcommander
Link to comment
Share on other sites
ktkenshinx

ktkenshinx

Posted
Posted

I appreciate your use of actual data, and your attempt to do a thorough job of data collection. Unfortunately, I am worried about your sample size of just 10 WZs. This isn't just a statistical point. For example, 100 WZs of data is still really not a statistically adequate sample size, but I would be more than happy to see that many cases in a dataset. But over just 10 WZs, it's really hard to capture the "reality" of PvP damage output.

 

When did you play these WZs? Were they played consecutively, or over the course of a few days? Do you only play in the morning/night? Or do you balance your WZ times? Do you leave WZs that are going badly? All of these factors can really distort your findings in a sample size of just 10 WZs. Maybe you only play in the morning when the less geared, unguilded players are online. Maybe you only play on weekday when players are unlikely to assemble full 4 man premades. There is just so much room for bias when you just look at 10 WZs. Given that Smash only appears ONCE in the entire top 50 hits, it looks like you just played against 1 smasher in all 10 WZs. Average would probably be about 1-2 PER Warzone, not 1-2 in all 10 WZs. That alone is going to skew things.

Link to comment
Share on other sites
Highcommander

Highcommander

Posted
  • Author
Posted
I appreciate your use of actual data, and your attempt to do a thorough job of data collection. Unfortunately, I am worried about your sample size of just 10 WZs. This isn't just a statistical point. For example, 100 WZs of data is still really not a statistically adequate sample size, but I would be more than happy to see that many cases in a dataset. But over just 10 WZs, it's really hard to capture the "reality" of PvP damage output.

 

When did you play these WZs? Were they played consecutively, or over the course of a few days? Do you only play in the morning/night? Or do you balance your WZ times? Do you leave WZs that are going badly? All of these factors can really distort your findings in a sample size of just 10 WZs. Maybe you only play in the morning when the less geared, unguilded players are online. Maybe you only play on weekday when players are unlikely to assemble full 4 man premades. There is just so much room for bias when you just look at 10 WZs. Given that Smash only appears ONCE in the entire top 50 hits, it looks like you just played against 1 smasher in all 10 WZs. Average would probably be about 1-2 PER Warzone, not 1-2 in all 10 WZs. That alone is going to skew things.

 

First, the top hits just allows 1 from each ability so smash can ONLY appear 1 time in it.... its not a collection of the top 50 hits as in it does not have all 30 smashes in it.... I realize now the name of the list could have been better chosen. As far as smash goes, as the data shows there were 30 hits total.

 

As far as statistically small sample I agree 100% that it is far too small. However for now it will have to do because compiling 10 warzones of attacks is not easily done. I have to parse the logs, then physically copy each attack into a data chart. 10 warzones took me an entire day to compile and even something as small as 100 would take me at least a week.

 

If someone knows of an easier method I would love to get some larger samples put together!

 

I would only add the data was pretty consistent to what I am use to.

Link to comment
Share on other sites
Cowflab

Cowflab

Posted
Posted
It's just 10 warzones, I'm going to guess I didn't get into a scrap with a decent PT pyro.

 

Same for assassins. I hit bigger mauls than that in a tank spec with tank gear. When I run deception in power gear 6k mauls come pretty often.

Link to comment
Share on other sites
Highcommander

Highcommander

Posted
  • Author
Posted
Same for assassins. I hit bigger mauls than that in a tank spec with tank gear. When I run deception in power gear 6k mauls come pretty often.

 

I don't think i've been hit with a 6k maul... at least I don't remember it. Again, I know it's not the biggest sample I can get. I will try for a larger sample... let's say 100 warzones next time. Although this will take me at least a week to put together.

Link to comment
Share on other sites
ktkenshinx

ktkenshinx

Posted
Posted
I don't think i've been hit with a 6k maul... at least I don't remember it. Again, I know it's not the biggest sample I can get. I will try for a larger sample... let's say 100 warzones next time. Although this will take me at least a week to put together.

That's the thing with data-driven analysis, especially in the data-bereft world of an MMO forum. We are always so tempted to publish and post our results immediately, but in doing so we tend to just draw criticism about sample size and bias. So even if you have a good point overall, readers just don't notice it.

 

I am doing an an analysis of premades in WZs, and although I wanted to post my findings a week ago, I would much rather collect a full month of data. Your analysis would be better served with similar patience (it's a great idea!). In the past, I have definitely jumped the gun and been met with similar sample-size criticisms.

 

Also, the fact that you are not showing individual, discrete attacks is really misleading. Your top 10 list should read something like 1) Smash, 2) Maul, 3) Smash, 4) Railshot, 5) Takedown, 6) Smash, 7) Railshot, etc., with lots of repetitions. This would show people not only how hard attacks are hitting, but also their frequency in the overall sample. Both frequency and magnitude are hugely important in making conclusions like the ones you want to make.

Link to comment
Share on other sites
JackNader

JackNader

Posted
Posted

Judging by those numbers, the guy is either vsing teams of recruit geared scrubs or he is simply making those numbers up.

 

5994 smash? add at least 1000 to that.

3.4k deathfield? lol add 1000 to that.

2982 maul? lol add 2000 to that.

2435 ravage tick? Rotfl. The last tick of ravage will hit your *** for over 5k.

Link to comment
Share on other sites
Cowflab

Cowflab

Posted
Posted
I don't think i've been hit with a 6k maul... at least I don't remember it. Again, I know it's not the biggest sample I can get. I will try for a larger sample... let's say 100 warzones next time. Although this will take me at least a week to put together.

 

6k mauls aren't a mythical unicorn number. Especially on a sage. Aside from smash, maul could possibly be the second highest damaging ability in the game, especially with a setup on a sage from a mad maul assassin with unearthed knowledge proc'd. The problem is that the spec takes an extra bit of skill to play successfully. As the previous poster said, you'd be better served grabbing a larger sample size. Just from an assassin stand point, I can see that the majority of assassins you faced were 23/1/17 spec'd based on small maul damage and death field. Either way, you'll know when you run up against a good deception/deception hybrid on a sage because death will come early and often. ;)

Link to comment
Share on other sites
Highcommander

Highcommander

Posted
  • Author
Posted
That's the thing with data-driven analysis, especially in the data-bereft world of an MMO forum. We are always so tempted to publish and post our results immediately, but in doing so we tend to just draw criticism about sample size and bias. So even if you have a good point overall, readers just don't notice it.

 

I am doing an an analysis of premades in WZs, and although I wanted to post my findings a week ago, I would much rather collect a full month of data. Your analysis would be better served with similar patience (it's a great idea!). In the past, I have definitely jumped the gun and been met with similar sample-size criticisms.

 

Also, the fact that you are not showing individual, discrete attacks is really misleading. Your top 10 list should read something like 1) Smash, 2) Maul, 3) Smash, 4) Railshot, 5) Takedown, 6) Smash, 7) Railshot, etc., with lots of repetitions. This would show people not only how hard attacks are hitting, but also their frequency in the overall sample. Both frequency and magnitude are hugely important in making conclusions like the ones you want to make.

 

Frequency can be important, but I opted for total damage (which is a byproduct of frequency). Again smash is represented by its largest hit, i list it as having hit 30 times out of 3000 attacks and I also list its total damage (85483) simple math tells my reader it hit on average of 2849 damage. Do people need to see each individual smash? I don't think benefits anyone... but it can be added with my next attempt at this.

 

I can see the appeal of having a larger sample size, although again, compiling 10 warzones isn't just a click and paste method. The attacks have to be stripped out of the logs and this takes tremendous amounts of time for me. I imagine if it was super easy everyone would be sharing their data.

Link to comment
Share on other sites
Highcommander

Highcommander

Posted
  • Author
Posted
Judging by those numbers, the guy is either vsing teams of recruit geared scrubs or he is simply making those numbers up.

 

5994 smash? add at least 1000 to that.

3.4k deathfield? lol add 1000 to that.

2982 maul? lol add 2000 to that.

2435 ravage tick? Rotfl. The last tick of ravage will hit your *** for over 5k.

 

Numbers don't lie, check the torparse my entire logs there. It is entirely possible in this 10 warzone sample the players didn't meet up to your standards. Let's be civil about it though, saying "he is simply making those numbers up" is crazy talk. I provided my logs as evidence.

Link to comment
Share on other sites
ktkenshinx

ktkenshinx

Posted
Posted
Frequency can be important, but I opted for total damage (which is a byproduct of frequency). Again smash is represented by its largest hit, i list it as having hit 30 times out of 3000 attacks and I also list its total damage (85483) simple math tells my reader it hit on average of 2849 damage. Do people need to see each individual smash? I don't think benefits anyone... but it can be added with my next attempt at this.

Listing, or somehow showing, individual smashes (or other attacks) are extremely important IF your question is "Is smash overpowered?" or "is attack ____ overpowered?". For example, if over the course of 100 WZs we only saw 1 smash hit for 6k, we might just assume that this guy was in the best possible gear getting the highest possible damage values and it was a total aberration. But if you are consistently seeing smashers hit for 5k+ and no one else is consistently hitting for 5k+, then that says something entirely different. You even mention yourself as a parenthetical, "(EACH ATTACK TYPE CAN HAVE ONLY 1 SPOT IN THE LIST, for example I got hit with 25+ smashes for well over 5k, yet the biggest was 5994)". That 25+ smash information is really important! The same goes for Rail Shot, Maul, Takedown, Assassinate, etc. The goal is not just to see how hard an attack hits every once and a while. It is to see how REGULARLY the attack is hitting as hard as it is.

I can see the appeal of having a larger sample size, although again, compiling 10 warzones isn't just a click and paste method. The attacks have to be stripped out of the logs and this takes tremendous amounts of time for me. I imagine if it was super easy everyone would be sharing their data.

Again, I appreciate your approach and don't want to come off as insulting you. You seem like a smart, reasonable, thorough individual, and I don't want to offend you.

 

But that being said, if you don't have the time/energy/resources to do a proper evaluation with a big sample size (100 WZs or 1 month of WZs, for example), then maybe it isn't worth doing the research at all. 10 WZs is just too small. I have won 10 WZs in a row some days for a 100 win percentage. But other days, I have lost 6-7 in a row. And my overall win percentage is at about 60%, which is nowhere near those numbers. The point is, in 10 WZs you can't extrapolate anything with certainty. Damage is a big, important, and meaningful question on these forums (as I am sure you know). If you want to treat it with data (and as I said, it's a great idea/approach), you need to do so in a systematic and thorough way.

 

Again, I can't emphasize enough that I am not trying to offend you or argue with you. I am simply saying that if you don't have the time/energy/resources/interest in doing a "proper" analysis, then you shouldn't do a short and potentially misleading one.

Link to comment
Share on other sites
Highcommander

Highcommander

Posted
  • Author
Posted

Updated to add a "top 100" chart with hits allowed in more than once:

 

  1. 78464 [Kill {2852850421989376}]
  2. 5994 [smash {807801743998976}]
  3. 5404 [smash {807801743998976}]
  4. 5314 [smash {807801743998976}]
  5. 5246 [smash {807801743998976}]
  6. 5171 [smash {807801743998976}]
  7. 5164 [smash {807801743998976}]
  8. 4918 [smash {807801743998976}]
  9. 4892 [smash {807801743998976}]
  10. 4882 [Ambush {814781065854976}]
  11. 4725 [blade Storm {1191698805817344}]
  12. 4631 [blade Storm {1191698805817344}]
  13. 4614 [Ambush {814781065854976}]
  14. 4553 [blade Storm {1191698805817344}]
  15. 4537 [Rail Shot {814278554681344}]
  16. 4513 [Ambush {814781065854976}]
  17. 4508 [smash {807801743998976}]
  18. 4428 [Ambush {814781065854976}]
  19. 4414 [Ambush {814781065854976}]
  20. 4405 [Rail Shot {814278554681344}]
  21. 4358 [smash {807801743998976}]
  22. 4354 [Force Scream {998270658674688}]
  23. 4353 [blade Storm {1191698805817344}]
  24. 4336 [Ambush {814781065854976}]
  25. 4283 [Ambush {814781065854976}]
  26. 4188 [Rail Shot {814278554681344}]
  27. 4153 [Thermal Detonator {2027100009660416}]
  28. 4147 [Merciless Slash {1261715362676736}]
  29. 4085 [Thermal Detonator {2027100009660416}]
  30. 4076 [Takedown {987683564290048}]
  31. 4071 [Rail Shot {814278554681344}]
  32. 4066 [Takedown {987683564290048}]
  33. 4065 [Rail Shot {814278554681344}]
  34. 4042 [blade Storm {1191698805817344}]
  35. 4039 [blade Storm {1191698805817344}]
  36. 4003 [smash {807801743998976}]
  37. 3981 [Takedown {987683564290048}]
  38. 3903 [Rail Shot {814278554681344}]
  39. 3892 [Vicious Throw {2145542322782208}]
  40. 3884 [Rail Shot {814278554681344}]
  41. 3864 [smash {807801743998976}]
  42. 3863 [Takedown {987683564290048}]
  43. 3839 [Heatseeker Missiles {814592087293952}]
  44. 3794 [Heatseeker Missiles {814592087293952}]
  45. 3781 [Thermal Detonator {2027100009660416}]
  46. 3781 [smash {807801743998976}]
  47. 3721 [Rail Shot {814278554681344}]
  48. 3686 [Takedown {987683564290048}]
  49. 3632 [blade Storm {1191698805817344}]
  50. 3609 [Hidden Strike {2200792782077952}]
  51. 3608 [blade Storm {1191698805817344}]
  52. 3602 [Followthrough {2300994369093632}]
  53. 3598 [shock {808308550139904}]
  54. 3529 [Heatseeker Missiles {814592087293952}]
  55. 3509 [smash {807801743998976}]
  56. 3485 [Thermal Detonator {2027100009660416}]
  57. 3479 [Rail Shot {814278554681344}]
  58. 3468 [Thermal Detonator {2027100009660416}]
  59. 3460 [Heatseeker Missiles {814592087293952}]
  60. 3436 [blade Storm {1191698805817344}]
  61. 3431 [Death Field {808433104191488}]
  62. 3429 [Thermal Detonator {2027100009660416}]
  63. 3426 [backstab {814789655789568}]
  64. 3418 [Explosive Probe (Tech) {814815425593688}]
  65. 3385 [Thermal Detonator {2027100009660416}]
  66. 3374 [Death Field {808433104191488}]
  67. 3370 [backstab {814789655789568}]
  68. 3353 [Followthrough {2300994369093632}]
  69. 3314 [shock {808308550139904}]
  70. 3279 [Explosive Probe (Tech) {814815425593688}]
  71. 3249 [Rail Shot {814278554681344}]
  72. 3239 [shock {808308550139904}]
  73. 3228 [Explosive Probe (Tech) {814815425593688}]
  74. 3226 [shock {808308550139904}]
  75. 3223 [shock {808308550139904}]
  76. 3213 [shock {808308550139904}]
  77. 3193 [shock {808308550139904}]
  78. 3189 [Obliterate {1009763991158784}]
  79. 3143 [Force Scream {998270658674688}]
  80. 3134 [Rocket Punch {814300029517824}]
  81. 3124 [Rocket Punch {814300029517824}]
  82. 3118 [smash {807801743998976}]
  83. 3093 [Annihilate {808123866546176}]
  84. 3068 [Master Strike {812139660967936}]
  85. 3066 [Force Scream {998270658674688}]
  86. 3050 [smash {807801743998976}]
  87. 2991 [Death Field {808433104191488}]
  88. 2982 [Maul {808269895434240}]
  89. 2971 [shoot First {807256283152384}]
  90. 2951 [Rocket Punch {814300029517824}]
  91. 2914 [Orbital Strike {2145301804613632}]
  92. 2886 [Explosive Probe (Tech) {814815425593688}]
  93. 2881 [snipe {814892735004672}]
  94. 2879 [Rail Shot {814278554681344}]
  95. 2876 [Master Strike {812139660967936}]
  96. 2856 [Hidden Strike {2200792782077952}]
  97. 2821 [Ambush {814781065854976}]
  98. 2793 [Explosive Probe (Tech) {814815425593688}]
  99. 2767 [snipe {814892735004672}]
  100. 2764 [Vicious Throw {2145542322782208}]

Link to comment
Share on other sites
Cowflab

Cowflab

Posted
Posted
Like I said before, and others as well, a larger sample pool is required. Looking at the assassin numbers alone is enough for me to make that determination. You didn't face a single non 23/1/17 assassin in those 10 games. There's no telling how many others aren't properly represented. But if these numbers are to be taken seriously, I look forward to our buff. :p
Link to comment
Share on other sites
ObscureKnight

ObscureKnight

Posted
Posted (edited)
I find this interesting since my sage has 1300 exp, I am full healer build and I get nailed with smashes in the 7k range at least several times a day. I am wondering what you are up against. I know that I tend to get 5k range smashes on me in the mornings when the real pvp teams on our server are are not online. When they show up, you can see the difference. SO I am curious to your sample times vs, who is online at that time. Edited by ObscureKnight
typo
Link to comment
Share on other sites
Cowflab

Cowflab

Posted
Posted (edited)
I find this interesting since my sage has 1300 exp, I am full healer build and I get nailed with smashes in the 7k range at least several times a day. I am wondering what you are up against. I know that I tend to get 5k range smashes on me in the mornings when the real pvp teams on our server are are not online. When they show up, you can see the difference. SO I am curious to your sample times vs, who is online at that time.

 

This may be a bit rude of me to say, but RP PvE servers aren't exactly the "creme de la crop" in PvP if you get what I mean...

Edited by Cowflab
Link to comment
Share on other sites
ObscureKnight

ObscureKnight

Posted
Posted (edited)
This may be a bit rude of me to say, but RP PvE servers aren't exactly the "creme de la crop" in PvP if you get what I mean...

 

Then I should mention that I do have a 50 shadow and trooper on your server (EB) and have seen the same thing there with the lol smash monkeys.

 

However the main server I am on now is a PVE server, and it is the same thing I saw months ago over on the Ebon.

Edited by ObscureKnight
Link to comment
Share on other sites
JackNader

JackNader

Posted
Posted (edited)
Your log is hilarious. It is absolutely baffling to me that the most you've been hit is 5900 smash. Your being hit 10 - 30% less than a typical sage is hit across ALL the abbilities. The only thing I can discern from these numbers is that the people your playing are massive scrubs who do not know how to gear or your rolling with guards and taunt spam galore. Either way, it is NOT a realistic sample rate at all. Edited by JackNader
Link to comment
Share on other sites
ArchangelLBC

ArchangelLBC

Posted
Posted
Your log is hilarious. It is absolutely baffling to me that the most you've been hit is 5900 smash. Your being hit 10 - 30% less than a typical sage is hit across ALL the abbilities. The only thing I can discern from these numbers is that the people your playing are massive scrubs who do not know how to gear or your rolling with guards and taunt spam galore.

 

If its 30% across the board, then taunt spam and guards doesn't seem outside the realm of possibility to me. Especially since as far as I know SOP is to kill the healer first

Link to comment
Share on other sites
cultivatedmass

cultivatedmass

Posted
Posted (edited)

very weak smash hits. that's about the same on my merc with power barrier up(36% mitigation).

 

either undergeared smashers or they were doing something wrong.

 

heatseakers for only 3800 is also strange. those should be hitting for 4.5-5k as that's what mine does against most targets. the tracers were within standard deviation of geared players though. very strange. i bet he was unleashing heatseeker off cd with no stacks just like that smasher was not building shockwave.

 

this doesn't mean his server is especially bad, just that within those 10 games the same types of people(or the same people) were queueing.

Edited by cultivatedmass
Link to comment
Share on other sites
DaedalusV

DaedalusV

Posted
Posted

Thank you for taking the time and effort to do this OP. It would be a huge deal better if you enlarged the sample size quite a bit. Too many random factors are present in such a small sample size.

 

Tip:

 

Try gathering data for a month in a healer spec. By using a DPS spec you skew numbers of hits on you since you're not a priority target.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...