Lol, your post is wrong on so many levels, I'm not even going to bother pointing out all the errors. Let me just leave you with this little tidbit: there's a difference between proc ratio and the number of times you proc.
Alright, just got done doing some controlled testing parses. For the parsing tests, I compared two Cobalt Leafblades against an RGF. The mob of choice was Shrouded Pounder in SS, Lvl48 heroic. Mob was chosen due to decent amount of HP and the fact it's grey to a Lvl60, which means nearly 100% hit rate. For the purposes of testing, I killed 5 times with each setup. Haste was FBSS in Infuriate Adept3. I understand that 5 samples is not a large enough sampling pool to be conclusive off from, but large enough to be able to get a decent calculation off from. Conclusion of the parses: The Leafblade came out with a 3.5% proc rate, EXACTLY what I predicted. The RGF came out with a 20% proc rate. Fury proc'd close to the my predicted rate, meaning Fury's proc rate probably is indeed using the same calculation as weapon proc rates, or something very similar. Total number of procs Leafs: 14 Total number of procs RGF: 41 Total number of hits Leaf: 404 Total number of hits RGF: 205 Leaf proc rate: 14/404 = 3.5% RGF proc rate: 41/205 = 20% Furious assault hits Leaf: 24 Furious assault hits RGF: 32 Fury proc rate, Leaf: 24/404 = 6% Fury proc rate, RGF: 32/205 = 15.6% DPS was virtually identical and too close to call it one way or the other. So despite some folk's assertions, everything I said was dead on affirmed with parses. The proc rates were right at where I said they would be, and the Leaf's weren't superior to the RGF in DPS. In fact, the two set ups produced nearly identical DPS. Unfortunately these boards don't allow any complex HTML formatting, unfortunately, so here is the data in a CSV format if people want to copy the data and analyze it themselves. You can highlight the data, copy it to your clipboard and then paste it into notepad and save it as a *.csv file. Leaf parses: Attack,Start,End,Duration,Damage,Dmg %,DPS,Hits,Misses,Hit %,Max,Min,Avg You,,,,,,,,,,,, pierce,8:59:47,9:00:42,0:00:55,6547,41.26,119.04,53,0,100,197,59,123.53 Amputate,8:59:47,9:00:40,0:00:53,1722,10.85,32.49,4,0,100,136,68,95.67 Unyielding Battering,8:59:49,9:00:35,0:00:46,990,6.24,21.52,3,0,100,372,287,330 Frenzied Blows,8:59:51,8:59:51,0:00:01,695,4.38,695,3,0,100,286,180,231.67 No Quarter,8:59:53,9:00:21,0:00:28,368,2.32,13.14,2,0,100,257,111,184 Furious Assault,8:59:53,9:00:32,0:00:39,649,4.09,16.64,3,0,100,240,188,216.33 Breach,8:59:56,9:00:38,0:00:42,625,3.94,14.88,3,0,100,302,151,208.33 Counterattack,8:59:58,9:00:37,0:00:39,1624,10.24,41.64,6,0,100,322,218,270.67 Wallop,8:59:58,9:00:41,0:00:43,940,5.92,21.86,4,0,100,268,171,235 Slay,9:00:01,9:00:01,0:00:01,510,3.21,510,1,0,100,510,510,510 Provoking Counterattack,9:00:09,9:00:27,0:00:18,674,4.25,37.44,3,0,100,274,178,224.67 Gleaming Strike,9:00:12,9:00:34,0:00:22,522,3.29,23.73,2,0,100,271,251,261 ,,,,,,,,,,,, ,,,,,,,,,,,, pierce,9:01:08,9:01:55,0:00:47,5852,37.07,124.51,46,0,100,198,56,127.22 Amputate,9:01:08,9:01:55,0:00:47,1587,10.05,33.77,4,0,100,116,57,93.35 Furious Assault,9:01:08,9:01:48,0:00:40,1481,9.38,37.02,6,0,100,287,224,246.83 Unyielding Battering,9:01:10,9:01:55,0:00:45,971,6.15,21.58,3,0,100,356,262,323.67 No Quarter,9:01:13,9:01:42,0:00:29,558,3.53,19.24,2,0,100,284,274,279 Frenzied Blows,9:01:15,9:01:15,0:00:01,679,4.3,679,3,0,100,246,187,226.33 Counterattack,9:01:15,9:01:46,0:00:31,1556,9.86,50.19,6,0,100,315,215,259.33 Breach,9:01:17,9:01:39,0:00:22,591,3.74,26.86,2,0,100,305,286,295.5 Wallop,9:01:20,9:01:44,0:00:24,651,4.12,27.13,3,0,100,244,174,217 Slay,9:01:22,9:01:22,0:00:01,775,4.91,775,1,0,100,775,775,775 Gleaming Strike,9:01:28,9:01:55,0:00:27,620,3.93,22.96,2,0,100,350,270,310 Provoking Counterattack,9:01:30,9:01:36,0:00:06,465,2.95,77.5,2,0,100,268,197,232.5 ,,,,,,,,,,,, pierce,9:02:45,9:03:38,0:00:53,6588,41.59,124.3,51,0,100,203,55,129.18 Amputate,9:02:44,9:03:38,0:00:54,1789,11.29,33.13,4,0,100,138,96,99.39 Furious Assault,9:02:45,9:03:32,0:00:47,782,4.94,16.64,3,0,100,296,194,260.67 Unyielding Battering,9:02:47,9:03:37,0:00:50,1014,6.4,20.28,3,0,100,411,275,338 Gleaming Strike,9:02:48,9:03:38,0:00:50,458,2.89,9.16,2,0,100,259,199,229 Frenzied Blows,9:02:50,9:02:50,0:00:01,788,4.97,788,3,0,100,329,190,262.67 Provoking Counterattack,9:02:52,9:03:12,0:00:20,454,2.87,22.7,2,0,100,258,196,227 Counterattack,9:02:52,9:03:38,0:00:46,1446,9.13,31.43,6,0,100,261,203,241 No Quarter,9:02:53,9:03:21,0:00:28,459,2.9,16.39,2,0,100,268,191,229.5 Breach,9:02:56,9:03:16,0:00:20,544,3.43,27.2,2,0,100,361,183,272 Wallop,9:02:58,9:03:25,0:00:27,717,4.53,26.56,3,0,100,284,149,239 Slay,9:03:01,9:03:01,0:00:01,801,5.06,801,1,0,100,801,801,801 ,,,,,,,,,,,, pierce,9:04:56,9:05:48,0:00:52,7083,44.76,136.21,52,0,100,192,61,136.21 Amputate,9:04:55,9:05:46,0:00:51,1747,11.04,34.25,4,0,100,127,67,97.06 Unyielding Battering,9:04:57,9:05:46,0:00:49,988,6.24,20.16,3,0,100,366,282,329.33 Furious Assault,9:04:57,9:05:07,0:00:10,517,3.27,51.7,2,0,100,307,210,258.5 Frenzied Blows,9:04:59,9:04:59,0:00:01,755,4.77,755,3,0,100,331,209,251.67 Provoking Counterattack,9:05:01,9:05:01,0:00:01,209,1.32,209,1,0,100,209,209,209 Counterattack,9:05:01,9:05:33,0:00:32,835,5.28,26.09,3,0,100,328,228,278.33 No Quarter,9:05:02,9:05:31,0:00:29,332,2.1,11.45,2,0,100,191,141,166 Gleaming Strike,9:05:03,9:05:36,0:00:33,1553,9.81,47.06,6,0,100,303,229,258.83 Breach,9:05:04,9:05:39,0:00:35,664,4.2,18.97,3,0,100,274,184,221.33 Wallop,9:05:07,9:05:48,0:00:41,814,5.14,19.85,4,0,100,280,102,203.5 Slay,9:05:09,9:05:09,0:00:01,328,2.07,328,1,0,100,328,328,328 ,,,,,,,,,,,, pierce,9:06:18,9:07:06,0:00:48,6564,41.53,136.75,54,0,100,199,69,121.56 Amputate,9:06:17,9:07:05,0:00:48,1421,8.99,29.6,4,0,100,96,79,94.73 Gleaming Strike,9:06:18,9:06:50,0:00:32,533,3.37,16.66,2,0,100,331,202,266.5 Unyielding Battering,9:06:19,9:06:47,0:00:28,699,4.42,24.96,2,0,100,405,294,349.5 Frenzied Blows,9:06:22,9:06:22,0:00:01,849,5.37,849,3,0,100,450,152,283 Counterattack,9:06:23,9:07:07,0:00:44,859,5.44,19.52,3,0,100,296,279,286.33 Breach,9:06:25,9:06:54,0:00:29,767,4.85,26.45,3,0,100,315,186,255.67 Furious Assault,9:06:26,9:07:01,0:00:35,2434,15.4,69.54,10,0,100,298,199,243.4 Wallop,9:06:28,9:06:57,0:00:29,766,4.85,26.41,3,0,100,278,233,255.33 No Quarter,9:06:30,9:06:30,0:00:01,111,0.7,111,1,0,100,111,111,111 Slay,9:06:33,9:06:33,0:00:01,378,2.39,378,1,0,100,378,378,378 Provoking Counterattack,9:06:43,9:07:07,0:00:24,423,2.68,17.63,2,0,100,213,210,211.5 ,,,,,,,,,,,, RGF: Attack,Start,End,Duration,Damage,Dmg %,DPS,Hits,Misses,Hit %,Max,Min,Avg You,,,,,,,,,,,, crush,5:50:48,5:51:40,0:00:52,5625,34.86,108.17,18,0,100,477,104,312.5 Amputate,5:50:47,5:51:36,0:00:49,1640,10.16,33.47,4,0,100,100,83,96.47 Unyielding Battering,5:50:50,5:51:35,0:00:45,962,5.96,21.38,3,0,100,401,250,320.67 Furious Assault,5:50:50,5:51:38,0:00:48,1310,8.12,27.29,5,0,100,309,244,262 Ancient Flame,5:50:52,5:51:35,0:00:43,1719,10.65,39.98,9,0,100,244,153,191 Counterattack,5:50:52,5:51:38,0:00:46,1387,8.6,30.15,5,0,100,320,211,277.4 Frenzied Blows,5:50:52,5:50:52,0:00:01,769,4.77,769,3,0,100,312,219,256.33 Wallop,5:50:55,5:51:37,0:00:42,721,4.47,17.17,4,0,100,220,151,180.25 No Quarter,5:50:57,5:51:22,0:00:25,468,2.9,18.72,2,0,100,242,226,234 Breach,5:50:59,5:51:30,0:00:31,732,4.54,23.61,3,0,100,333,171,244 Slay,5:51:01,5:51:01,0:00:01,801,4.96,801,1,0,100,801,801,801 ,,,,,,,,,,,, crush,5:52:11,5:53:02,0:00:51,6568,41.2,128.78,19,0,100,535,83,345.68 Amputate,5:52:10,5:52:59,0:00:49,1667,10.46,34.02,4,0,100,126,89,98.06 Ancient Flame,5:52:10,5:52:55,0:00:45,1302,8.17,28.93,7,0,100,230,154,186 Unyielding Battering,5:52:12,5:53:01,0:00:49,1039,6.52,21.2,3,0,100,364,336,346.33 No Quarter,5:52:14,5:52:43,0:00:29,456,2.86,15.72,2,0,100,259,197,228 Furious Assault,5:52:14,5:52:59,0:00:45,1860,11.67,41.33,8,0,100,271,189,232.5 Frenzied Blows,5:52:16,5:52:16,0:00:01,645,4.05,645,3,0,100,223,209,215 Wallop,5:52:19,5:52:57,0:00:38,923,5.79,24.29,4,0,100,272,155,230.75 Breach,5:52:21,5:52:48,0:00:27,795,4.99,29.44,3,0,100,355,174,265 Slay,5:52:24,5:52:24,0:00:01,367,2.3,367,1,0,100,367,367,367 Counterattack,5:52:57,5:52:57,0:00:01,320,2.01,320,1,0,100,320,320,320 ,,,,,,,,,,,, crush,5:53:30,5:54:17,0:00:47,6193,39.32,131.77,16,0,100,519,282,387.06 Amputate,5:53:29,5:54:17,0:00:48,1584,10.06,33,4,0,100,97,57,93.18 Ancient Flame,5:53:30,5:54:09,0:00:39,1858,11.8,47.64,9,0,100,237,152,206.44 Unyielding Battering,5:53:31,5:53:55,0:00:24,546,3.47,22.75,2,0,100,288,258,273 Frenzied Blows,5:53:33,5:53:33,0:00:01,856,5.43,856,3,0,100,450,137,285.33 No Quarter,5:53:35,5:54:00,0:00:25,400,2.54,16,2,0,100,288,112,200 Furious Assault,5:53:37,5:54:04,0:00:27,1524,9.68,56.44,6,0,100,283,217,254 Breach,5:53:38,5:54:16,0:00:38,785,4.98,20.66,4,0,100,243,152,196.25 Wallop,5:53:40,5:54:09,0:00:29,669,4.25,23.07,3,0,100,264,162,223 Slay,5:53:43,5:53:43,0:00:01,368,2.34,368,1,0,100,368,368,368 Provoking Counterattack,5:53:59,5:54:06,0:00:07,429,2.72,61.29,2,0,100,248,181,214.5 Counterattack,5:54:06,5:54:13,0:00:07,539,3.42,77,2,0,100,293,246,269.5 ,,,,,,,,,,,, crush,5:57:02,5:57:50,0:00:48,6025,38.18,125.52,19,0,100,476,57,317.11 Amputate,5:57:01,5:57:47,0:00:46,1448,9.18,31.48,4,0,100,101,96,96.53 Furious Assault,5:57:01,5:57:50,0:00:49,2417,15.32,49.33,10,0,100,304,207,241.7 Unyielding Battering,5:57:03,5:57:29,0:00:26,556,3.52,21.38,2,0,100,299,257,278 Frenzied Blows,5:57:05,5:57:05,0:00:01,888,5.63,888,3,0,100,449,156,296 Ancient Flame,5:57:05,5:57:48,0:00:43,1624,10.29,37.77,8,0,100,238,156,203 Slay,5:57:07,5:57:07,0:00:01,281,1.78,281,1,0,100,281,281,281 Breach,5:57:10,5:57:48,0:00:38,1090,6.91,28.68,4,0,100,354,215,272.5 Wallop,5:57:12,5:57:50,0:00:38,699,4.43,18.39,4,0,100,218,103,174.75 No Quarter,5:57:15,5:57:45,0:00:30,459,2.91,15.3,2,0,100,252,207,229.5 Counterattack,5:57:16,5:57:16,0:00:01,293,1.86,293,1,0,100,293,293,293 ,,,,,,,,,,,, crush,6:00:47,6:01:40,0:00:53,6354,39.97,119.89,20,0,100,479,94,317.7 Amputate,6:00:46,6:01:38,0:00:52,1515,9.53,29.13,4,0,100,96,51,89.12 Counterattack,6:00:48,6:01:36,0:00:48,1066,6.71,22.21,4,0,100,294,249,266.5 Ancient Flame,6:00:48,6:01:34,0:00:46,1676,10.54,36.43,8,0,100,241,168,209.5 Unyielding Battering,6:00:48,6:01:39,0:00:51,1005,6.32,19.71,3,0,100,397,295,335 No Quarter,6:00:50,6:01:16,0:00:26,478,3.01,18.38,2,0,100,275,203,239 Frenzied Blows,6:00:52,6:00:52,0:00:01,1199,7.54,1199,3,0,100,500,315,399.67 Breach,6:00:55,6:01:36,0:00:41,846,5.32,20.63,4,0,100,268,185,211.5 Wallop,6:00:58,6:01:30,0:00:32,489,3.08,15.28,3,0,100,213,126,163 Slay,6:01:01,6:01:01,0:00:01,555,3.49,555,1,0,100,555,555,555 Furious Assault,6:01:01,6:01:14,0:00:13,713,4.49,54.85,3,0,100,279,193,237.67 Message Edited by Tuddar on 12-17-2005 09:17 PM
Where you Dual Weilding? Ive no idea how you got those numbers Tuddar but i broke out the parser for the first time in a month or so and decided to show you that you are completely wrong, not sure if its the program your using or what, but reguardless your numbers are seriously out of whack. First test i did was 5 mobs just like you with the use of CA's : 2nd test i did was with no CA's what so ever and the result was : Now ive no clue how exactally you produced your numbers, but mobs i used for this example where all ^^^ con mobs and had around 15 - 16k HP each. As you can see im not really sure how or what you did to get your numbers, but i can get it close to 9 - 10% proc rate just like Unbridled Fury states it is with a 10% proc rate. I cant seem to find my RGF, ive no clue whats going on there currently waiting on a petition about it but i may just go get a guild group together and kill eggnog for one and do the same tests with a RGF. One thing i think you are misunderstanding with that " old " calculation is that when they upgraded Dual Weild proc ratios they would of had to come up with a " new " formula making the " old " one obselete or there would of been no upgrade to begin with. Im not a mathimatition and i have no idea how one would go about working out the new formula but maybe some of the smarter Berserkers out there could help here, Pin, Sokolov? EDIT - Sorry about the size of the pics, ive got no where to upload them and Photobucket.com was my only choice, but here is a more basic view per fight that you can link to the pics. 5 mobs with CA's : 64 swings 6 Furious Assaults 4 Gleaming Strikes 66 swings 6 Furious Assaults 3 Gleaming Strikes 71 swings 9 Furious Assaults 2 Gleaming Strikes 59 swings 7 Furious Assaults 5 Gleaming Strikes 77 swings 1 Furious Assault 2 Gleaming Strikes 5 mobs without CA's : 109 swings 7 Furious Assaults 4 Gleaming Strikes 208 swings 17 Furious Assaults 8 Gleaming Strikes 95 swings 10 Furious Assaults 5 Gleaming Strikes 91 swings 13 Furious Assaults 4 Gleaming Strikes 99 swings 11 Furious Assaults 3 Gleaming Strikes Message Edited by -Aonein- on 12-18-2005 06:19 PM
I told you exactly where I ran the tests at and what the mob was that was used for testing. Exactly what is confusing about that? Lvl48 Shrouded Pounders, they are ^^^ Heroic mobs. Exactly the kind of mob you want to parse on. You can find them right by the desert madmen's shrine. Second, what mobs are YOU killing. You didn't specify the name of the mob or mobs. From my data you can see exactly what CA's were used and all the auto-attack damage. You can see the hits and misses for each CA. You can verify my numbers from the data I posted. You posted no raw data. My numbers were output by statalyzer. I can see you are using CombatStats. The problem is, CombatStats doesn't provide much in the way of statistics. Not only that, but CombatStats isn't showing you what you think it is. CombatStats doesn't show you hits or misses, it just shows you how often something was used. So hits and misses are all lumped together by CombatStats. However, misses don't count for the purposes of whether a weapon procs or not. In short, CombatStats is great for spot analysis of your DPS, but not so great for trying to break things down. It simply doesn't have anywhere near the analytical breakdown that statalyzer has. If you are serious about breaking down the numbers, CombatStats is not the tool to do so. Third, you posted numbers that agree with me!! Do the math. Let's assume that you connected 100% of the time, if you were fighting grey heroic mobs like I did in my test. With CA's your recorded number of swings are 64+66+71+59+77 = 337 swings. Of which, you had 16 GS procs. 16/337 = 4.74%. Without CA's, your recorded number of swings are 109+208+95+91+99 = 602 swings. Of which, you had 24 GS procs. 24/602 = 3.9% As far as the number of Fury procs you experienced, I'll be running more parses tomorrow, so I'll see if this was just a run of bad luck on my part, or a run of good luck on yours. I'll be increasing my sample size to 50 for each weapon set, so the numbers should be a little less prone to temporary streaks. -Aonein- wrote: "One thing i think you are misunderstanding with that " old " calculation is that when they upgraded Dual Weild proc ratios they would of had to come up with a " new " formula making the " old " one obselete or there would of been no upgrade to begin with." I'm not misunderstanding anything. What I am understanding is that the proc rate for dual wield doesn't even come close to a high delay 2 hander. Perhaps what you are misunderstanding is that the old formula caused an extra penalty towards dual wields if you used CA's, and they probably just made a minor adjustment to help with that fact. But it's pretty clear that there was no huge jump in the proc ratio of dual wields, and even your own numbers prove that. As far as the RGF thing, I knew you didn't have one to begin with, because anyone who does or has had one can tell you even without parsing that the proc on the RGF goes off an insane amount. Your claims of only a 1-2% difference immediately told me that you had no idea how often it procs, and you were just making numbers up. Hell, your own parses pretty much agree with me when it comes to weapon proc rate. When you said that there was only a 1-2% difference in procs between the leaf blades and an RGF, I'm sure everyone who owns both sets immediately knew that you were, in fact, making stuff up. And your own parses prove it. P.S. As far as figuring out the new formula, until a Dev comes straight out and tells you what the calculation is, you'll have to hypothesize possible algorithms, then devise different sets of tests to try to isolate each portion of the algorithm, and then see if your algorithm agrees with them statistically over all sets. Which is a lot of parsing to do. To compound this problem, there aren't parsing mobs like there were in EQ, mobs that had millions of HP and didn't fight back, where you could do extensive parses on for long periods of time and get data sets large enough to be statistically valid. Getting those data sets in EQ2 will be very difficult. Message Edited by Tuddar on 12-18-2005 02:16 AM
HAHAHA, Tuddar Combatstats does everything Statalyzer does, i can give you a full rpint out in CSV or HTML format and i can give you as many screen shots of hits, miss's, blocks, parries, ripostes, hell i can give you the mobs hits miss etc etc, but truth is how many screen shots do you want and i dont have a unlimited amount of web space to upload stuff. Mobs im testing are the lvl 48 spectres and yes im getting 100% hit ratio with 0 misses. I got more tests coming for you to endulge yourself with with a range of tests being done with 1.2, 1.5 and im just going to buy a 3.8 delay wep and test that for [expletive haxx0red by Raijinn]s and giggles.
Also while i think of it Tuddar, all the data your CSV formatt provides, my screen shots provide the same thing and taking into account that every hit is a 100% hit with no misses etc, one can just average that out, yours just shows that you have succesfully hit every hit 100%, no difference, just yours shows the amount you hit for on the accual hit itself, this in no way changes the amount of procs you do or makes my numbers any different from yours seeing as mine is also 100% hit ratio also.
Lol, dude, you really have no clue. Export out your data in CSV format in CombatStats. You know what it looks like? It looks like this: pkey,owner,battle,name,lowdamage,avgdamage,highdamage,used,total,lastused 1001,1005,1001,"assault",34,69,109,6,418,11/06/2005 18:11:24 1002,1001,1001,"counterattack",199,293,372,340,99649,12/01/2005 18:06:36 1003,1005,1001,"crush",3,50,142,27,1368,11/06/2005 18:11:34 You see misses anywhere in there? No. Damage % of fight? No. Hit %? No. Does CombatStats give total figures for the entire log? No. Can I determine with CombatStats what my hit % was on my CA's from 1 Dec-15 Dec? No. I could go on and on about how much more Statanalyzer does then CombatStats, but it's not worth wasting my time, because you don't even know what CombatStats does. Go ahead, post your screenshots showing misses from CombatStats. Try making it large enough so people can actually see something. This is going to be good. Or better yet, export out your data showing it. Do you even bother to double-check what you post? 3 seconds of work exporting out your data in CombatStats would have shown you that what you have posted about CombatStats is, in fact, not true. Message Edited by Tuddar on 12-18-2005 09:25 AM
I've PM'd you an address, username, and password you can use to upload images to. Feel free to upload your images there. You can then link your images here with an address like this: http://216.119.80.244/Aonein/5mobswithCAs.jpg Make sure to save your screenshots large enough so they are readable. You've got tons of file space, so make them as large as you like.
Tell you what i will do Tuddar, send me another PM with the site where i can download statalyzer and ill do my tests with your program seeing as reguardless what or how i do anything with combat stats you will find something technical about it to not be true when all i want it to do is show you a 100% true value of what the proc ratio really is with a 100% hit ratio and i did just that, have you looked into why your proc ratio was so low on your dual weild test? I dont even believe you tested it and just did a random number test using your own numbers so that it fell your way. When you have a 100% succes rate of all hits connecting it doesnt matter what program you use as long as it tells you how many swings and how many procs, providing you have connected 100%.
Exactly what are you not comprehending? YOUR OWN PARSES CAME UP WITH NUMBERS VIRTUALLY IDENTICAL TO MINE. Jesus, how much more clear do you have to get? You were the one saying that CombatStats does everything Statalyzer does, and now your asking me for a link to the download? So exactly how did you make the claim, and I quote you: "HAHAHA, Tuddar Combatstats does everything Statalyzer does, i can give you a full rpint out in CSV or HTML format and i can give you as many screen shots of hits, miss's, blocks, parries, ripostes, hell i can give you the mobs hits miss etc etc, but truth is how many screen shots do you want and i dont have a unlimited amount of web space to upload stuff." This is like the third time you've claimed something and didn't know what the hell your talking about. Your just making [expletive haxx0red by Raijinn] up as you go along. You say CombatStats does something, and then I point out that it does no such thing. You say it does everything that Statalyzer does, yet you don't even have Statalyzer to know the difference. After all this, you have the nuts to accuse *me* of making stuff up. Dude, you are one class act. At this point I'm just humoring you, because your already beyond credibility. You can get statalyzer at http://www.thescoutssanctuary.com/parser/statalyzerbeta062.zip Last, but not least, and as promised, here are the numbers from 50 kills with each weapon set. Again, Lvl48 ^^^ Shrouded Pounders in SS: LEAFS: Proc ratio: 3.4594096% Fury ratio: 7.1494465% RGF: Proc ratio: 16.183% Fury ratio: 11.7106% Notice that the leaf's proc ratio on both GS and Fury is exactly what I had predicted, and very closely matches my first set of parses. Interestingly, GS has a 5% proc rate and Fury has a stated 10%. Now notice that in the results above, GS procs exactly half as much as Fury. In other words, the parsed ratios EXACTLY match what you would predict. Fury proc'd twice as much as GS, which makes sense since Fury has a base 10% and GS has a base 5%. This also lends further credence to the theory that Fury is using the same proc formula as weapon procs do. The procs on the RGF are very close to the predicted rate. Fury is .5% lower in this parse then expected, and Ancient Flame about 1% higher. Not a huge difference between parse and prediction. You can download the parses for these figures at http://216.119.80.244/parses/parses.zip. These are actually EQ2 log files, not extracts of any parsing program. So you can see exactly what happened, and you can verify my results with the logs directly. I supposed next you'll accuse me of randomly generating the 14,500 lines of logs that it took to generate these figures. Message Edited by Tuddar on 12-18-2005 06:30 PM
Funny thing is Tuddar Combatstats is a harder program to configure but it can do everything that Statalyzer does, the CSV and XML / HTML formats just look different. Ill post screen shots of both later to explain it for you, and by the way, if you read my first post correctly, the very first one i made here, i pointed out what you have been trying to argue all along.
Download Statalyzer, and then you can tell me CombatStats does everything it does. With personal working knowledge of both programs, I can tell you factually that it can not. Like I said, CombatStats is good enough for seeing DPS info, but that's about it. And that's because that is all it was designed for.
Actually, in your first post you said: "Now if your like me and use a set of Leafblades that have a 2.1 delay attack speed, your going to be maximizing your proc potential while also maximizing your auto attack damage from not missing many combat rounds due to CA usage. The 2.1 attack speed on a set of dual weilds is far superiour to a RGF, reason for this is because you have the calculation of 2.1 delay per weapon, where with the RGF you have one weapon at 3.8." To which I pointed out the flaw in that logic, because for high delay two handers your going to miss less auto-attack damage, your going to proc more then a dual wield combo because of the way procs work in EQ2, and with comparable weapon sets the high delay two hander will flat out own dual wield as far as DPS. That's why a T5 Fabled two hander is doing equal to slightly better DPS then a pair of T6 Legendary. The leafblades will put out more DPS if your not using CA's, such as when your out of power. Again, like I said, there's probably a good reason your not seeing high delay two handers out of DoF. They just have too much of an advantage in everyday gameplay. Message Edited by Tuddar on 12-19-2005 11:20 AM
Accualy Tuddar if you read that post again, i was reguarding to how i play as in how i go about the use of my CA's, for my gameplay style i get the best out of Leafblades because i like to Dual weild meaning like we both agree on, the slower the weapon the less auto attack damage you miss due to long casting timers on certain CA's. Now seeing as the Leafblades are even slower then some 2 handers out there, it makes for a perfect medium when it comes to missing auto attack damage with heavy CA usage, if i was to parse myself using Slashing dual weilds which are for the most part around 1.2 second delay i would notice a huge decrease in auto attack damage, while the swings would be more the damage would be less. I think majority of us already knew that there was going to be no more 3.8 second delay weapons before DoF was released, who knows, they might start making them again in a expasion or two, but one has to ask themselves, what will the Berserker class be like in 1 or 2 expasions? Will they benefit from a extremely slow 2 hander like they do now?
I don't need to re-read your post again. The intent of your post was to say that the Leafs were superior to an RGF. I've shown that's not the case and explained why it's not the case. Last time I'm posting on this thread, as I've made my point and not going to bother arguing with you saying one thing and then later making it out like you meant something else.
No Tuddar your taking what i said out of context and yeah maybe i did exagerate about the proc ratios being 1-2 % difference from a dual weild set of leafblades but i exagerated no more then you did with your parses when you then followed it up with you will run more tests that aggred with mine.......:smileyindifferent: If you read a post more carefully next t ime instead of jumping the gun and i cant remember how many times in how many posts that Berserkers have argued about in over how much difference there is in a heavy CA user and a light CA user and what type of weapon set up they use plays a big part in DPS. Got those screen shots coming too for ya.
Ok ill start off with saying i couldnt use the site you gave me, wouldnt load up for some reason on my comp so ill stick with photobucket, you can easily download the pics to your own comp if you wish. You asked me if Combatstats can determine what my hit % was on such and such a date etc etc, sure it can, it has a archive folder which you can quite easily flick back through using the date section on the program. First is showing you how Misses, parries, blocks etc are displayed ( keep in mind that this parse is from before the changes to dual weild so take no note of the proc ratios ). Notice i have it set to Detailed Player Statistics, not a summary. As you can quite clearly see it shows everything Statalyzer does when it comes to miss percent ratios and what not. Second picture shows you how a compliation of CA's are complied during a full session of using Combatstats : Now the one thing i will admit that i dont like about Combatstats is notice the total hits i did with i think it is piercing, once the number generated hits the thousands, you lose track of what you have really done in the program itself, i havent yet used Statalyzer to produce a number that big as yet, so i dont know if it does the same thing. Pics from here on in are recent. But upto this point both programs can supplie and show the exact same data. Next lot of pics : Here we have two exact same parsed instances that i ran at the exact same time, both displaying the exact same thing, a complilation of the CA's and auto attack damage from the fight. Notice the miss, block, parry etc etc boxs next to the CA's i used plus the 100% hit ratio i maintained across the fight on both programs? This picture is a example of where IF you dont purge the database how you can change the date to redisplay history form days gone by of what your old data was say 2 weeks ago etc etc, or months ago if you wish, but you must not purge the database or obviously you lose all that data, unless you back it up in CSV, XML format which then you can do exactally what you can do with Statalyzer and copy the log file back into the program and see the stats all over again, nothing different here. Now as you can see here that this is probally one feature that combat stats doesnt have and that it doesnt acually tell you what the mob is trying to hit you with if he misses, it just gets compiled into the hit / miss ratio of the mob itself, but none the less, it doesnt really matter in the end because it all registers the same numbers just statalzyer gets a little credit here for being a little more neat. As you can see both programs peform the same dutie and purpose, the CSV, XML or HTML reports are more then likely different and id wager you cant use the CSV, XML / HTML files from Combatstats in Statalyzer or visa versa because the programs read them differently or are produced differently depending on how the program is built, you know its a binary thing, coded that way. I had more pics, like 14 to be honest, but they were just pics i took of Statalyzer and how the front page of Statalyzer was a fight summary and that i didnt like the way you cant reset that without turning off your logfile and ethier deleting that log file OR removing it from the log folder so when you start a new /log it starts fresh instead of picking up where you did /log off and recreating all the statistics all over again, where Combatstats is good for that because you can reset it after each and every fight so you can get a read out of a per fight basis and still have a total compiled session all up. EDIT - Im just wondering if you have raw logfile that you have taken from the game itself, the text version of the logfile, can you upload it into Combatstats or Statlyzer to open that logfile and produce the stats it would generate while you had the program running while parsing? Message Edited by -Aonein- on 12-20-2005 12:16 PM
Maybe you exaggerated? Dude, you outrighted lied. Then you made posts stating things that were factually erroneous, because you didn't have a clue what you were talking about. Here's some juicy excerpts: "Dont forget your Dual Weilding as well, so the proc ratio isnt 3.5% on dual weild setup leafblades and nor does it work out like that in the game ethier, that calculation doesnt or i should say even work correctly and im 100% sure that its not even how they determine the proc rate now , because there is no way my Leafblades are working out to be a 3.5% chance to proc." Extensive parses showed the leafs proc'ing at 3.5% ratio, exactly as predicted. "I've ran the tests using a RGF and the difference is minimal at best using a high delay dual weild set up, the difference is 1 - 2%, which is why that calculation is nothing now, its old and i doubt they even use it themselves anymore." Outright lied since you don't have an RGF, anyone who has ever owned one would know the difference is huge, and the numbers 1-2% difference came straight out of your azz. " not sure if its the program your using or what, but reguardless your numbers are seriously out of whack." Yeah, so out of whack that two seperate parsing sessions produced almost exactly the same results. Again, opened your mouth without actually knowing what you were talking about. "have you looked into why your proc ratio was so low on your dual weild test? I dont even believe you tested it and just did a random number test using your own numbers so that it fell your way." Pathetic. You accused me of making numbers up, because there can be no other explanation since my numbers didn't match what you thought they should be. "HAHAHA, Tuddar Combatstats does everything Statalyzer does, i can give you a full rpint out in CSV or HTML format and i can give you as many screen shots of hits, miss's, blocks, parries, ripostes, hell i can give you the mobs hits miss etc etc, but truth is how many screen shots do you want and i dont have a unlimited amount of web space to upload stuff." You post this, and then admit you don't have Statalyzer. Again, talking straight out your azz, because you really didn't know. Don't piss on my leg, and then tell me it's raining. My second set of parses agreed with MY first set of parses. There was nothing to exaggerate, because I posted numbers directly from parses in both posts. So stop trying to make out like I was making things up, because you and everyone else that so desires can look at the data and see that everything came straight out of logs. You can download the logs directly and analyze them yourself. Second, you might as well stop posting screenshots, because no one can see what your talking about because they are too small. Third, the username/password I gave you allows you to FTP. If you don't know how to use FTP, then I can't help you. Lastly, there was nothing taken "out of context". Here's what you said (can't believe I'm having to post this again): "The 2.1 attack speed on a set of dual weilds is far superiour to a RGF, reason for this is because you have the calculation of 2.1 delay per weapon, where with the RGF you have one weapon at 3.8." Which is complete and utter nonsense. I explained why it's nonsense, and provided the parses to show it's nonsense.
LOL nice try Tuddar, i take it you havent downloaded those pics at all to look at them have you? I used a program just like Statalyzer for EQ1, it was identical, did the exact same thing, except it also gave you a pie graph to go with it. I used Statalyzer a long time ago and didnt like it because of reasons i mentioned. Like i stated Tuddar, Combatstats does exactally what Statalyzer does except for one thing which i pointed out. Now as to your parsing Tuddar, your numbers where never correct to begin with or predicted, your numbers changed all the time, and they dont match mine which i have posted screenshots for, you posted false information in your first post, when i called you out about it you tryed to say i had a string of good luck ( total bs ). Then when you did the tests yourself again, they came closer to my results BUT you need to run the test over 50 mobs to screw the variable down to keep it in your predicted range when we all know that running the test over a longer period of time, the percentage values drop due to being spread out over a larger number, so you needed to do this to keep your preditcion in tact, and you most likely already knew that, just look at the parse i posted that has something like over 200,000 damage done with just auto attack, look at the percentage values over that parse session, it clearly shows you how the varible changes due to the parse running over a longer period of time and i can bet you any money i could screw these tests right down to the floor to a 1% proc ratio because of the amount of subjects i run it over. Even less. Lets look here, you posted your numbers over 5 different mobs and this was your total value you came up with while using CA's : Tuddar wrote : Total number of procs Leafs: 14 Total number of procs RGF: 41 Total number of hits Leaf: 404 Total number of hits RGF: 205 Leaf proc rate: 14/404 = 3.5% RGF proc rate: 41/205 = 20% Furious assault hits Leaf: 24 Furious assault hits RGF: 32 Fury proc rate, Leaf: 24/404 = 6% Fury proc rate, RGF: 32/205 = 15.6% Now if you used your brain and copied the pics i posted to your comp and used Windows Picture and Fax Viewer to blow then up, you will clearly see that my pics prove that your numbers are totally ethier randomized OR just theroized or probally both. Pretty easy here ill post the numbers from my screen shots : 5 mobs with CA's, same amount of mobs you killed, same level, same con with both getting 100% hit ratio : 260 Piercing swings 28 Furious Assault procs 14 Gleaming Strikes 5 mobs without CA's, same amount of mobs you killed, same level, same con with both getting 100% hit ratio : 493 Piercing swings 51 Furious Assault procs 20 Gleaming Strikes Screenshots to go with those numbers that show both my CA usage and auto attack damage and like i stated 100% hit ratio, which i didnt show because you couldnt produce these numbers unless you had a 100% hit ratio to begin with. Point being how you got your numbers is total BS and randomized theroy using math to try and back your claim, then when i posted these numbers backed by screen shots, you say i was lucky and say your going to run the tests again over a larger scale which anyone with a brain KNOWS that the more mobs you engauge the smaller the percentage will be so you then HAD to use a scale of 50 mobs to bring your percentage down to your predicted value where if you did the same test again on a scale of 5 mobs ( like we were from the beginning ), you would get the exact same numbers i would............:smileyindifferent: EDIT - To support this you even helped me yourself with this theroy : Tuudar wrote : You did the test over a 50 mob subject value : LEAFS: Proc ratio: 3.4594096% Fury ratio: 7.1494465% RGF: Proc ratio: 16.183% Fury ratio: 11.7106% Compare those numbers with the numbers from the 5 mob test. Your RGF values dropped like i stated and funny thing is, youtr Leaf values stayed the same for weapon proc ( Gleaming Strike ) but acually increased with Fury procs......:smileyindifferent: Do you see the point im trying to make? It took me almost half the amount of swings to produce a little more procs then you did : 260 swings 14 Gleaming Strikes 28 Furious Assaults Your numbers using the same CA's over the same amount of mobs : 404 swings 14 gleaming strikes 24 Furious Assaults Now it took me to use NO CA's what so ever to produce a little more then what it took you to produce over 5 mobs using CA's..........: 493 swings 51 Furious Assaults 20 Gleaming Strikes As you can clearly see your numbers dont hold water, at all then you tryed to call me out on Combatstats not suppling enough data when i didnt show it to minimize space when posting, which i also then backed up my claims about Combatstats doing the same thing about Statalyzer. Im going to rerun all mys tests using Statalyzer AND Combatstats at the same time and post them both here for you to see Tuddar, no point in posting log files or any of the other BS you do because the log files are saved with in the programs themselves, after all it is how they parse the information to begin with. Then ill again put my numbers up against your 50 mob parse, then we will see if im lucky again. Message Edited by -Aonein- on 12-21-2005 02:38 PM
