My Hookv4 video was mostly to demonstrate the future native video recording capabilities of windower. I used Exenterator in that video because I was farming Diremites and anything would kill them.
Also, until you get a pretty solid PK set (which is pretty hard to get), Exenterator (which has an easy ideal set for the most part) stays competitive with PK. I think my PK set when I made that video was something like 4/5 Thaumas and Toci's Harness.
The Last Dance: Gearing Paradigms For A New Age
The Last Dance: Gearing Paradigms for a New Age
Leviathan.Kincard said: »
What is it about the new gear that benefits the Terpsichore so much more than the Twash? I kinda wondering if this has an effect on any of the other 1H mythics, particularly Vajra, since they're also on Skadi+1 and Mandalic Stab isn't total crap.
Skadi represents a minor shift away from multi-attack stacking (at least in non-Haste cap sets), which is good for Mythic AM3. Beyond that, I don't feel much has changed at all.
Vajra is a nasty case because of Mandalic Stab:
* Modifiers are really important for dagger WSs because our base damage is so low, and Mandalic Stab is pulling an impressive 30% DEX (the same as Evisceration).
* Typically dagger WSs with shitty mods (like Evisceration - 30% DEX) counter for this by having high combined fTPs (6.0 for Evisc without DA/TA). Mandalic Stab has 3 http://fTP.
* The counter to the low base weapon damage and fTP is supposed to be its large Attack bonus. However, in any situation where you want Thief to be a DD it will need plentiful attack boosts (Berserk, Minuets, Chaos Roll, etc.) like any other DD.
* Mandalic Stab's attack boost (if it works like every other attack boost) does not bypass the ratio cap. Thus, most of the time it won't benefit you at all when you're buffed.
> This weapon appears to have been designed specifically so a Thief in the outside party without buffs could still do decent WS damage on HNMs <
The idea of getting a mythic so that you can do slightly more respectable ***damage from the outside party hurts badly. THF also has no JAs that lets them more easily maintain AM3 like Dragoon (Jumps), Samurai (Meditate), or Dancer (No Foot Rise / Reverse Flourish). You run into viability issues pretty fast with mythic weapons unless you're in a merit party style event with a predictable monster supply or a zerg fight where you can start with 300TP.
It's really been the past few updates beefing up Pyrrhic Kleos that did it for Terpsichore.
Appalled at the claim that I mostly use Exenterator, I made another video of myself drunkenly soloing Apollyon II (with three characters). The mean Tauri gets one over on me when my slow reaction time is bein' slow and I don't get a sash. All is lost.
This probably isn't the best way to redeem the performance of Terpsichore, but it shows what's possible with Terpsichore when you and your support have had a lot of gin and "rice schnapps" and are all played by the same person. I actually went on to kill the demon boss as well, though Sjugy died to an awkwardly timed MS Condemnation. You do not have to kill all the monsters in this zone to kill the NM, and he doesn't seem to link with them.
[+]
Am I the only one who can't see a video? :(
ethanol what does it do?
You should really get Sjugy a college education. Phalanx + Regen V and you can sub Samurai and abuse Demon Killer in this zone!
[+]
Charis+2 isn't dead.
http://yy28.60.kg/test/read.cgi/ff11jobjobplus/1353447383/l50
Skadi+1 body is 0.07
http://yy28.60.kg/test/read.cgi/ff11jobjobplus/1353447383/l50
Skadi+1 body is 0.07
[+]
Does this mean I have to test the set bonus?
[+]
Jinjo took me to Aby-Kon and excluded 5% for me while I was in the shower (although apparently Kparser works strangely on my computer). So thanks to him!
With 97% critical hit rate:
Melee Crit Damage
Player #Crit C.Low/Hi C-0.Avg Crit%
Sylow 380 166/305 242.81 100.00 %
So, it's at least 3% for 2 pieces Testing 4% now.
With 97% critical hit rate:
Melee Crit Damage
Player #Crit C.Low/Hi C-0.Avg Crit%
Sylow 380 166/305 242.81 100.00 %
So, it's at least 3% for 2 pieces Testing 4% now.
96% Critical Hit Rate and Skadi+1 Head/Hands
(Base + Merits + Razed Ruins + Gnarled Horn + Dark Depths + Kacura Subligar+1 )
Melee Crit Damage
Player #Crit C.Low/Hi C-0.Avg Crit%
Sylow 411 160/451 217.73 100.00 %
Set bonus is +4% for two pieces.
(Base + Merits + Razed Ruins + Gnarled Horn + Dark Depths + Kacura Subligar+1 )
Melee Crit Damage
Player #Crit C.Low/Hi C-0.Avg Crit%
Sylow 411 160/451 217.73 100.00 %
Set bonus is +4% for two pieces.
[+]
Damn it...now there's a chance Morrigan's set bonus will make it betterer than Nares too since it's been established the set bonuses arn't equal. >_>
i'll be stuck underwater forever
i'll be stuck underwater forever
Leviathan.Kincard said: »
Damn it...now there's a chance Morrigan's set bonus will make it betterer than Nares too since it's been established the set bonuses arn't equal. >_>
i'll be stuck underwater forever
i'll be stuck underwater forever
Good. Keep farming me Alexandrite.
I
I am a super lucky herpaderp, the set bonus is 3%.
I am a super lucky herpaderp, the set bonus is 3%.
[+]
After 2000000 hits you got a non-crit?
No, JPs reported 3 so Jinjo took me back in and got a non-crit :(.
The one thing I've never really done for this thread is offer any spellcast suggestions, and I've been rewriting mine with Byrth's help in understanding some of the more advanced functions. Byrth's XML gave me an idea.
I've decided to share some of my ideas as I go along.
Background
I only really have room for one Step macro, and I had it as Box Step. So, if daze was at level 5 or something I'd have to manually input other steps! So I did this:
Sylow's Step Switcher Upper
1.) Add this to your Variables:
2.) Add this into your rules section:
3.) Now go to your Windower folder and open up the Scripts folder inside, open up "init.txt" in a text editor and find the section with the binds.
Add this to the binds section:
4.) Change your step macro to /ws "Battle Dance"
5.) You can now use Alt+(Equals Key) to change your preferred step and use them all with a single macro! (You'll either have to restart windower or open the console and type "bind != input /ws "Temporal Shift" without the """ to get it working).
I've decided to share some of my ideas as I go along.
Background
I only really have room for one Step macro, and I had it as Box Step. So, if daze was at level 5 or something I'd have to manually input other steps! So I did this:
Sylow's Step Switcher Upper
1.) Add this to your Variables:
Code
<variables clear="True">
<!---Default Step Variable, Change with "Temporal Shift" --->
<var name="Step">Box</var>
</variables>2.) Add this into your rules section:
Code
<!--- Use the current default step ---> <if spell="Battle Dance"> <if advanced='"$Step"="Box"'> <changespell spell="Box Step" /> </if> <elseif advanced='"$Step"="Quick"'> <changespell spell="Quickstep" /> </elseif> <elseif advanced='"$Step"="Stutter"'> <changespell spell="Stutter Step" /> </elseif> <elseif advanced='"$Step"="Feather"'> <changespell spell="Feather Step" /> </elseif> </if> <!--- Change the current default step, I bind this to Alt+= ----> <if spell="Temporal Shift"> <cancelspell /> <if advanced='"$Step"="Box"'> <var cmd="set Step Feather" /> <addtochat color="135">Steps Defaulted to *** $Step ***( Box | Feather | Quick | Stutter | Box )</addtochat> </if> <elseif advanced='"$Step"="Feather"'> <var cmd="set Step Quick" /> <addtochat color="135">Steps Defaulted to *** $Step *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$Step"="Feather"'> <var cmd="set Step Quick" /> <addtochat color="135">Steps Defaulted to *** $Step *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$Step"="Quick"'> <var cmd="set Step Stutter" /> <addtochat color="135">Steps Defaulted to *** $Step ***( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$Step"="Stutter"'> <var cmd="set Step Box" /> <addtochat color="135">Steps Defaulted to *** $Step *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> </if>
3.) Now go to your Windower folder and open up the Scripts folder inside, open up "init.txt" in a text editor and find the section with the binds.
Add this to the binds section:
Code
bind != input /ws "Temporal Shift"
4.) Change your step macro to /ws "Battle Dance"
5.) You can now use Alt+(Equals Key) to change your preferred step and use them all with a single macro! (You'll either have to restart windower or open the console and type "bind != input /ws "Temporal Shift" without the """ to get it working).
[+]
Here's a more advanced version (MOAR FEATURES!):
Variables:
Rules:
Functionality: By default, functions exactly as above.
/ws "Awful Eye" or //awfuleye will Toggle Step Alternation. Alternating steps default to Box and Feather, but you can change them with //yawn and //lowing respectively.
You still use steps with the same command (/ws "Battle Dance" or //battledance)
Allows you to alternate between two steps with a single macro. Good for something you'll be engaged with for several minutes and will cap out a single daze quickly.
Variables:
Code
<variables clear="True">
<var name="Step">Box</var>
<var name="AlternateSteps">False</var>
<var name="VAR-First">Box</var>
<var name="VAR-Second">Feather</var>
</variables>Rules:
Code
<!--- Use the current default step or next Alternate Step---> <if spell="Battle Dance"> <if advanced='"$AlternateSteps"="False"'> <if advanced='"$Step"="Box"'> <changespell spell="Box Step" /> </if> <elseif advanced='"$Step"="Quick"'> <changespell spell="Quickstep" /> </elseif> <elseif advanced='"$Step"="Stutter"'> <changespell spell="Stutter Step" /> </elseif> <elseif advanced='"$Step"="Feather"'> <changespell spell="Feather Step" /> </elseif> </if> <elseif advanced='"$AlternateSteps"="True"'> <if advanced='"$Step"="$VAR-Second"'> <var cmd="set Step $VAR-First" /> <if advanced='"$Step"="Box"'> <changespell spell="Box Step" /> </if> <elseif advanced='"$Step"="Quick"'> <changespell spell="Quickstep" /> </elseif> <elseif advanced='"$Step"="Stutter"'> <changespell spell="Stutter Step" /> </elseif> <elseif advanced='"$Step"="Feather"'> <changespell spell="Feather Step" /> </elseif> <addtochat color="135">Using $VAR-First Step, $VAR-Second Step will be next.</addtochat> </if> <elseif advanced='"$Step"="$VAR-First"'> <var cmd="set Step $VAR-Second" /> <if advanced='"$Step"="Box"'> <changespell spell="Box Step" /> </if> <elseif advanced='"$Step"="Quick"'> <changespell spell="Quickstep" /> </elseif> <elseif advanced='"$Step"="Stutter"'> <changespell spell="Stutter Step" /> </elseif> <elseif advanced='"$Step"="Feather"'> <changespell spell="Feather Step" /> </elseif> <addtochat color="135">Using $VAR-Second Step, $VAR-First Step will be next.</addtochat> </elseif> </elseif> </if> <!--- Change the current default step, I bind this to Alt+= ----> <if spell="Temporal Shift"> <cancelspell /> <if advanced='"$Step"="Box"'> <var cmd="set Step Feather" /> <addtochat color="135">Steps Defaulted to *** $Step ***( Box | Feather | Quick | Stutter | Box )</addtochat> </if> <elseif advanced='"$Step"="Feather"'> <var cmd="set Step Quick" /> <addtochat color="135">Steps Defaulted to *** $Step *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$Step"="Feather"'> <var cmd="set Step Quick" /> <addtochat color="135">Steps Defaulted to *** $Step *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$Step"="Quick"'> <var cmd="set Step Stutter" /> <addtochat color="135">Steps Defaulted to *** $Step ***( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$Step"="Stutter"'> <var cmd="set Step Box" /> <addtochat color="135">Steps Defaulted to *** $Step *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> </if> <!--- Toggle Alternating Steps on and off ---> <if spell="Awful Eye"> <cancelspell /> <if advanced='"$AlternateSteps"="False"'> <var cmd="set AlternateSteps True" /> <var cmd="set Step $VAR-Second" /> <addtochat color="135">Step Alternation: ON</addtochat> </if> <elseif advanced='"$AlternateSteps"="True"'> <var cmd="set AlternateSteps False" /> <addtochat color="135">Step Alternation: OFF</addtochat> </elseif> </if> <!--- For Alternating Steps, "Yawn" and "Lowing" change the first and second alternating steps, respectively. ---> <if spell="Yawn"> <cancelspell /> <if advanced='"$VAR-First"="Box"'> <var cmd="set VAR-First Feather" /> <addtochat color="135">Alternating Step 1 set to *** $VAR-First ***( Box | Feather | Quick | Stutter | Box )</addtochat> </if> <elseif advanced='"$VAR-First"="Feather"'> <var cmd="set VAR-First Quick" /> <addtochat color="135">Alternating Step 1 set to *** $VAR-First *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$VAR-First"="Feather"'> <var cmd="set VAR-First Quick" /> <addtochat color="135">Alternating Step 1 set to *** $VAR-First *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$VAR-First"="Quick"'> <var cmd="set VAR-First Stutter" /> <addtochat color="135">Alternating Step 1 set to *** $VAR-First ***( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$VAR-First"="Stutter"'> <var cmd="set VAR-First Box" /> <addtochat color="135">Alternating Step 1 set to *** $VAR-First *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> </if> <if spell="Lowing"> <cancelspell /> <if advanced='"$VAR-Second"="Box"'> <var cmd="set VAR-Second Feather" /> <addtochat color="135">Alternating Step 2 set to *** $VAR-Second ***( Box | Feather | Quick | Stutter | Box )</addtochat> </if> <elseif advanced='"$VAR-Second"="Feather"'> <var cmd="set VAR-Second Quick" /> <addtochat color="135">Alternating Step 2 set to *** $VAR-Second *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$VAR-Second"="Feather"'> <var cmd="set VAR-Second Quick" /> <addtochat color="135">Alternating Step 2 set to *** $VAR-Second *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$VAR-Second"="Quick"'> <var cmd="set VAR-Second Stutter" /> <addtochat color="135">Alternating Step 1 set to *** $VAR-Second ***( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> <elseif advanced='"$VAR-Second"="Stutter"'> <var cmd="set VAR-Second Box" /> <addtochat color="135">Alternating Step 1 set to *** $VAR-Second *** ( Box | Feather | Quick | Stutter | Box )</addtochat> </elseif> </if>
Functionality: By default, functions exactly as above.
/ws "Awful Eye" or //awfuleye will Toggle Step Alternation. Alternating steps default to Box and Feather, but you can change them with //yawn and //lowing respectively.
You still use steps with the same command (/ws "Battle Dance" or //battledance)
Allows you to alternate between two steps with a single macro. Good for something you'll be engaged with for several minutes and will cap out a single daze quickly.
[+]
I also want to point out that I didn't really know how to use variables or rules before I wrote this, so it may be bugged and occasionally fail to switch steps or something.
But, it seems to work pretty well on my end, so it just goes to show you how easy spellcast is to learn!
But, it seems to work pretty well on my end, so it just goes to show you how easy spellcast is to learn!
[+]
I see a sort of useability bug, in Step Alternator at the moment. It'll alternate your step to use next every time you hit your step macro, even if you fail because the (a.) step timer is down or you (b.) don't have enough TP or (c.) any other reason.
Pretty sure (b.) is a easy fix but I'm not particularly sure about (a.) and (c.)
(Step Switcher Upper is working flawlessly, just like my hair.)
Pretty sure (b.) is a easy fix but I'm not particularly sure about (a.) and (c.)
(Step Switcher Upper is working flawlessly, just like my hair.)
I fixed it to not alternate if you're not engaged, TP is too low, or slept/amnesia'd etc., but I can't figure out the timer part yet. It's not a gigantic big deal though '-';
Change the "Battle Dance" section of the code above.
Change the "Battle Dance" section of the code above.
Code
<if spell="Battle Dance"> <if status="idle|resting"> <cancelspell /> <addtochat color="115">Unable to use Steps outside of Battle.</addtochat> <return /> </if> <elseif buffactive="Amnesia|Petrification|Sleep|Stun|Terror|Debilitation|Encumberance"> <cancelspell /> <addtochat color="115">Steps failed due to current status.</addtochat> <return /> </elseif> <elseif tplt="10"> <cancelspell /> <addtochat color="115">Steps failed due to low TP.</addtochat> <return /> </elseif> <elseif status="engaged"> <if advanced='"$AlternateSteps"="False"'> <if advanced='"$Step"="Box"'> <changespell spell="Box Step" /> </if> <elseif advanced='"$Step"="Quick"'> <changespell spell="Quickstep" /> </elseif> <elseif advanced='"$Step"="Stutter"'> <changespell spell="Stutter Step" /> </elseif> <elseif advanced='"$Step"="Feather"'> <changespell spell="Feather Step" /> </elseif> </if> <elseif advanced='"$AlternateSteps"="True"'> <if advanced='"$Step"="$VAR-Second"'> <var cmd="set Step $VAR-First" /> <if advanced='"$Step"="Box"'> <changespell spell="Box Step" /> </if> <elseif advanced='"$Step"="Quick"'> <changespell spell="Quickstep" /> </elseif> <elseif advanced='"$Step"="Stutter"'> <changespell spell="Stutter Step" /> </elseif> <elseif advanced='"$Step"="Feather"'> <changespell spell="Feather Step" /> </elseif> <addtochat color="135">Using $VAR-First Step, $VAR-Second Step will be next.</addtochat> </if> <elseif advanced='"$Step"="$VAR-First"'> <var cmd="set Step $VAR-Second" /> <if advanced='"$Step"="Box"'> <changespell spell="Box Step" /> </if> <elseif advanced='"$Step"="Quick"'> <changespell spell="Quickstep" /> </elseif> <elseif advanced='"$Step"="Stutter"'> <changespell spell="Stutter Step" /> </elseif> <elseif advanced='"$Step"="Feather"'> <changespell spell="Feather Step" /> </elseif> <addtochat color="121">Using $VAR-Second Step, $VAR-First Step will be next.</addtochat> </elseif> </elseif> </elseif> </if>
Spellcast's TP variable lags your actual TP, or more accurately, when you hit your step macro it is because you anticipate having the necessary TP by the time the ability goes off, not when you hit the macro. Spellcast will process it when you hit the macro. This is the same problem I have with WS cancel rules especially in high haste situations.
I personally just macro individual abilities because I don't like being able to blame the program for my failures, but there are many things you can automate (waltz selection is another one.)
I personally just macro individual abilities because I don't like being able to blame the program for my failures, but there are many things you can automate (waltz selection is another one.)
Lakshmi.Byrth said: »
Spellcast's TP variable lags your actual TP, or more accurately, when you hit your step macro it is because you anticipate having the necessary TP by the time the ability goes off, not when you hit the macro. Spellcast will process it when you hit the macro. This is the same problem I have with WS cancel rules especially in high haste situations.
I personally just macro individual abilities because I don't like being able to blame the program for my failures, but there are many things you can automate (waltz selection is another one.)
I personally just macro individual abilities because I don't like being able to blame the program for my failures, but there are many things you can automate (waltz selection is another one.)
Interesting, I'll probably just leave it out and learn to stop being trigger happy on my steps. As it stands, I only have box macroed and select the others either through a menu or typing, so Step Switcher gives me more flexibility!
Once you get Terpsi, you will step so much less often that it is not even an issue.I only use presto steps, which means I do box, box, feather, box, box...
If I need FM for violent, I will sometimes use single steps.
If I need FM for violent, I will sometimes use single steps.
I'm stuck with Twashtar for now so I have to step all the time! D:
I've found with Terpsi that I prefer this cycle:
Presto (no sluggish daze) -> Box (1 minute) -> Presto (30 seconds) -> Box (1 minute) -> Presto (30 seconds) -> Feather (30 seconds) -> Presto (0 seconds) -> Box (1 minute...
Also, I feel that macro design is very important and affects how close to the ideal potential you will reach in practice. I set up my macros like this:
Feather/Box/Presto/NFR/Violent/Wild/Subjob/TP/AE/Spectral
Samba/CW5/CW3/TP/SD/RF/WS1/CF/PK/Chocobo
I mostly use the bolded choices, so I should move them closer together because I use a controller. Also, I can probably stand to eliminate the italicized options due to lack of use or better ways to address the same problem. The underlined area is where my selection seems to hover.
* "Subjob" is a subjob specific JA that I use frequently, like Berserk, Meditate, Sneak Attack, whatever. This can be automated with spellcast if you want, but I just do it manually.
* "TP" is a button that cycles through my TP set list (in one direction or the other). I'm finding that I don't actually use my Acc or PDT TP set pretty much ever, so I could probably stand to eliminate them. If I did that, I would only have Marches, Normal, and Evasion, so I could likely drop it down to one button.
* "WS1" is either Exenterator or Evisceration at the moment, but if I eliminated Aeolian Edge from the top row, I would move it to this slot. I change which WS is in this slot on the fly by duplicating the above macro set across multiple sets and moving between them using the up and down buttons. Set 1 is Evisceration, 2 is Exenterator, 3 is Evisceration, and 4 is Evisceration at the moment. There are other minor differences between the sets (like having Fan Dance and moving around some of the non-bold things).
Preliminarily, I think I will change to this for a week and see how I like it:
Feather/NFR/Box/Presto/Violent/Wild/Subjob/Subjob2/FD/Spectral
CW5/CW3/TPtoggle/SD/Samba/WS1/RF/PK/??/Chocobo
I always hate my new macro setups for a while when I change them and I'm sure this time will be no different, but logistically I think that the above macros are better for Terpsi. It opens up a second subjob specific button, puts Fan Dance into the main lineup, and moves things that I use frequently closer together while also keeping Violent Flourish closer to hand. I've been violent flourishing the ***out of ***lately.
Presto (no sluggish daze) -> Box (1 minute) -> Presto (30 seconds) -> Box (1 minute) -> Presto (30 seconds) -> Feather (30 seconds) -> Presto (0 seconds) -> Box (1 minute...
Also, I feel that macro design is very important and affects how close to the ideal potential you will reach in practice. I set up my macros like this:
Feather/Box/Presto/NFR/Violent/Wild/Subjob/TP/AE/Spectral
Samba/CW5/CW3/TP/SD/RF/WS1/CF/PK/Chocobo
I mostly use the bolded choices, so I should move them closer together because I use a controller. Also, I can probably stand to eliminate the italicized options due to lack of use or better ways to address the same problem. The underlined area is where my selection seems to hover.
* "Subjob" is a subjob specific JA that I use frequently, like Berserk, Meditate, Sneak Attack, whatever. This can be automated with spellcast if you want, but I just do it manually.
* "TP" is a button that cycles through my TP set list (in one direction or the other). I'm finding that I don't actually use my Acc or PDT TP set pretty much ever, so I could probably stand to eliminate them. If I did that, I would only have Marches, Normal, and Evasion, so I could likely drop it down to one button.
* "WS1" is either Exenterator or Evisceration at the moment, but if I eliminated Aeolian Edge from the top row, I would move it to this slot. I change which WS is in this slot on the fly by duplicating the above macro set across multiple sets and moving between them using the up and down buttons. Set 1 is Evisceration, 2 is Exenterator, 3 is Evisceration, and 4 is Evisceration at the moment. There are other minor differences between the sets (like having Fan Dance and moving around some of the non-bold things).
Preliminarily, I think I will change to this for a week and see how I like it:
Feather/NFR/Box/Presto/Violent/Wild/Subjob/Subjob2/FD/Spectral
CW5/CW3/TPtoggle/SD/Samba/WS1/RF/PK/??/Chocobo
I always hate my new macro setups for a while when I change them and I'm sure this time will be no different, but logistically I think that the above macros are better for Terpsi. It opens up a second subjob specific button, puts Fan Dance into the main lineup, and moves things that I use frequently closer together while also keeping Violent Flourish closer to hand. I've been violent flourishing the ***out of ***lately.
Another thing I've been considering is using spellcast variables to control skillchaining sets somehow. I've determined that the skillchain window is 10 seconds, so you could maybe see something like:
I mean, skillchain damage mirrors against many targets these days. Charis Bangles +2 and Mujin Band add another 12% skillchain damage (1.38/1.23). Now, increasing the damage of the closing skillchain will increase both your WS and skillchain damage (so a 6% increase in WS damage would match a 12% increase in skillchain damage), but I doubt those two slots are increasing our WS damage by 6% more than Charis Bangles +2/Mujin Band.
I might still not carry Mujin band because it's Inventory +1 and not a large performance improvement, but I would like to at least work Charis hands +2 in because they're so potent and we all carry them already.
Code
<if Spell="Evisceration">
<if Advanced'"$Skillchain" == "Distortion"'>
<equip set="Evisceration|SCdmg" />
<var cmd="set Skillchain Darkness" />
<command>wait 10;var set PreSC Darkness;vulcanshot</command>
</if>
<else>
<equip set="Evisceration" />
<var cmd="set Skillchain Gravitation" />
<command>wait 10;var set PreSC Gravitation;vulcanshot</command>
</else>
</if>
<if Spell="Vulcan Shot" Advanced='"$PreSC"="$Skillchain"'>
<var cmd="set PreSC None" />
<var cmd="set Skillchain None" />
</if>I mean, skillchain damage mirrors against many targets these days. Charis Bangles +2 and Mujin Band add another 12% skillchain damage (1.38/1.23). Now, increasing the damage of the closing skillchain will increase both your WS and skillchain damage (so a 6% increase in WS damage would match a 12% increase in skillchain damage), but I doubt those two slots are increasing our WS damage by 6% more than Charis Bangles +2/Mujin Band.
I might still not carry Mujin band because it's Inventory +1 and not a large performance improvement, but I would like to at least work Charis hands +2 in because they're so potent and we all carry them already.
Interesting idea, Sylow, and a problem that has bugged me in the past. I tweaked your idea to work in my spellcasts, and put it in the general Mote-Rules-Include so that it's usable with any job (you can look at the code there if you're interested, though it's not anything special).
Controls for it:
/ma Trigger1 Cycle(Step)
/ma Trigger1 Cycle(AltStep)
/ma Trigger1 Cycle(UseAltStep)
/ma Trigger1 Cycle(SelectStepTarget)
/ma Trigger1 Step
Note: You can change the trigger number if you like. Make sure to update the rules as well.
Also: "/ma Trigger" currently resolves to "/ma Trigger1", so you can use the commands without the number unless/until they actually fix that in Spellcast.
Cycle(Step) and Cycle(AltStep) rotate through the available steps, like your example.
UseAltStep determines whether or not to use the alternate step. Default is No, but you can set a different default in each job xml.
SelectStepTarget determines whether the default target is the normal <t>, or <stnpc> (which I use in Dynamis for hitting mobs I'm not engaged to). Default is No, but you can set a different default in each job xml. (eh, might change default to Yes)
And then the last command uses the currently defined step/altstep.
I'd probably set up binds like:
bind ^= input /ma Trigger1 Cycle(Step)
bind != input /ma Trigger1 Cycle(AltStep)
And set the UseAltStep and SelectStepTarget values to defaults I expect to keep (or put them in macros on my dustbin palette, as the number of bind options is pretty limited).
Actually, that gives me an idea. ... Ok, put in the ability to customize the binds for Ctrl-=, Alt-=, Ctrl--, Alt--, per job. Set variable values to either a bind value (eg: "input /ma Trigger1 Cycle(Step)"), "None" to unbind, or "Ignore" to not touch existing binds (in case you have binds on those keys already). Variables are: ClassBindCtrlEqual, ClassBindAltEqual, ClassBindCtrlDash, ClassBindAltDash. These are executed on First Run.
Oh, another possible point of failure with alternating steps: being out of range. Can make use of the WS distance limit for that, I suppose, but I didn't bother with it in my code.
Controls for it:
/ma Trigger1 Cycle(Step)
/ma Trigger1 Cycle(AltStep)
/ma Trigger1 Cycle(UseAltStep)
/ma Trigger1 Cycle(SelectStepTarget)
/ma Trigger1 Step
Note: You can change the trigger number if you like. Make sure to update the rules as well.
Also: "/ma Trigger" currently resolves to "/ma Trigger1", so you can use the commands without the number unless/until they actually fix that in Spellcast.
Cycle(Step) and Cycle(AltStep) rotate through the available steps, like your example.
UseAltStep determines whether or not to use the alternate step. Default is No, but you can set a different default in each job xml.
SelectStepTarget determines whether the default target is the normal <t>, or <stnpc> (which I use in Dynamis for hitting mobs I'm not engaged to). Default is No, but you can set a different default in each job xml. (eh, might change default to Yes)
And then the last command uses the currently defined step/altstep.
I'd probably set up binds like:
bind ^= input /ma Trigger1 Cycle(Step)
bind != input /ma Trigger1 Cycle(AltStep)
And set the UseAltStep and SelectStepTarget values to defaults I expect to keep (or put them in macros on my dustbin palette, as the number of bind options is pretty limited).
Actually, that gives me an idea. ... Ok, put in the ability to customize the binds for Ctrl-=, Alt-=, Ctrl--, Alt--, per job. Set variable values to either a bind value (eg: "input /ma Trigger1 Cycle(Step)"), "None" to unbind, or "Ignore" to not touch existing binds (in case you have binds on those keys already). Variables are: ClassBindCtrlEqual, ClassBindAltEqual, ClassBindCtrlDash, ClassBindAltDash. These are executed on First Run.
Oh, another possible point of failure with alternating steps: being out of range. Can make use of the WS distance limit for that, I suppose, but I didn't bother with it in my code.
All FFXI content and images © 2002-2024 SQUARE ENIX CO., LTD. FINAL
FANTASY is a registered trademark of Square Enix Co., Ltd.