


That's actually allowed though (surprisingly), modifying the way the game works to gain an advantage isn't.
3 x Melee will be even more optimal unless there is a specific mechanic that makes it sub optimal (Physical Resist/Heavy AOE/Magic weakness)
Will still be SS>Crit>Det, mainly to try and do 5 x F4 during Ley Lines.Hi all. Just need some expert guidence on something I have been thinking about.
Due to this new buff is the new stat priority Crit>SS>Det or still SS>Crit>Det? Spell speed was very useful before to give more flexibility in high movement situations although this won't be an issue anymore and we are limited in F4 usage per AF phase by MP anyway.
I never said they should hand out a ban based on the evidence in this thread (although it is pretty damning when combined with the video). If they've "conducted an investigation based on official logs that were accumulated within the development team" as they have said, then surely it is just a matter of looking at this player in question and handing out the relevent punishment - especially before 3.2.Dev tracker drew my attention here so I'm gonna chime in. They CANNOT just hand out a ban based on your Evidence. They HAVE to do a proper investigation which can take a bit.To expect otherwise is quite frankly insane because until they have their own investigative proof, it's a case of He Said/She Said. It's also possible action was taken that you're not aware of (IE direct Warnings from a GM and a flag placed on their account to monitor activity) All they've done is announced they implemented new tools to detect stuff. It doesn't mean they've CAUGHT anyone with enough evidence to take action yet.
You've done your part. It's time to walk away from the issue.
I hope that is the case, although that hasn't been the case previously when people have used Position Hacks to clear turns of coil during progression.It's unlikely that they'll ban the person immediately for two reasons:
1) It would verify the name to those who "suspect" but don't know for certain;
2) They're probably searching logs & other information about the user & all their contacts to see if it's more widespread within their "network".
It is also possible that they may really take a hard line & be looking at legal action depending on how the hack was done. There's pretty strong laws in some places covering reverse engineering of software &/or modifications to data transport.
TL;DR Fear not, they'll get their just deserts.
Maybe, but going 3x Melee for progression is a stupid idea since you can't guarantee there won't be a mechanic that enforces having a caster like the things you mentioned.
Kairi™
Or you take a caster that can play Melee well. Flexibility when going for Server or even World Firsts is nice. Obviously this is in a perfect world scenario and you can't gear up multiple classes, but I guess that's what alts are for.
Wish I was in the position to be able to do it, would be fun.
I think BLM and SMN do comparable DPS to NIN/DRG in the majority of fights where that is not necessary. Depending on your group, you may have to switch out a caster for a melee main if another melee DPS would make a difference. Some mechanics can definitely be harder to execute with 3 melees.Or you take a caster that can play Melee well. Flexibility when going for Server or even World Firsts is nice. Obviously this is in a perfect world scenario and you can't gear up multiple classes, but I guess that's what alts are for.
Wish I was in the position to be able to do it, would be fun.
Last edited by lulunami; 02-23-2016 at 09:18 AM.
Fried popoto enthusiast.
For the F4, F4, F1, F4, F4, versus F4 x 4.
My current spell speed (BiS ignoring Diadem and using Eso 210 weapon)
2.5sec GCD = 2.32 sec
3 sec GCD = 2.78 sec
3.5 sec GCD = 3.25 sec
F4 F4 F4 F4 B3 T1 B4 F3 = 20.86 seconds. If Thundercloud Procs
F4 F4 F4 F4 T3P Transpose B3 B4 F3 = 21.79 seconds.
I do not know if you really need to use B3 if you get a proc, it would depend on your mana but if we assume you don't need it, the rotation would be :
F4 F4 F4 F4 T3P Transpose B4 F3 = 19.47 seconds. The problem with this rotation also is that F4x4 is 11.12 seconds. It's really tight to use a proc then transpose, you might transpose into nothing and you'll lose a ton of DPS. However, we haven't placed Swiftcast anywhere. The rotation could be :
F4 F4 F4 F4 T3P Swift B3 B4 F3 = 20.68 sec
You can easily start to assume where I'm going with that.
3 rotation of 20 seconds fix the usage of our cooldowns that we often delay.
If we go F4 F4 F1 F4 F4 B3 T1 B4 F3. It would be 23.18 seconds.
Worst, if you get a F3P, it becomes 25.5 seconds.
If you get a T3P, it would be... 27.82 seconds.
With Leylines, the GCDs become.
2.5sec GCD = 1.972 sec
3 sec GCD = 2.363 sec
3.5 sec GCD = 2.7625 sec
F4 F4 F4 F4 F4 = 11.815 seconds. That's a bit too tight unless we pump more Spell Speed or we have Selene.
With Selene and Leylines :
2.5sec GCD = 1.9024 sec
3 sec GCD = 2.2796 sec
3.5 sec GCD = 2.665 sec
F4 F4 F4 F4 F4 = 11.398 sec
I don't think the F4x5 opener would work because this would mean Flare won't get any boost so I highly doubt we'll get any gain. We'd need an Haste card from Astrologian with Selene and Leylines.
However, we can use Leylines twice per Raging Strikes. I think the most optimal rotation right now would be
F4 F4 F1 F4 F4 B3 T1 B4 F3 still. With Leylines, the rotation is 19.703 seconds.
F4 F4 F1 F4 F3P F4 B3 T1 B4 F3 = 21.675 seconds
I haven't calculate the Off-GCDs we use but the second Leylines should be in the middle of the second rotation. An optimal rotation should look something like :
[F4 F4 F4 F4 B3 T1 B4 F3] [F4 F4 F4 F4 B3 T1 B4 F3] [F4 F4 F4 F4 B3 T1 B4 F3] around 1 minute.
We need to add Sharpcast + Swiftcast
[F4 F4 F4 F4 B3 SharpT1 B4 F3] [F4 F4 F4 F4 T3P SwiftB3 B4 F3] [F4 F4 F4 F4 B3 T1 B4 F3] around 1 minute.
The problem is multiple Thundercloud Procs. We need more Spell Speed.
If we add the second Leylines in the rotation
[F4 F4 F4 F4 B3 SharpT1 B4 F3] [F4 F4 Leylines F4 F4 T3P SwiftB3 B1** B4 F3] [F4 F4 F1 F4 F4 F3P* B3 T1 B4 F3]
* If F1 procs
** We might need a filler to be full mana.
Leylines will do about 0.6 seconds to set. Leylines saves 0.417 sec per F4. So we are safe.
That's roughly what's been in my head so far about the changes. I think we need more spellspeed, I'm trying to work around a new rotation. I found one that I think could work and if I'm correct is about 1.3% better than what we have (with a 57% chance of getting a Thundercloud proc)
I figured this information won't hurt anybody.

Here is my Black Mage guide. My hope is to get this out there for all Black Mages who are new to the game and looking for guidance. If you have any input, please feel free to make any suggestions and I will test them. I would like to thank all of you for your support and contributions to this community.
https://docs.google.com/document/d/1...it?usp=sharing

I don't think you will ever need to use the filler B1 because Swift B3 + F4 are 2 GCDs since UI3 will trigger as soon as you cast out the B3.
Also why do you use T3p in your Fire rotation instead of Ice rotation?
In 3.0 Opener, the Blizzard3 opener I think there's a mistake: You use Swiftcast+Thunder3, so Sharpcast+Enochian should have close 0 time since you use it during the GCD.
Also, another pro of that opener is that you may get Thunder procs with which you can or can not (we'll see) replace F4s and give you higher mobility.
In AoE rotation, you should add F3 after Transpose and then repeat. I'm also not sure if Flare is recommended on 2 targets since it will leave you with 0 MP and UI1.
Last edited by Hontaro; 02-23-2016 at 02:04 PM.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote



