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

[Niberu]

Ok, I'm getting the hang of sc again most of the xmls are working properly. A few of them give the parsing error line 0 ingame, what's the most common cause for this error?

[Yugl]

Not having the include/not naming the include correctly.

If using my XML, this is the include for my v3 XMLs: http://pastebin.com/BtAREr77

[Masamune]

Hello all

I have a problem with my BST xml that may interest also SMNs and PUPs ppl:

Most xmls have usually one Idle set to run around with...
But in the case of pet jobs, being idle doesnot mean necessarily being just running around showing off yur town gears. So the problem occurs when i'm putting my pet on a NM and run...

EDIT: see the rest of post below, forum and probably my fingers fucked up lol...

[Byrthnoth]

Why not include a variable in your idle set so it's something like:
IdleSet=Idle_$Pet
with $Pet = "Pet" or "NoPet"
and then just have two sets, one with pet enhancing gear (Idle_Pet) and one without (Idle_NoPet).

I'm sorry if I'm misunderstanding the question.

[Masamune]

Hello all

I have a problem with my BST xml.

Usually i have only 1 Idle set and 1 engaged set on my xmls but.... in the case of bst i'll need 2 idle sets:
- 1st one being true idle set showing off town, Skadi feet, and dmg taken- gears;
- 2nd one being fake in the sense your pet is tanking and you are out of range from NM (so need to equip Pet:xxx enhancing gears).

My question is: which rule to use to differentiate those 2 idle sets ?
If i use %PetIsValid alone, it doesnot work since i could be running around showing my ass ..... with pet out.
If i use %PetTP and AutoExec, it doesnot work either if Pet has Regain while i'm actually not fighting just running around...
If i use %TargetDistance and %PetIsValid, i would need to know if my pet is engaged (with If Spell="Fight") but then another prob can occurs: if pet dies, SC still thinks my pet is fighting... when i should be on my true idle gears with Skadi feet to run away.

EDIT: yes Byrth it's what i meant but which rules to differentiate between IdlePetFighting and IdlePetNotFighting ?

[Masamune]

ok above posts corrected, sorry for the multiposting :s

[Byrthnoth]

Well, I can imagine something like this:
1) Create a variable "Pet_Fighting" and initialize it to 0.
2) Use Fight to flip a variable (Pet_Fighting) to 1.
3) Use AutoExec to flip the variable back to 0 pet HP hits 0. (is this possible?)
4) Use Spellcast to flip the variable back to 0 if you use Leave, Retreat, or (as a failsafe) Call Beast.

[TacoTaru]

you are way too complicated XD

only need to write :

<equip when="$%Status" set="$%Status"/>

and it will equip directly your Idle, Engaged sets

A little late getting back tot his, but I'm a bit confused. So basically aftercast just needs to be:

<equip when="$%Engaged" set="TP"> or are you saying to literally post what you said? If it's a literal copy/paste, do I need to make a variable for what Status is for engaging

I've never seen an XML uses this rule for status so I'm not sure what I'm supposed to use.

[Masamune]

A little late getting back tot his, but I'm a bit confused. So basically aftercast just needs to be:

<equip when="$%Engaged" set="TP"> or are you saying to literally post what you said? If it's a literal copy/paste, do I need to make a variable for what Status is for engaging

I've never seen an XML uses this rule for status so I'm not sure what I'm supposed to use.

%Status can get the following values: Idle, Engaged, Resting, Dead, Zoning

so writing <equip when="$%Status" set="$%Status"> can have essentially 3 possible interpretation by Spellcast:
<equip when="Idle" set="Idle">
or
<equip when="Engaged" set="Engaged">
or
<equip when="Resting" set="Resting">
or for Dead or Zoning bah justmake emptys ets to not get the error prompt in game

On other hand, if you want to specify a set for Aftercast, Precast, MidCast, then yea gotta write explicitly <equip when="XXXcast" set="SetYouWant"/> where XXX=After or Mid or Pre.




Thanks Byrth i didnot thought about <If petHP=0>, i'll try to work out something with that...

[TacoTaru]

I see, so basically changed the name of TP > Engaged then putting that rule will use that set as long as I'm engaged? Makes sense. When using variables, how does that work? If I'm wanting to TP in mixed evasion how do I make %Status recognize that I don't wanted engaged but mixed-evasion instead?

