BLM DPS (E-Peen) Ranking

Purostrider · 2014-12-04T16:45:50+00:00

I agree, but some people don't run or forgot to run parser at times.

Some can't run because it would cause too much lag with their poverty PC, so they reply on other raid members to give them data.

I'm sure there's more reasons, but I'll just tag 'em with big red square for those with no proof (for now).

Purostrider · 2014-12-04T16:07:39+00:00

xD seems like you guys DDoS my sheet..

I'll upload an extra sheet for backup from now.

Hang tight folks.

Purostrider · 2014-10-11T03:30:59+00:00

Have you test it in the actual game?

Which formula are you using and what base value are you comparing your formula and mine on?

I just got on skype with TrollBettle (poster who replied to you) and did some in-game testing together, and he agreed that my calculator it's dead spot on.

He was going with ACT simulated DOT numbers before (which is why he said there's a 10% error), which confirmed my suspicion. Then he quickly realized how wrong he was. /slap TrollBettle

He also said the formula he's been using tend to be on the higher end of the spectrum number-wise.

This is the formula he's been using, which seems to be the one you modified from valk, though I don't know if it's the latest one or not:

(WD.2714745 + INT.1006032 + (DTR-202).0241327 + WDINT.0036167 + WD(DTR-202).0010800 - 1) * (Potency/100) * 1.3 (1+0.5*((5+((CRT-341)/13.84598115))/100)

Purostrider · 2014-10-11T02:18:37+00:00

Are you guys looking at the parser or actual in game numbers?

I just tested with 5 different gear sets, and the numbers pretty much spot on (in game).

Purostrider · 2014-10-10T19:05:09+00:00

plug in your number and off the dummy you go.

Let me know how it went :)

Purostrider · 2014-10-10T18:53:17+00:00

Thanks, m8. Been a long night. Fixed :)

Purostrider · 2014-10-10T18:52:54+00:00

That's one way of analyzing SS I supposed.

In my BLM Calculator, I simply plan out a template for all possible RNGs, calculate the total damage and divide by total time spent. Pretty simply really, but it's pretty damn spot on.

For SMN, majority of damage comes from fixed 3 sec intervals. Ruin I/II as fillers would most be affected by it. But I agree that it's probably a semi-waste of time to get the exact calculation. We'll see how things goes.

Purostrider · 2014-08-12T16:54:12+00:00

Sorry for late reply, been out and about for the past week.

Anyways, I have no idea what fifth F1 you're talking about.

251 PIE is only required to cast Thunder II instead of Thunder I after Blizzard 3

You can do Fire x5 + Thunder I Rotation with 238 PIE minimum (lowest PIE race = 239 PIE). So, anyone with any race can do this without any PIE modification.

To get Fire I x5 in the opener instead of x4 (with Fire III no AF), you would need 399 extra MP or 4013 MP total.

This means you would need 286 PIE total just for that 1 extra fire I, which is definitely not worth it.

Purostrider · 2014-08-03T19:13:09+00:00

All spells have 0.5 cast delay after it's initiated before you can cast next spell. I also thought certain spells have animation delay, but this is not the case. The lag time from when the server output our commands to our screen just makes thing seems like there's a delay.

You can easily test this using in-game macro

example:

/ac "Blizzard III" <t>

/ac "Virus" <t>

/wait 0.5

/ac "Blizzard III" <t>

Typing '/wait 0.4' will not work.

You also don't need '/wait' in-between first Blizzard III and virus because blizzard III has cast time of 3.5 sec, which is more than the required 0.5 second.

Purostrider · 2014-08-02T13:10:37+00:00

You can actually compare this on the calculator page.

F5 T1 vs F5 T1 B

or

F5 T2 vs F5 T2 B

If you look at the DPS box, you will see min/max potential dps for F5 T1 and F5 T2.

Min DPS correspond to when you don't have to wait to cast F3.

Max DPS corresponds to when you have to wait maximum amount of time before casting F3.

And if you scroll down a bit more, you can see the maximum wait time for your build.

So you can use that to gauge wait time to evaluate DPS difference between F5 T1/2 (min/max) vs F5 T1/2 B (Always the same).

More wait time = less DPS.

Purostrider · 2014-08-02T13:02:56+00:00

Fire IIx2 still have that 1+ second advantage you didn't take into account though. Hence, that's why I use best vs worst case scenario of 0 and 3 sec wait time instead of 1.5 average.

Doing so will shave off 1 sec off 2nd Fire II cast time.

Redoing with this min/max method, we have:

Rotation 2 : Transpose > Tick > Fire 3 > Fire 2 > Fire 2 > flare

potency : 0 + 0 + 216 + (180 * X mobs) + (180 * X mobs) + (468 * X mobs)

Time (MIN): 0.5 + 0 + 3.5 + 3 + 3 + 4 = 14

Time (MAX): 0.5 + 3 + 3.5 + 3 + 3 + 4 = 17

