Black Mage Sanctuary - A Guide to DPS

[nugglets]

So, while this opener would have roughly a 7.58 PPS higher than the old Sharpcast opener (depending on SS), it will still be slightly lower than a sharp opener that gets the second Firestarter. And the reason for this is weaving.

If you get a Firestarter in your rotation, where do you put it?

But your opener is still stronger than a normal sharp opener w/o a proc.

Ya, I had noticed the Proc from 3.0 Sharp opener slightly outshines mine above, but I think consistency is better overall. It's something like 1.5PPS advantage for the old one where, as you confirmed, I was seeing 7+ advantage for this one.

And while there isn't time to get the FS proc in under RS, you can still get it in before B3, for a little added potency, with enough time to refresh Enochian. So that brings it even closer to the 3.0 opener with the second proc, I would imagine.

Thanks for checking it for me

[Waliel]

With your mini stances now lasting 12 seconds, you can Swift F3 Convert without FS proc in the F1 FS opener, netting you that extra ~38 potency. A random realisation I got today.

[Garotte14]

With your mini stances now lasting 12 seconds, you can Swift F3 Convert without FS proc in the F1 FS opener, netting you that extra ~38 potency. A random realisation I got today.

I'm not 100% sure I'm understanding what you mean. In the Sharpcast F1 opener with the F3P, You should use your proc first, then weave in Swiftcast, then F4, while weaving in convert. Allowing both Swiftcast and convert to be fully oGCD. Casting Swiftcast after anything that isn't an instant cast would be a slight loss because there would be a delay, even if it's very small. But I could be completely misunderstanding what you're say, so sorry if I am.

[Marianno]

I think Det might be slightly above CHR this patch. Again, that's not confirmed and I haven't thourghly tested it yet, but just something to keep in mind. We haven't had any actual stat weight updates as far as I can see. Ariyala still shows 2.5 weights[/QUOTE]

I would be interested in your findings on this. With all the DET on our gear, there has to be a reason for this.

[Waliel]

I'm not 100% sure I'm understanding what you mean. In the Sharpcast F1 opener with the F3P, You should use your proc first, then weave in Swiftcast, then F4, while weaving in convert. Allowing both Swiftcast and convert to be fully oGCD. Casting Swiftcast after anything that isn't an instant cast would be a slight loss because there would be a delay, even if it's very small. But I could be completely misunderstanding what you're say, so sorry if I am.

If you don't get a FS proc when you do F4 F4 F1, you would normally Swift Flare at the end, but now that AF lasts longer, it's possible to do F4 F4 F1 F4 Swift F4 etc. instead.

[nugglets]

But your opener is still stronger than a normal sharp opener w/o a proc. And also if you can fit T1 in before B4, yes you should always do that. Otherwise you are cutting in to your 25 sec rotation where things are a little more tight, especially if you have to move or get some procs.

After upgrading to Lore pants today, and now with 885SS without food, I can fit the FS proc under RS as well. But... a bad mana tick means not refreshing Enochian if using T1 before B4. It's very, very close, so Fey Wind would cure this I'm sure but I haven't been able to test it with a SCH yet.

So now, the question is whether or not the full opener, with a proc, is beneficial enough to push back T1 to after B4 if you don't have Fey Wind. I want to say it is, but I'm not 100% sure.

Going to test some more and see what I can come up with.

Edit: So, after doing this with a party today MP ticks aren't an issue with the FS Proc, even with T1 before B4 and no Fey Wind, as long as you have the SCH/AST PIE buff.

So I think this is the highest PPS opener right now as long as you meet the SS requirement. I'm not sure exactly what that is right now, but it's somewhere between 815 and 885. I'll try to narrow it down when I have time.

[HaroldSaxon]

As we are nearing the release of Patch 3.2 and the introduction of the next raid tier, the development team has already implemented a stricter log observation, as well as a stricter automated detection for any data irregularities on the server-side.

I would like to mention that should we find tools which unjustifiably control the client process speed, or tools which modify the packets, we will not hesitate to carry out punishment such as banning the offending players.

https://np.reddit.com/r/ffxiv/commen...k_hummelfaust/

And the original player in question is still playing.

[Kuwagami]

That was to be expected. No action being taken on the "original" offender (or more precisely, the first one getting caught), it just encouraged other to keep on cheating. It will continue as long as nothing serious is done, and will continue even after but with more precautions taken by the hackers

[Zantitrach]

That was to be expected. No action being taken on the "original" offender (or more precisely, the first one getting caught), it just encouraged other to keep on cheating. It will continue as long as nothing serious is done, and will continue even after but with more precautions taken by the hackers

Maybe they'll care more since this new guy that was detected was on a JP server?

I mean, extremely doubtful, but I hope?

[IllyriaKnotfred]

That's really discouraging to say the least.