Does anyone know if you can macro where you spam one macro and if fire procs you cast fire 3 on next spell? If you do please help me out!
Firestarter macro!
Printable View
-
12-09-2013, 08:11 PMokieFirestarter macro!
-
12-09-2013, 08:54 PMBlueMage
You mean an auto pilot macro to make the class play itself?
-
12-09-2013, 09:17 PMTeleniel
The in game macro system was not designed to allow you to script a class, and does not allow for conditional affects.
The best you could do is not have enough MP for fire 3... and have your macro be
This would always attempt to cast fire 3 first, and would fall back on casting Fire, if for any reason you couldn't cast fire 3 (lack of MP)Code:/ac "Fire III" <t>
/ac "Fire" <t>
-
12-09-2013, 10:29 PMDevaking55oh jesus...Quote:
Originally Posted by BlueMage
im pretty sure hes talking about a macro where fire3 will cast when it procs....as you should know its annoying casting another fire when you have a firestarter proc ready. -
12-10-2013, 12:08 AMBlueMageYeah, like a Bloodletter macro: making an already simple class even more faceroll. You're right. Having to pay attention to procs and press a different button is super annoying. Can't I just keep spamming 1 and have macros sort it all out for me?Quote:
Originally Posted by Devaking55
-
12-10-2013, 12:19 AMXNihiliWhy even have to spam ? How about one button to do it all ? One button to bring them all and in the darkness bind them ?Quote:
Originally Posted by BlueMage
-
12-10-2013, 01:50 AMZer0mr
No, there is no way to make a macro that shoots off procs whenever they occur. You just have to pay attention and not waste them.
-
12-10-2013, 01:54 AMajxExcept for BLM you always miss firestarter procs as they only proc halfway into your next cast .Quote:
Originally Posted by BlueMage
Problem exists and unless SE fixes you cant blame someone unaware of ToS looking for ways to solve this -
12-10-2013, 02:20 AMLgalang
If only SE will add condition to macro that will be really good. Example
/ac [Firestarter] "Fire III" <t>
/ac [Thundercloud] "Thunder III" <t>
/ac Fire <t> -
12-10-2013, 02:31 AMDarkstarz
Only macro you could possibly use is the following
/ac "Fire" <t>
/wait 2.5
/ac "Fire III" <t>
When u see u get firestarter, stop spamming the button. -
12-10-2013, 03:02 AMJudge_Xero
Since with macros you can't pre activate a skill it would still be better to just use Fire 3 on proc. Over time you would lose more damage waiting for the GCD to finish before using your macro compared to if you miss a proc.
-
12-10-2013, 03:13 AMDarkstarzYes its still better to do it manually as the /wait times only use .5 increments, so spells speed is lost with macros where cast times are involvedQuote:
Originally Posted by Judge_Xero
-
12-10-2013, 04:10 AMSynovius
Do not macro this. Ever. You will be severely gimping your DPS. Further, as was pointed out earlier, you can't really macro this appropriately because there's no way to check if you have a proc. You would have to do this with a third-party program and that would be against the ToS.
-
12-10-2013, 06:49 AMokie
Thx for the replies guess i'll stick with missing a proc cause like someone said if you wait to see if you proc you lose dps cause can already have another fire landing! Anyways thx again and if anyone knows the soft caps for blm and whm i am trying to find info on them!
-
12-10-2013, 08:16 AMSynoviusCheck out my thread called The Black Mage Rotations. I cover Firestarter procs therein. For Firestarter, don't wait and see if you are going to get one. Just keep right on casting and use the Firestarter proc after your next spell (or after a few spells if you're at the end of the Fire I portion of your rotation).Quote:
Originally Posted by okie
-
12-11-2013, 12:56 AMDevaking55*sigh* do you even BLM? You actually lower your dps by waiting for every firestarter proc. so many times ive gotten firestarter to proc twice before actually being able to use it. It makes me sad.Quote:
Originally Posted by BlueMage
same with thundercloud really but then again im just super happy i even got a proc on it :) -
12-11-2013, 03:07 AMMalevicton
As an aside, does any other BLM completely flip out when things line up perfectly: 1) start casting fire, 2) get thundercloud, 3) cast thunder3 as you register a firestarter, 4) roll out of your chair in excitement and miss a landslide
-
12-11-2013, 03:30 AMDevaking55I'm super happy and flip out when thundercloud procs chain themselves back to back lolQuote:
Originally Posted by Malevicton
-
12-11-2013, 11:20 AMBlueMageSo the obvious solution is to completely automate the class? Whats needed is having the proc activate on cast, rather than on hit. What we dont need is a macro that automatically casts Thunder 3 and Fire 3 for you on procs, completely negating any need to pay attention or even press a different button, but I guess I'm a rocket scientist because I dont find my BLM (my main) hard to play? We're already one of the most powerful yet faceroll classes in the game. "SQUARE ENIX! PLEASE MAKE FIRESTARTER AND THUNDERCLOUD AUTOMATIC SO I DONT HAVE TO SWITCH TO PRESSING A DIFFERENT BUTTONZ PLZ!"Quote:
Originally Posted by Devaking55
-
12-12-2013, 03:59 AMDevaking55to do that wouldnt you have to take firestarter off the global cooldown? think about the implications of that.Quote:
Originally Posted by BlueMage
-
12-12-2013, 04:05 AMDaleIt's hard for me to believe that it would lower your dps by any significant amount just by waiting the split second it takes in-between Fire1 casts.Quote:
Originally Posted by Devaking55
But that aside, sometimes Fire Starter will proc twice back to back. So you run the risk of wasting one if you continue casting just like you say. So that's why I think it's best just to wait a tiny bit to be sure.
Agree with you about thunder. The proc on that thing is way too rare. It needs some serious love. -
12-12-2013, 04:10 AMMaeroAgreed, and sometimes 3 in a row :)Quote:
Originally Posted by Devaking55
i actually really like thundercloud -
12-12-2013, 04:25 AMDevaking55exactly! my dream is to dps a mob down with thundercloud chained thunder 3s :) epic winQuote:
Originally Posted by Maero
-
12-13-2013, 01:51 AMMalevictonThat split second of waiting is about the time it takes for wholly another fire1 cast. Don't think of it as losing a firestarter as much as gaining an extra fire1, because that's what is actually happening.Quote:
Originally Posted by Dale
I think thunder feels about right, especially since it's a much more passive proc than firestarter. -
12-13-2013, 06:23 AMDaleYou must have some insane spell speed if you can throw out a fire1 in the tiny amount of time it takes for firestarter to proc in between casts. One of those things I would have to see to believe.Quote:
Originally Posted by Malevicton
-
12-13-2013, 06:34 AMKenji1134
The only time it is somewhat justifiable to wait for a Firestarter proc is on the last Fire 1 of your fire cycle.
Here's the issue. You cast your last F1, then immediately queue B3. F1 lands, you get a FS proc, but B3 now has about 0.5s left on its cast, which is the time interval where you can move without breaking a cast... So your B3 goes off. Now you do your regen cycle, and are now at full mana with 2-3 sec left on your FS proc.
In this situation, your options are to use another B3 for 220 potency then F3 without the FS proc - perhaps leading into the double-F3 speed cast if you are good at it.
Or you can use F3 with the FS proc while in UI3 (154 potency), saving you 0 casting time (fast-cast F3 from UI3 vs Instant from FS), and a whopping 133 mana.
Now if you wait that extra half-second on the last F1 in your fire cycle, 40% of the time, you should get an extra F3 at 396 potency out of it.
A single cycle takes roughly 22 seconds, lets say you are very unlucky with procs and it takes 20 seconds. So by adding an extra 0.5s to your 20s cycle, your dps is dropping by 20/20.5 = ~2.5%.
The shorter cycle using the double-fast F3 trick has a net potency of roughly:
154(B3 in AF3) + 395(Full T2) + 154(F3 in UI3) + 396(F3 in AF3) + 270x3 (F1 in AF3) = roughly 1909 potency in ~ 20 seconds, with no procs.
This is ~95.5 potency/sec, so adding 0.5s to the cycle drops it to 93.1 pot/sec.
By adding this 0.5s delay, we now have a 40% chance to get an extra 396 pot F3 into the cycle, adding ~2.5s to it.
So 60% chance to have 1909/20.5 and 40% chance to have 2305/23 = 95.96 pot/sec average.
So ~95.5 with no procs and spamming buttons, or 96 with the 0.5s extra delay. In this case it IS slightly beneficial to wait for an FS proc on the very last F1... but not every F1. Granted the gain is small, but as we get more procs and have longer average rotations, the dps penalty of the 0.5s delay will get smaller as well.
I guess its a tossup... But uh, never wait on ALL F1s. Wait on the last F1, or none at all. -
12-13-2013, 07:02 AMAllyrionOr you can B3 --> Thunder II --> (Transpose) F3Quote:
Originally Posted by Kenji1134
Guess I'm not sold that double F3 is worth the mana. -
12-13-2013, 11:59 PMWalielYou lose an extra Fire and two potential FS procs with going double F3: 2xF3 + 3xF1 compared to F3 + 5xF1. You can get a fourth Fire with double F3 if your mana ticks align right and you have at least 248 Piety, but then you have to wait for mana for Thunder after B3.Quote:
Originally Posted by Allyrion
-
12-14-2013, 01:43 AMAllyrionOkay, so leaving out the F3 under Umbral for both and using Kenji's potency numbers.Quote:
Originally Posted by Waliel
F1 x 5 (270 under AF3) = 1350 potency
F3 (396 under AF3) + F1 x 3 = 396 + 810 = 1206 potency
So now I'm really not sold, lol. The latter does have a notable time advantage, as it is like 2.5 seconds shorter. However, the above calculation does not even take the two extra potential Firestarter procs into account. Also, if you ever don't get the second quick cast, it's way behind.
Thanks for checking how many casts you get per burn. I was being lazy.