Spellcast Help Thread (Link your XML using Pastebin.com for help!)

[Gustave]

Whats your enmity set?

You're giving yourself credit for +68 hp that you are not getting. If ethereal is not in your enmity lear then thats more like 83. Change it to midcast and test.

<!-- Engaged set has HP+140, Emnity set has HP+213, so a difference of +73 -->
If your enmity set has more hp than engaged set why would you equip it precast, then equip hp- then go back up?

You are adding up it like you're going hp down , then enmity, then hp+.


Let's assume you have 1600 hp engaged, it does not matter if you have 1650 or w/e.

if ethereal earring is your lear for enmity
1600 engaged
1673 precast enmity
1543 precast with hp down
1863.
1543/1863

320 hp cured. Am I missing something?

[Motenten]

From a bit of testing:

HP and HPP each take time before they register their new values in the %HP and %HPP variables. A bit of playing around seems to indicate about 3 seconds is needed, but 2 might be sufficient (dependant on /wait timers).

HPMax doesn't change unless you open the equipment window, in order to force the game to refresh the value.

On the other hand, for your purposes, HPMax can be considered mostly a constant. You may add or remove gear for different actions, but you will tend to return to a fixed baseline. So, making use of it is not necessarily a bad thing.

With allowance for Cure 3/4's 2.5 second cast time, I would probably do something like:

    <var cmd="setcalc HPGap %HPMax - %HP" />
    
    <if advanced='$HPGap &lt; 100'>
        <!-- cure kit -->
        <CastDelay Delay="0.5" />
        <AftercastDelay Delay="2.0" />
        <if MPPGT="40">
            <changespell Spell="Cure IV" />
            <equip when="precast" set="FastCast|Cure4PreKit">
            <equip when="midcast" set="Enmity|Cure4Kit">
        </if>
        <else>
            <changespell Spell="Cure III" />
            <equip when="precast" set="FastCast|Cure3PreKit">
            <equip when="midcast" set="Enmity|Cure3Kit">
        </else>
    </if>

And fiddle with the CastDelay value until it works. Might go as high as 1.0, though that would be annoying.

Edit: Not sure on AftercastDelay; I use it in different ways in different xmls, but been a long time since I did pld cure kits, and don't remember exactly why I chose the values I did.

[Masamune]

A ok i misunderstood yur previous post, thanks Gustav indeed i missed that... i'll give a look tomorrow.

Ok Mot I'll try that too, yes you should be right saying HPmax as a constant shouldnot be a problem actually ^^

[Yugl]

Add-on for return rules (Not reflected in pastebin load because I'm not sure what I cut out of the old one and I can't be assed to fix both XMLs atm):

		<elseif Type="PetCommand|BloodPact*" notPetISValid="TRUE">
			<return />
		</elseif>

