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

[Magi]

I'm using spellcast to tell me when Haste/Refresh etc are wearing off on the person I cast it on, but is there anyway I can change this echo text color so it's more noticeable, like orange for haste, green for refresh? I know there's <addtochat color * > but I have no idea how to make that work with what I have already, apologies for being clueless about all this

<if Spell="Haste">
<command when="aftercast">spellcast var inc hasteid;wait 175;input /echo [$hasteid:%spell] &lt;%SpellTarget&gt; Wearing off in 5s</command>
</if>

[Nishida]

Try this. The 204 after addtochat is the color code. Not 100% on all the codes. I took this from a SMN XML I knew that had a similar coding.

<if Spell="Haste">
            <command when = "aftercast">spellcast var inc hasteid;wait 175;addtochat 204 [$hasteid:%spell] &lt;%SpellTarget&gt; Wearing off in 5s</command>     
</if>

[Cymmina]

Try this. The 204 after addtochat is the color code. Not 100% on all the codes. I took this from a SMN XML I knew that had a similar coding.

<if Spell="Haste">
            <command when = "aftercast">spellcast var inc hasteid;wait 175;addtochat 204 [$hasteid:%spell] &lt;%SpellTarget&gt; Wearing off in 5s</command>     
</if>

The addtochat used here is a plugin. Note that if you use the timestamp plugin, lines inserted via addtochat plugin do not get a timestamp added to them, which makes it line up funny.

[Manque]

I was hoping someone could help me set a variable for equipping my jalzahn's ring for TA in salvage, assault, and nyzul. Is it possible? Thank you ; ;

[Magi]

I copy and pasted exactly what you wrote out Nishida but nothing happened, I tried changing some things around as best I could but I got nothing to work. I checked to see if addtochat worked for me at all and it does, 204 is a dark green, but timestamp actually does show up for me on the same line when it prints to the screen. Not really sure what I'm doing wrong D:

[Yugl]

I was hoping someone could help me set a variable for equipping my jalzahn's ring for TA in salvage, assault, and nyzul. Is it possible? Thank you ; ;

<if spell="TA" Area="Nyzul*|*Remnants|Assault area names here">
<equip>
<lring lock="yes">Jal Ring</lring>
</equip>
</if>

[Manque]

Thank you so much for your help Yugl. /bow

[TacoTaru]

Rewriting my BLM XML from the ground up, but I can't figure out how to make staves equip during nukes without manually typing out:
<if spell="Spell*> etc

I know there's an easy way to do this, but for the life of me I can't figure it out.

[Yugl]

Variables.

        <var name="Staff-Fire">Vulcan's Staff</var>
        <var name="Staff-Ice">Aquilo's Staff</var>
        <var name="Staff-Wind">Auster's Staff</var>
        <var name="Staff-Earth">Terra's Staff</var>
        <var name="Staff-Thunder">Jupiter's Staff</var>
        <var name="Staff-Water">Water Staff</var>
        <var name="Staff-Light">Light Staff</var>
        <var name="Staff-Dark">Pluto's Staff</var>

From here you have two choices. You can place the variable in sets as:
<main>$Staff-%SpellElement</main>

OR

<if spell="W/e parameters you want for spells>
<equip when="midcast>
<main>$Staff-%SpellElement</main>
</equip>
</if>

[TacoTaru]

So if I go with your first option, I don't need anything in the rules concerning spells? Just add:

<main>$Staff-%SpellElement</main>

in my nuking/enfeebling sets, make sure the variables are there and that's that? Feel like I tried this last night, but it may have looked like this:

<main>$Staff%SpellElement</main>

Does the hyphen between them matter?

[Nishida]

I copy and pasted exactly what you wrote out Nishida but nothing happened, I tried changing some things around as best I could but I got nothing to work. I checked to see if addtochat worked for me at all and it does, 204 is a dark green, but timestamp actually does show up for me on the same line when it prints to the screen. Not really sure what I'm doing wrong D:

<if Spell="Haste">
<action type="AfterCastDelay" Delay="175" />
<command>spellcast var inc hasteid</command>
 <action type="addtochat" color="204" when="aftercast">[$hasteid:%spell] &lt;%SpellTarget&gt; Wearing off in 5s</action>
</if>

Try this? if I were able to test this in game + saw your full XML I'd be able to test this myself @_@;

If that doesn't work you can try:

<if Spell="Haste">
<action type="AfterCastDelay" Delay="175">
<command>spellcast var inc hasteid</command>
 <action type="addtochat" color="204"  when="aftercast">[$hasteid:%spell] &lt;%SpellTarget&gt;  Wearing off in 5s</action>
</action>
</if>

Not sure which one is the correct way to put it. They may both work.

Note:
http://wiki.windower.net/plugins/spellcast/colortestxml
this gives an ingame display of all colors and their respective codes for the addtochat variable.

So if I go with your first option, I don't need anything in the rules concerning spells? Just add:

<main>$Staff-%SpellElement</main>

in my nuking/enfeebling sets, make sure the variables are there and that's that? Feel like I tried this last night, but it may have looked like this:

<main>$Staff%SpellElement</main>

Does the hyphen between them matter?

Using the syntax he gave you need to use the hyphen. What $Staff-%SpellElement does is takes whatever the spell element is of the spell you're casting. For example you will get $Staff-Ice when casting Paralyze. So in the variables he has <var name="Staff-Ice">Aquilo's Staff</var>

This essentially makes $Staff-%SpellElement turn into $Staff-Ice which tells spellcast to equip Aquilo's Staff.

[Haborym]

Anyone have a nice spellcast for a Vereth MNK they wouldn't mind sharing?

[fantasticdan]

Can anyone post the code they use to keep gear locked in while a JA as active? I'm attempting to get BLU af3 head/feet locked in during CA/BA, but nothing I've tried wants to work.

[Yugl]

<if mode="OR" BuffActive="Chain Affinity" Spell="Chain Affinity">
<equip when="precast|midcast">
<head lock="true">Mavi Helm</head>
</equip>
</if>

Repeat for BA

[TheDirtyHobo]

You don't need to do the <mode="OR" spell="Chain Affinity"> part, the gear only needs to be equipped on the spell that uses the buff, not during the buff activation. You may also want to make <head> into <head lock="true"> so any other gear swaps won't overwrite it.

Just a quick question about <else> vs <elseif> uses. According to the spellcast wiki:

<elseif>

<elseif> bound rule criteria will be checked only if the immediately preceding <if> or <elseif> rule check evaluated to false. Beyond that, it works exactly the same as an <if> rule and supports the same nesting.

<else>

<else> rules will only process if the entire preceding chain of <if> and/or <elseif> rules criteria checks evaluated to false. In other words, if all the <if> and <elseif> statements return false, the <else> will be the default action. <else> rules do not check against any rule criteria themselves. Beyond that, it works exactly the same as an <if> rule and supports the same nesting.

The way that sounds is that if there's an <else> near the end of your spellcast, every single <if> or <elseif> statement has to check false, yet a friend has has success using an <if> + <else> combo to check time for AF boots vs Danzo in NIN idle set, and the rule came directly after a tautology <if> statement.

So, is it just poor wording on wiki's part (or poor interpretation on my part), and <else> only checks up to the immediately preceding <if> statement, and the only difference between <else> and <elseif> is <elseif> allows for conditions? That seems like it would be the logical way to go.

[Yugl]

I forgot the lock, but yes, lock the piece of gear. The OR is a security measure since lag on fast spells might end up missing the piece of gear. I'll test the elseif stuff soon since I'm working on a XML that heavily relies on a string of them with an <else> at the end.

[Mercilessturtle]

It works like it should, else covers the false cases from the chain of ifs and ifelses.

[fantasticdan]

<if mode="OR" BuffActive="Chain Affinity" Spell="Chain Affinity">
<equip when="precast|midcast">
<head lock="true">Mavi Helm</head>
</equip>
</if>

Repeat for BA

Thanks, this worked, but I did have to add "aftercast|idle" to the when part. Well not sure if both were necessary but it's working now, lol.

One more quick question, how can I lock in items like teleport rings, warp cudgels, etc. so they never get swapped out if equipped?

[Yugl]

<if EquipSpellcastSlotHere="Name of item here">
<equip when="all">
<slot lock="true" />
</equip>
</if>

[Clash Perez]

You don't need to do the <mode="OR" spell="Chain Affinity"> part, the gear only needs to be equipped on the spell that uses the buff, not during the buff activation. You may also want to make <head> into <head lock="true"> so any other gear swaps won't overwrite it.

Just a quick question about <else> vs <elseif> uses. According to the spellcast wiki:



The way that sounds is that if there's an <else> near the end of your spellcast, every single <if> or <elseif> statement has to check false, yet a friend has has success using an <if> + <else> combo to check time for AF boots vs Danzo in NIN idle set, and the rule came directly after a tautology <if> statement.

So, is it just poor wording on wiki's part (or poor interpretation on my part), and <else> only checks up to the immediately preceding <if> statement, and the only difference between <else> and <elseif> is <elseif> allows for conditions? That seems like it would be the logical way to go.

If you don't have an <if> in the spellcast that returns false, the <else> will never be checked.

It works up to the last related if. For instance, something like this works:

<if blah="blah blah">
       <blah />
</if>
<elseif blah="blah blah blah">
          <if blah="blah">
                 <blah />
          </if>
          <elseif blah="blah blah">
                 <blah />
          </elseif>
          <else>
                 <blah />
          </else>
<else>
     <blah />
</else>
<if blah="blah">
     <blah />
</if>
<else>
     <blah />
</else>

The nested <else> works only with the nested <if> chain, and the final <else> works only with the immediately preceding <if> chain, which will be parsed regardless of the status of the initial <if> check.

Does that answer your question? I have a sneaking feeling I've missed something here.