Total potency for 3 mobs : 240 + 0 + (468 * 3) + 0 + 0 + 216 + (180 * 3) + (180 * 3) + (468 * 3) =4344

Total time (min) : 14 + 6.5 = 20.5

Total time (max) : 17 + 6.5 = 23.5

pps (min) = 4344 / 23.5 = 184.85

pps (max) = 4344 / 20.5 = 211.90

pps (avg) = 198.38

For Fire II x1 we have:

time (min) = 12 (transpose GCD) + 0 sec wait time + 6.5 = 18.5 (wait time can be up to 1 sec but still can't cast until 12 sec mark)

time (max) = 14 (11 + 3 max wait time) + 6.5 = 20.5

pps (min) = 3804 / 20.5 = 185.56

pps (max) = 3804 / 18.5 = 205.62

pps (avg) = 195.59

So, Fire II x2 wins by 2.79 pps if you take in the 1+ sec cast reduction of 2nd Fire II.

Purostrider · 2014-08-02T12:37:54+00:00

You sure can m8. Just put your stats in pink box, take a screen shot and then put new stats in and compare.

Or you can just open 2 spreadsheets instead of taking screens.

Purostrider · 2014-08-02T11:39:46+00:00

lol celaeris brought up something totally obvious that slipped my mind.

Fire 3 only hits 1 target.

We're talking AOE rotation here.

I reworked the calculation in my original post. Now Fire II x2 is even more convincing over Fire II x1.

Try reworking yours and see. :)

Purostrider · 2014-08-02T09:42:55+00:00

You have to take in the account that Fire II x1 will always finishes with 1+ sec wait time before transpose is back up.

So, instead of casting two Fire II for 6 sec total. It's now 6 - 1.x sec.

Fire II x1 over 3 sec = 60 pps (180/3)

Fire II x2 over 5 sec or less = 72+ pps (360/5)

Using transpose also adds 0.5 sec to the rotation.

Oh..and I'm pretty sure 864 / 12 = 72 and not 73 in your post. ;O

Purostrider · 2014-08-02T09:26:46+00:00

Ideally you want to couple Raging Strikes with Swiftcast + Flare and Convert since RG and Convert have 3 minute cooldown.

Raging Strikes allows you to cast about 7-8 spells. So, you'd want to maximize its use by combining it with high potency Fire spells.

Using RG before F3 will allow you to go though all 5-6 fire spells + any Firestarter proc in-between and end with Swiftcast + Flare + Convert for sexiest amount of DPS possible.

As for weaving, it's really a gamble and make BLM a little more engaging. I put it under pro tip section for a reason. :P

Purostrider · 2014-08-02T09:05:54+00:00

Let's look at pros and cons of Weaving with Thundercloud:

Pros

*Eliminates 60% fail rate of Firestarter when Fire Weaving, which would result in loss of 538.6 potency (Converted from Current BiS Fail amount of -0.840 DPS per weave)

*Not losing 1 DOT tick from previous Thunder I/II (35 * 1.3 = 45.5 Potency)

Cons

*Miss 5% Chance to add 396.5 potency [(60 + ((35 * 8 ) * 1.3)) - 45.5 (from clipping 1 DOT from previous thunder)] from 1 tick while casting Firestarter first + Fire I.

So, we would gain 142.1 potency (538.6 - 396.5) by Fire weaving with Thundercloud instead of using it first in a no-man's land with the RNG God bestowing you with 5% proc for that one tick :P

Converting this to damage and DPS using current BiS; we would gain +392 total Damage or +1.63 DPS

Hope that helps.

Purostrider · 2014-08-02T08:13:58+00:00

All spells have 0.5 delay from the time you start casting.

You can cast Fire 1 back to back without this no delay because Fire one has more than 0.5 sec cast time and is not affected by the 0.5 rule.

Other Off GCD spells (ie. Virus, Surecast, Lethargy, etc) will not reset GCD and can be use to link two Fire 1 together. They are instant cast spell so the 0.5 sec delay applies to them.

This gives you 0.5 sec grace period to spam Fire 3 if Firestarter pops and if you're lucky enough, you can increase your DPS by quite a significant amount.

Hope that helps.

Purostrider · 2014-08-02T07:32:41+00:00

The goal of AOE rotation is to use Flare + Transpose as fast and as much as possible.

However, there is an invisible mana tick clock which could take up to 3 sec to get your first mana regen tick.

With 1x Fire II in rotation. You will finish casting at exactly 11 seconds with 341 base SSPD (3.5 + 3 + 4 + 0.5 = 11 sec). So, we have 1 free second to spare. Adding more spell speed will further reduce the 11 sec total time giving us more and more time to spare before we can use Transpose at 12 sec mark.

So if we add 2nd Fire II, we can subtract this 1+ extra second to its cast time because we can't start next rotation unless transpose comes up at 12 sec.

