Mythic Weapon Compiled Information

[Nameless]

Yea, from what I read from Kirschy's small sample, I thought the DA "stack" in a way that haste and haste stack, not haste and delay reduction stack, which would make Conqueror pretty insane in zerg situation (some said possible to hit 85% DA if stack).

So yea, interested to see the bigger test result. I was thinking the same way as Starr as well (big fan of kirschy so I generally believe in her tests even if the samples are small).

[Kirschy]

I started the test off doing it by hand, but I figured KParser couldn't hurt so I loaded it up about ~30 hits in.

Differences:
-By hand I started ~30 hits earlier.
-I didn't count hits while AM3 was not active.
-I didn't count the last hit if it was single. (The last hit could be a DA or a Single so it should remove a proportionate amount of both.)

By hand: 198 DA, 320 Attack Rounds = 61.875%
KParser: 187 DA, 323 Attack Rounds = 59.94%

(It should be noted that KParser marked the end of 11 mobs /w a single hit. And it counted a few hits between AM3 which accounts for the slightly lower DA%.)

DRK/WAR /w Brutal + Askar Body + Pole Strap + Ares Legs:

http://img200.imageshack.us/img200/2091/am3.png

62% leans toward the fact that maybe the inital AM3 DA rate is off. I'll see if I can run another test w/o the extra DA+% before my LS does Ein~

[Masamune]

(198+187)/(320+323)=385/643= 59.87% parsed total DA rate, for a sample of 643 rounds.

DRK/WAR /w Brutal + Askar Body + Pole Strap + Ares Legs (assuming 0 WAR roll) = 21% DA job trait + 45% from Liberator's AM3 during the 79% remaining time DA didnot proc'd = 21% + 45%*79% = 56.55%

If stacked DA+AM3, would give 21%+45%=66%.

Since usually parsed stats tends to start with high rates to decrease as sample size increase => looks like 1st hypothesis is the nearest ?

Edit: Did yu parse the initial DA rate where yu were building 300TP ? (AM3 off)
If yu parse w/o DoubleAttack jobtrait, how will yu validate if DA jobtrait+libeAM3 stacking ?
and last question: i don't understand how KParser got 59.97% : 187/323=57.89% ?

[Kirschy]

It seems you were right Masamune, I went back and tested DRK/DRG with no DA+ and somehow I got a ~52% DA rate. I'm honestly confused at how it differs so much from my previous ~46% DA rate I got originalli. (Did SE ninja change Mythic AM3??). For now I'll just assume my original testing sample was faulty or too small.

By Hand: 180 DA, 347 Attack Rounds = 51.87% DA Rate
By KParser: 51.42%

(Again same differences as before, last round single hits and hits while AM3 were down were not counted.)

~50% DA rate calculated seperately from the +21% DA when I was /WAR /w DA+ would come out to be 61% which is close to what the data came out to be.

http://img32.imageshack.us/img32/882/am32.png

I'm honestly confused at why got 132 DA / 284 Attack Rounds when I tested in April, and now I'm getting 52% =x. LS COR + WAR coming out so I can stack all the DA and see how my rate is. Won't be a large sample size though.

[Masamune]

don't use war roll, nothing better to skew parse results, since its random.

[Kirschy]

I did a small sample of war roll @ 5 /w war in pt. (DRK/WAR /w 11% DA) I just wanted to see if I would hit close to the 100% mark like I felt I did in the past. But it was way off. KParser had it at 66%, but it'd be a little higher since AM3 dropped twice, and I finished off a few mobs /w a single attack.

50% * (21%[/war & DA+] + 18%[Roll]) = ~69% DA Rate

50% + 21% + 18% = ~89% DA Rate

It's clear "Occasionally Attack Twice" of Mythic is calculated seperately from DA. I apologize for my initial testing being inaccurate~

[Yugl]

I'm always right etc

It's clear "Occasionally Attack Twice" of Mythic is calculated seperately from DA.

Best thread ever.

Is it possible that the AMIII percentage declines over time? Or is it a confirmed static percentage?

[Kirschy]

I can post my handwritten data if ppl wanna see it, but it seems uniform distribution from just looking at it.

Starr was right, I did say they were calculated together... I'm the one who is wrong here ; But at least we know for sure now. But *sigh at Mythics looking even worse than before :/.

[Nevex]

It's worse for WAR, NIN/WAR, SAM/WAR, THF and little else. Job combinations that don't posses Double/Triple attack or don't load on DA/TA (excluding Brutal earring since that's a given) gear are barely affected by that.

