For anyone who won't see it, buffs to MCH not incoming

[RiceisNice]

yeah sure every dummy pars is not the average, maybe the drg, mnk etc. parses are aswell cherry picked with a lot crits? just because they are the old jobs no one cares enough :P if you listen he also mentions that he got very bad procs at the start

And he also got some stupidly amazing good procs on wildfire, as well as crits. That's where the number inflation comes from. There's a difference between parsing to find where a class stands, and parsing to see how much you can deal. You're taking the latter and trying to use that to represent what the average machinist should be doing =/

[Edellis]

MCH parses terrible always and forever

Look at this DRG/MNK/WHM/something parse its great

Hey guys here's a pretty good parse for MCH i think

definitely cherrypicked adjust for inflation not practical at all 15 mins or gtfo

Come on guys we need real data not cherrypickings

[SovereignAegis]

Come on guys we need real data not cherrypickings

My real experience leveling my MCH is that my scholar at all points did more damage spamming broil. And a whitemage stone hits WAY harder than scholar broil. (This is not when a MCH fully buffs out, where they do do more damage than healers spamming their basic ability.)

I don't need any fancy parsers to tell me that, and in fact I am against them since the developers stance is against them.


Burst is also lower, because I can spam drain life inbetween broils with DoT effects. WHM and AST can both also maintain DoT output at all times too to increase their damage even further as well. At present healers CAN AND DO out damage MCH. I think Dark Knights do as well, and warriors CERTAINLY do.

[Outfoxed]

SE, are you not reading your own forums? Are you not looking at the HARD FACTS? Do you even play this game?!

So, we're able to parse every other job correctly, but not MCN?

who says we're parsing other jobs correctly? lots of people have been crying about parsers being inaccurate.

they addressed your complaint completely.....

they said that they will look into the discrepancy between player parsers and dev parsers.

and let's be real here..... who do you think is more accurate? a third party app or a first party app with thorough knowledge of the in-game workings?

[Nadirah]

As a side note, Xero explained a longstanding fault with ACT, which is why in EQ2 (the game ACT was originally developed for) the common tactic was to name your pet after yourself, so pet damage was added to your own.

Cannot rename pets here.

[Whiteroom]

As a side note, Xero explained a longstanding fault with ACT, which is why in EQ2 (the game ACT was originally developed for) the common tactic was to name your pet after yourself, so pet damage was added to your own.

Cannot rename pets here.

Was wondering about how well the parsers played with pets.

[pandabearcat]

Parsers do seem to be inaccurate, if that is any consolation for you guys.

1. It seems skill speed/spell speed don't correctly increase dot damage on parsers.
2. A few people in my static run parsers, and the numbers they tell me never match up with each other...on some I am up to 100 dps lower than others.

[Kenji1134]

It does make sense that ACT is having trouble with dots since the SS change.
Parsers see if the dot is active, what effects were active when it was applied, and calculate damage based on the average potency from other known attack values.
But with the SS change, the dot potency is not equal to the attack potency, so unless ACT gains dynamic access to your SS value, it will be inaccurate when parsing dots.

Again I want to bring up the ACT Enmity Addon. If you can simply read the enmity generated on the dummy by abilities without a hate mod, and divide that by the time you spent beating on the dummy, then you have your dps.
It is not the easiest method, but it can be used to obtain accurate data.

[RiceisNice]

Parsers do seem to be inaccurate, if that is any consolation for you guys.

1. It seems skill speed/spell speed don't correctly increase dot damage on parsers.
2. A few people in my static run parsers, and the numbers they tell me never match up with each other...on some I am up to 100 dps lower than others.

1. People have done tests with skill speed on Bard, and I've checked my own numbers on MCH. It has *very* little affect on our only DoT (Lead Shot), nor does it boost turret potency.
2. Ravana can easily be teh cause of that because of unmerged parses. People have different threshold timers where a fight will reset because nothing goes on for X amount of seconds.

And are you really insisting that machinist is the only class that is being parsed wrong and not the other twelve (or the other tweleve is being parsed wrong).

[pandabearcat]

...no? I'm saying that our parsers could be inaccurate and so maybe the devs know something we don't. Yikes.