[Motenten]

If I'm wanting to TP in mixed evasion how do I make %Status recognize that I don't wanted engaged but mixed-evasion instead?

You don't. If you want to gear for multiple statuses then you need to build sets for those configurations, possibly set variable flags to indicate what status you want to gear for, and set them all appropriately. For example, instead of

<equip when="$%Status" set="$%Status" />

you'd have (simplified version):

<if advanced='"$UseEvasion"="Yes"'>
  <equip when="aftercast|engaged" set="Engaged|Evasion" /> or <equip when="aftercast|engaged" set="EngagedWithEvasion" />
</if>
<else>
  <equip when="aftercast|engaged" set="Engaged" />
</else>

or alternatively set a variable called EvasionSet to either "Evasion" or "None" (an empty set) and use:

<equip when="aftercast|engaged" set="Engaged|$EvasionSet" />

[Nightfyre]

I see, so basically changed the name of TP > Engaged then putting that rule will use that set as long as I'm engaged? Makes sense. When using variables, how does that work? If I'm wanting to TP in mixed evasion how do I make %Status recognize that I don't wanted engaged but mixed-evasion instead?

I'm not great at explaining it, but take a look at how my xml handles engaged sets sometime. You could change the variable called Melee to Engaged and use the <equip when="%Status" set="$%Status"> rule (though without the $ used in Masa's status check) suggested above, though you'd have to change the implementation of Armor sets. That won't cover the null value for %Status though.

[Yugl]

If I understand this:
Idle 1: Normal
Idle 2: Pet engaged and you're running from the NM? Movement+Pet enhancement gear?

<if petcommand="SicOrW/eCommandYouUsetoAttack">
<var cmd="set $PetIdle PetIdle" />
</if>
<elseif mode="OR" petcommand="dismiss|W/ethatSitStillOneIs" PetISValid="False">
<var cmd="set $PetIdle N" />
</elseif>

Make sets Idle-PetIdle and Idle-N.

Edit: Oh Byrthnoth got it. If you want a rule for when the mob kicks your pet's ass, use PetISValid="False", which indicates that you have no pet.

[Masamune]

If I understand this:
Idle 1: Normal
Idle 2: Pet engaged and you're running from the NM? Movement+Pet enhancement gear?

<if petcommand="SicOrW/eCommandYouUsetoAttack">
<var cmd="set $PetIdle PetIdle" />
</if>
<elseif mode="OR" petcommand="dismiss|W/ethatSitStillOneIs" PetISValid="False">
<var cmd="set $PetIdle N" />
</elseif>

Make sets Idle-PetIdle and Idle-N.

Edit: Oh Byrthnoth got it. If you want a rule for when the mob kicks your pet's ass, use PetISValid="False", which indicates that you have no pet.

Nope Yugl: i explained in my post why PetIsValid is not enough

rephrasing my question more specifically would be:

How to know my pet is actually fighting ? ie PetStatus="Engaged" ?

[TacoTaru]

OK, I'm pretty sure I got it now. Ignoring the irony of I couldn't figure out why my own XML was borked, is there advantage to using that over what I have been, other than preference?

[Byrthnoth]

I have bastardized your monk XML again, Yugl, to borrow the piping idea. Tonight I will test it!

Is there any specific change in the autoexec between the two versions? I borrowed and modified the includev3 already.

[Yugl]

There shouldn't be any difference in the Autoexec.

Nope Yugl: i explained in my post why PetIsValid is not enough

rephrasing my question more specifically would be:

How to know my pet is actually fighting ? ie PetStatus="Engaged" ?

No way to know Pet's status atm. Your best bet is to have variables set to specific actions (Sic/Dismiss)/PetISValid.

[Masamune]

There shouldn't be any difference in the Autoexec.



No way to know Pet's status atm. Your best bet is to have variables set to specific actions (Sic/Dismiss)/PetISValid.

aw.... /em call @ GM[Yekyaa]

[TacoTaru]

Is there a shorthand way to do obis/sorc pants in one rule instead of taking like 20 lines to do it in?

[Yugl]

Not making promises, but after fixing RDM and BLU (Again, SCH is a logistic terror I'll need more time to work around) I think DRK, SAM, BST, and BRD are the ones not somewhat covered already? I'll need details on those though since I don't play them unless you want a "normal" spellcast for those.