If I understand correctly with AM3 and Brutal Earring you get an effective 52.5% chance of attacking twice per round? That's better than the previously assumed 5%(earring) + 45%(AM3).

Edit: actually nvm, AM3 is still 45%. Meh, just a 2-3% loss, no big deal.

[Masamune]

Best thread ever.

Is it possible that the AMIII percentage declines over time? Or is it a confirmed static percentage?

Best thread ever indeed i concurr Thank you Starr for this fun ^^
And kudos for Kirchys giving his time for testing and being nice:D

For AM3 value, should be static, its just when yu parsing yu'll notice values often start with erratic and high, then tends to decrease and less and less erratic to finally stabilize as sample size increase. Never seen a parse starting with low values so far :s

[Masamune]

I can post my handwritten data if ppl wanna see it, but it seems uniform distribution from just looking at it.

Starr was right, I did say they were calculated together... I'm the one who is wrong here ; But at least we know for sure now. But *sigh at Mythics looking even worse than before :/.

Starr were saying opposite (DA+AM3 stacking), big difference Kirchy ^^

[Masamune]

Edit: actually nvm, AM3 is still 45%. Meh, just a 2-3% loss, no big deal.

Actually, 2nd parse Kirchy did with 0 DA jobtrait proved (as far as sample size goes) AM3=50%.

45% value is when yu accounting capped accuracy in, ie 50%*95%=47.5% landed DA hits

[PeaceNLove]

Actually, 2nd parse Kirchy did with 0 DA jobtrait proved (as far as sample size goes) AM3=50%.

45% value is when yu accounting capped accuracy in, ie 50%*95%=47.5% landed DA hits

A DA is still a DA regardless of whether it hits or not. It doesn't have to hit for the parse (or human eye) to pick it up.

[Kirschy]

I know /w larger sample size you'll get a more accurate number... It just feels unsettling that I got 46.5% in ~284 Attack Rounds and 52% in 347 attack rounds... 5.5% difference seems too much. As was said, accuracy plays no role in DA determination.

Regardless, it appears 50% is the correct number, and AM3 is calculated seperately from DA+%

I am to blame for the DA + AM3 stacking though :/ I had posted that it appeared to work this way, but I was wrong. I'm just glad we figured out the true mechanics behind it~

[Masamune]

How about Nevex's Tizona AM2 duration ?

[Starr]

Excuse me for agreeing with one of the top FFXI math posters ever, go fap to me being wrong Yugl.

[Nameless]

I can post my handwritten data if ppl wanna see it, but it seems uniform distribution from just looking at it.

Starr was right, I did say they were calculated together... I'm the one who is wrong here ; But at least we know for sure now. But *sigh at Mythics looking even worse than before :/.

May I have your handwritten data mailed to me plz? PMing you my address. Oh sign it for me as well :D

j/k j/k lol

[Valisk]

Originator of RC Zerg - 6/26/07
Finder of 43.3% Cap on Magic Haste

Are you REALLY the originator of RC Zerg and the finder of the 43.3% Magic Haste cap?

[Gergall]

Best thread ever indeed i concurr Thank you Starr for this fun ^^
And kudos for Kirchys giving his time for testing and being nice:D

For AM3 value, should be static, its just when yu parsing yu'll notice values often start with erratic and high, then tends to decrease and less and less erratic to finally stabilize as sample size increase. Never seen a parse starting with low values so far :s

At the beginning of a parse, erratically low data should be just as common a sight as erratically high data.

If it's erratically high at the start each and every single time, as your post suggests, then there is an element of decay.

As I don't have any data, I can only state these obvious facts.

Edit: Actually, the first part of your post that I bolded uses the word "often" but then later you used the absolute term "never" so I'm not sure what you're trying to suggest. If I take it literally, you are saying that sometimes it starts out erratically high, and sometimes it starts out around the stable value, but it never starts out erratically low. That's pretty weird and I have my doubts about the veracity of this.

[Kirschy]

Are you REALLY the originator of RC Zerg and the finder of the 43.3% Magic Haste cap?

Fairly certian he was the first one who saw there was a cap on magic haste (and posted about it). He posted about it on KI and I went ahead to test and confirm he was right. The precise value is 43.75% (7/16).

I think Masamune just misphrased. Whenever you're parsing or testing data it's just erratic in general. High and Low. I don't think he meant to imply a decaying factor.