Edit: Fixed. Old one would have blocked all summons from happening I think (Idk what SummonerPact is, but I assume that's it?).

[Ricekid]

Posting again, anyone have a DNC and a BST xml they like to share?

[Yugl]

Byrthnot has a DNC one located somewhere in this thread.

[Gustave]

I would like setup my thf xml to have the melee first melee hit with full TH (except knife) so the first proc is capped gear th.

Is there a way to a run only once rule?

Maybe setting auto set engaged = TP set then TH set but have my aftercast set to just TP? If I'm understanding this correctly autoset would only process when I engaged but not actions after that while engaged.

[Motenten]

It would work sometimes, but not if you were engaging while out of range and waiting there (eg: waiting for proc). In that case, if you waited, say, 5 seconds after engaging to put regular gear back on, you'd have regular gear on by the time you actually hit the mob. On the other hand, putting TH gear on when engaging but just using a manual reset to put regular gear back on would leave you TPing in TH gear a lot of the time.

If I were to get creative... I'd put on TH gear on engage, and set a variable with your current TP (reset it to -1 on disengage). Then have a periodic call (using a <command> with a wait delay) check to see if your TP has changed (have to account for both actually hitting the mob as well as using a weaponskill, so TP can go up or down); if so, revert to standard TP gear and don't renew the call. It gets more complicated if you want to swap Thief's Knife in and out (possibly restricted based on current TP), and possibly stack with SA/TA/Feint gear if pre-charged, but it should be workable.

[Masamune]

isnot TH much harder to "lvlup" if yu remove TH gears after 1st TH message ?

I 1st thought like Gustave, but after a few NMs i rapidly discovered better to just stay in TH gears to be able to lvlup till TH10 (with Dread atma). Otherwise would take much longer to lvlup... and my ls don't want to hear about anything like "TH8-9 is enough..."

Regarding cure rules, my tests shows the game have hard time to swap correctly (and update HP accordingly) between precast gears and midcast gears...
I'll test with a midcastdelay, but i don't want to use castdelay since im throwing my cures between NM's hits, so have to do all this cure shit within the 2,5secs casting time span (not more).

[Aemora]

For the last 6 hours, been tweaking Yugl's MNK.xml for my THF, and finally managed to get it to be where I want it to be. It still needs tweaking, there's probably a bit in there that's redundant, and I have been pulling my hair out trying to figure out a way to make SA work in a gazillion different circumstances, but finally gave up and just added a simple rule.

Anyway, this is the full file: http://pastebin.com/EybiP2vL

And what I've done with TH, is the following:

        <!-- Change to wear TH gear (Foxfire) -->
        <if spell="Foxfire">
            <cancelspell />
            <if advanced='"$TH"="0"'>
                <var cmd="set TH 1" />
	<action type="equip" set="TH"/>
                <addtochat color="135">Treasure Hunter - ON</addtochat>
            </if>
            <elseif advanced='"$TH"="1"'>
                <var cmd="set TH 0" />
                <action type="equip" set="$TP" />
                <addtochat color="135">Treasure Hunter - OFF</addtochat>
            </elseif>
        </if>
        <if advanced='$TH == 1'>
	<action type="equip" set="TH" when="engaged|aftercast"/>
        </if>

Add a variable up the top:

<var name="TH">1</var>

And then 'cast' Foxfire to equip TH gear and it overwrites your current TP gearset (Eva, PDT, MDT, Haste, there's even an Omni set in there for Abyssea) and perma-equips TH gear whilst TP'in until you 'cast' Foxfire again, which disables the TH function.

The full script is a little bugged when forcing changes between Sets and cycling through sets, but other than that, it's all working fine.

I hope...

[Gustave]

isnot TH much harder to "lvlup" if yu remove TH gears after 1st TH message ?

I 1st thought like Gustave, but after a few NMs i rapidly discovered better to just stay in TH gears to be able to lvlup till TH10 (with Dread atma). Otherwise would take much longer to lvlup... and my ls don't want to hear about anything like "TH8-9 is enough..."

If that's that case then you probably need a capped haste TH tp set. But even if your farming multiple mobs I would rather kill more than proc 10.

If I were to get creative... I'd put on TH gear on engage, and set a variable with your current TP (reset it to -1 on disengage). Then have a periodic call (using a <command> with a wait delay) check to see if your TP has changed (have to account for both actually hitting the mob as well as using a weaponskill, so TP can go up or down); if so, revert to standard TP gear and don't renew the call. It gets more complicated if you want to swap Thief's Knife in and out (possibly restricted based on current TP), and possibly stack with SA/TA/Feint gear if pre-charged, but it should be workable.

Going to aim for this.

Was a real pain in the ass trying to outparse an empy nin with my basic thf in salvage gears and try to hit them all with max TH lol

[Esvedium]

I had a rule that was based off of %targethpp or something like that for a while, but it was unreliable, so for now on my THF, I have my +TH gear (not including knife) swapped in on my /range, then I'll get TH if I'm pulling mobs in dyna, or I can just hit /ra while running up to a mob to get the first hit in. I have an aftercastdelay set for /ra of a few seconds, don't remember off hand, and it's always been enough to either throw my raider's boomerang at the mob or get that first swing in, then it goes back to either idle or tp, based on status.

It's not all fancy and automated, but it works well enough that I don't feel a need to "fix" it any further.

[Gustave]

That sounds perfect, my only problem is I hate reaching for 1-0 macros so I bind nearly everything to alt or crt letter keys.


Is there I was to add key bindings to windower init.txt temporarily? Use autoexec to execute a script that adds the bindings but how would i delete them when i changed jobs? Or can you link a script.txt file with bindings to your windower file?


Example
<-Scripts(folder->
Job1.txt (contians Alias and key bindings)
Job2.txt
Job3.txt

//exec job1.txt

Would this enable those bindings ?

[Esvedium]

I have all of my macros saved in txt files that I execute when I change jobs. I could use autoexec to automate it, but haven't gotten around to it.

//exec esve/ninwar.txt

Then in that txt file is something like the following.

Spoiler: show

clearbinds
bind ^v paste
bind f12 screenshot png hide
bind !f10 drawdistance set 5
bind ^f10 drawdistance set 1
bind f11 game_forceambientlight
bind !f fillmode

input /macro book 3
input /macro set 1

bind !` input /ja Provoke <stnpc>
bind !1 input /ma "Utsusemi: Ichi" <me>
bind !2 input /ma "Utsusemi: Ni" <me>
bind !3 input /ma "Myoshu: Ichi" <me>
bind !4 input /ma "Migawari: Ichi" <me>
bind !5 input /ma "Yurin: Ichi" <t>

bind ^1 input /ja Provoke <t>
bind ^2 input /ja Berserk <me>
bind ^3 input /ja Warcry <me>
bind ^4 input /ja Aggressor <me>
bind ^5 input /ja Yonin <me>
bind ^6 input /ja Innin <me>
bind ^7 input /ma "Hojo: Ni" <t>
bind ^8 input /ma "Kurayami: Ni" <t>
bind ^9 input /ma "Jubaku: Ichi" <t>
bind ^0 input /ma "Aisha: Ichi" <t>

bind @` input /item "Forbidden Key" <stnpc>
bind @1 input /ws "Blade: Hi" <t>
bind @2 input /ws "Blade: Yu" <t>
bind @9 input /ma "Monomi: Ichi" <me>
bind @0 input /ma "Tonko: Ni" <me>

bind !f1 input /ma "Katon: Ni" <t>
bind !f2 input /ma "Doton: Ni" <t>
bind !f3 input /ma "Suiton: Ni" <t>
bind !f4 input /ma "Huton: Ni" <t>
bind !f5 input /ma "Hyoton: Ni" <t>
bind !f6 input /ma "Raiton: Ni" <t>
bind !f9 burst
bind !f10 tornado
bind !f11 quake
bind !f12 flood

bind ^f1 input /ma "Hyoton: San" <t>
bind ^f2 input /ma "Katon: San" <t>
bind ^f3 input /ma "Suiton: San" <t>
bind ^f4 input /ma "Raiton: San" <t>
bind ^f5 input /ma "Doton: San" <t>
bind ^f6 input /ma "Huton: San" <t>

alias m meteor
alias drops input /item "Echo Drops" <me>
alias kat input /equip main Kannagi; wait 1; input /equip sub Kamome
alias dag input /equip main "Twilight Knife"; wait 1; input /equip sub Kamome
alias gkat input /equip main Uchigatana
alias fork input /equip main "Pitchfork +1"
alias club input /equip main "Raphael's Rod"; wait 1; input /equip sub Kamome
alias staff input /equip main "Terra's Staff"
alias sword input /equip main "Centurian's Sword"; wait 1; input /equip sub Kamome

The clearbinds at the top means I have to set all the basic binds, screenshots, etc. I have a txt file for almost all of my main/sub combos. If I have some off-sub for some reason, I just load one of the random ones for that main job.

[Gustave]

Perfect.

[Gustave]

Trying to grasp elseif. Are these 2 the same?

    <if>
        <if>
        </if>
        <elseif>
        </elseif>
        <else>
        </else>
    </if>

    <if>
        <if>
        </if>
        <else>
            <if>
            </if>
            <else>
            </else>
        </else>
    </if>

[Radec]

Trying to grasp elseif. Are these 2 the same?

Yes

[Gustave]

Any benefit to

    <if status="Visitant">
        <if advanced='&quot;$Blade:Hi&quot; = &quot;DEX&quot;'>
        <var cmd="set Blade:Hi AGI" />
    </if>
    <elseif advanced='&quot;$Blade:Hi&quot; = &quot;AGI&quot;'>
        <var cmd="set Blade:Hi DEX" />
    </elseif>
    </if>

Over

 <if status="Visitant">
      <var cmd="set Blade:Hi AGI" />
</if>
<else>
      <var cmd="set Blade:Hi DEX" />
</else>

[Esvedium]

Any benefit to

    <if status="Visitant">
        <if advanced='&quot;$Blade:Hi&quot; = &quot;DEX&quot;'>
        <var cmd="set Blade:Hi AGI" />
    </if>
    <elseif advanced='&quot;$Blade:Hi&quot; = &quot;AGI&quot;'>
        <var cmd="set Blade:Hi DEX" />
    </elseif>
    </if>

Over

 <if status="Visitant">
      <var cmd="set Blade:Hi AGI" />
</if>
<else>
      <var cmd="set Blade:Hi DEX" />
</else>

Second looks far simpler, but this is what I use:

<if area="Abyssea*">
	<equip when="precast" set="Abyssea-Hi" />
</if>
	<else>
		<equip when="precast" set="BladeHi" />
	</else>

[Radec]

/Crazypills, but those appear to be doing different things - top one toggles between agi and dex every action if visitant is up, lower one swaps to and stays on agi in abyssea, swaps to and stays on dex outside.

Edit: The tabs make it clear what was intended, but I'm trying to make a point that you understand the lower one better, and should definitely use it