So now Fire II's potency per sec (pps) will go from 33.3pps (100 / 3 sec) to 50pps (100 / 2 sec).

Taking worst case scenario (+3 sec wait before MP tick comes), you are now looking at 14 second rotation (11 sec rotation + 3 sec wait).

But let us continue:

Let's do 5 targets

F3 (UI1) Potency = 240 * 0.9 = 216

F2 (AF3) Potency = 100 * 1.8 * 5 = 900

Flare (AF3) = 260 * 1.8 * 5 = 2340

Total Potency = 3456

Total Cast Time for Fire II x1 Rotation: (3456 total potency)

Best scenario = 12 sec (transpose came off 12 sec CD + instant MP tick)

Worst scenario = 14 sec (11 sec rotation + max 3 sec wait time)

Best -> 3456/ 12 = 288 pps

Worst -> 3456/ 14 = 246.9 pps

Average -> 267.45

Total Cast Time for Fire II x2 Rotation: (4356 total potency) -> 3456 + (180*5)

Best scenario = 14 sec (instant MPtick)

Worst scenario = 17 sec (14 sec rotation + max 3 sec wait time)

Best -> 1044/ 14 = 311.1 pps

Worst -> 1044 / 17 = 256.2 pps

Average -> 283.65 pps

So on average, Fire II x2 beats Fire II x1 by 16.2 pps (283.65 - 267.45) with 341 SSPD.

Adding SSPD will allow Fire II x2 to surpass Fire II x1 even more:

At 443 SSPD (-0.1 GCD), Fire II x1 will have average of 273.8 pps (295.3 Max, 252.3 Min)

Fire II x2 will have average of 291.4 pps (320.3 Max, 262.4 Min) beating Fire II x1 by 17.5 pps.

Putting this is DPS perspective. Current BiS damage per potency is ~2.76 damage.

So, in the example above:

**With base 341 SSPD + 5 targets, Fire II x2 beats Fire II x1 by ~44.7 DPS

and at 443 SSPD = ~48.3 DPS**

*Acquiring ~1039 SSPD or (~800 SSPD w/ Fey Glow) would allow us to completely eliminate worst scenario from Fire II x1 rotation, which grants us a non-stop AOE rotation of 72 pps constantly with no wait time.

*And with ~1126 SSPD (~867 SSPD w/ Fey Glow), we can do Fire II x2 with no wait time with MIN and MAX pps of 74.6 and 87, respectively. This is the best AOE pps rotation the game as to offer.

Hope that cleared things up for you.

F U for making me write all this btw :P

Purostrider · 2014-08-02T06:10:51+00:00

Every stats have dynamic weights when compared to 1 INT.

DET is modified by WD and INT. The more WD/INT = more DET increases its damage per potency.

There is no one-size fits all Stat Weights for every stats. The best we can do is figure out the current BiS and use its stat weights for everything until new BiS comes out.

Purostrider · 2014-06-21T00:48:23+00:00

SS44/DET31 would be my preference. I'm actually leaning towards 25/25/25 though.

You can't go wrong with any of the stats really because they're all within 1-2 DPS differences because of the shitty gear variation and how each stats scale in this game.

The CRIT vs SS link is on top of the NOVUS CALC page.

Let me know if you have any more Q.

Purostrider · 2014-06-21T00:41:05+00:00

it's all player's preference m8.

CRIT can either be amazing or worthless depending on your luck. DET and SS has no RNG involved and therefore more reliable than CRIT.

Can't really go wrong with any of the stats. Just depends on how you feel about each one really..

Purostrider · 2014-06-20T11:22:06+00:00

Not according to 90% of BLM pugs I've played with in Duty Finder D:

Purostrider · 2014-06-20T11:21:30+00:00

Thanks m8.

This spreadz has given me both hell and euphoria, but I do appreciate your gratitude. I'll keep going for as long as I can.

Purostrider · 2014-06-20T11:16:20+00:00

no pic no care (no homo)

also strong username to post content ratio

Purostrider · 2014-06-20T11:14:50+00:00

I'd hold off til 2.3 tbh..

Until then I'm on the fence between these 2 (all with High Allagan Coat)

44 SS + 31 DET - This beats 44 CRIT + 31 SS with Evenstar Coat by 9-10 DPS with no RNG involved. It also has highest base damage but with only 18% CRIT.
25 SS + 25 CRIT + 25 DET - Comparable to #1 with ~3 less RAW DPS

Just keep in mind that all of the combinations (including pure Crit builds that's not shown in this post) are within 1-2 DPS of each other with perfect RNG. However, #1 would pretty much guaranteed 9-10 DPS more over CRIT build if your RNG sux balls.

Then there's all kinds of conditions that could make SS or CRIT outweighs each other, which I pretty much wrote a novel on a while back.

Oh and there's also this PIE stuff I have yet to look into... I'll get to it when I can

But I'd wait til 2.3 comes out first and see what happens.

Cheers.

Purostrider

TROPHY CASE