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

**Himay** · 2012-05-18 22:33

With regards to the cure staff issue in mote's new whm|sch xml's mentioned above, I don't know if this is of any help, but it will equip my apollo's staff on the first casting of cure after loading the xml, but does not for all subsequent casting of cure spells.

Edit: Also, whatever I manually change my staff to, it keeps that staff on during/after casting cures.

**ssjjfar** · 2012-05-18 22:48

Why is my spellcast crashing while on DNC?
First time I thought it was a lvl sync problem, but now I'm out solo and it crashes everytime I use JA, or I type in /p /l.
I had no xml at first, just lvling 1-30. But i tired making one that it would load with empty sets, and it does same thing.

No problems on other jobs 99.

**Nightfyre** · 2012-05-18 23:40

Hold on, let me go find a psychic with programming experience for you.

**Yugl** · 2012-05-19 01:04

Originally Posted by ssjjfar

Why is my spellcast crashing while on DNC?
First time I thought it was a lvl sync problem, but now I'm out solo and it crashes everytime I use JA, or I type in /p /l.
I had no xml at first, just lvling 1-30. But i tired making one that it would load with empty sets, and it does same thing.

No problems on other jobs 99.

You're going to need to post your XML for us to see what is wrong with the XML.

**ssjjfar** · 2012-05-19 06:52

Originally Posted by Yugl

You're going to need to post your XML for us to see what is wrong with the XML.

I forgot to put the error which looks like this:

Code:

Spellcast encountered a fatal error and must be terminated. Error: Access violation in OutgoingText method.
Spellcast - Plugin successfully unloaded.

This was happening when I had no DNC xml made at all.

But here is my default :

Code:

<?xml version="1.0" ?>
<spellcast>
	<config AutoLoadXML="true" />
	<variables />
	<sets />
	<rules />
</spellcast>

and here is the empty dnc code I made to try and fix it.

Code:

<?xml version="1.0" ?>
<spellcast xmlns:xi="http://www.w3.org/2001/XInclude">
    <config
        RequiredVersion="2.15"
        Debug="False"
        HideErrors="False"
        ShowGearSwaps="False"
        ShowSpellInfo="false"
        />
    <sets>
        <group default="yes" name="DNC">
            <set name="Standard">
                
            </set>
            <set name="Resting">
                
            </set>
            <set name="Engaged">
                
            </set>
        </group>
    </sets>
    <variables>
        
    </variables>
    <rules>
        <if spell="autoset">
            <equip when="resting" set="Resting" />
            <equip when="idle" set="Standard" />
            <equip when="engaged" set="Engaged" />
        </if>
        
    </rules>
</spellcast>

Something else is happening cause there is nothing in the xmls to happen to make spellcast even doing anything. And it is crashing on anything typed, even just saying hello in LS or party chat.

**grevenilvec75** · 2012-05-19 09:26

Originally Posted by ssjjfar

I forgot to put the error which looks like this:

Code:

Spellcast encountered a fatal error and must be terminated. Error: Access violation in OutgoingText method.
Spellcast - Plugin successfully unloaded.

This was happening when I had no DNC xml made at all.

But here is my default :

Code:

<?xml version="1.0" ?>
<spellcast>
	<config AutoLoadXML="true" />
	<variables />
	<sets />
	<rules />
</spellcast>

and here is the empty dnc code I made to try and fix it.

Code:

<?xml version="1.0" ?>
<spellcast xmlns:xi="http://www.w3.org/2001/XInclude">
    <config
        RequiredVersion="2.15"
        Debug="False"
        HideErrors="False"
        ShowGearSwaps="False"
        ShowSpellInfo="false"
        />
    <sets>
        <group default="yes" name="DNC">
            <set name="Standard">
                
            </set>
            <set name="Resting">
                
            </set>
            <set name="Engaged">
                
            </set>
        </group>
    </sets>
    <variables>
        
    </variables>
    <rules>
        <if spell="autoset">
            <equip when="resting" set="Resting" />
            <equip when="idle" set="Standard" />
            <equip when="engaged" set="Engaged" />
        </if>
        
    </rules>
</spellcast>

Something else is happening cause there is nothing in the xmls to happen to make spellcast even doing anything. And it is crashing on anything typed, even just saying hello in LS or party chat.

Are you wearing any new gear (like event gear)? if so try updating your resources.

**ssjjfar** · 2012-05-19 13:20

Originally Posted by grevenilvec75

Are you wearing any new gear (like event gear)? if so try updating your resources.

Ok, updating resources didn't do anything, but after taking off decennial body legs and ring, problem is solved.
Thanks for the help.

**Motenten** · 2012-05-19 15:18

Originally Posted by Himay

With regards to the cure staff issue in mote's new whm|sch xml's mentioned above, I don't know if this is of any help, but it will equip my apollo's staff on the first casting of cure after loading the xml, but does not for all subsequent casting of cure spells.

Edit: Also, whatever I manually change my staff to, it keeps that staff on during/after casting cures.

Ok, think I know the problem for your whm. Do you have a Tefnut Wand build? I'm guessing not. As currently built, it cures in Tefnut Wand if you idle with Owleyes, or cures with staff if you idle with staff. If it's in Tefnut mode and you don't have it, nothing's gonna swap.

This is really far too specific to my own setup, and is problematic when used by anyone else, so I made a number of modifications to the general setup and logic. You can now set some variables in the vars section that control the behavior, so you don't have to mess around with the sets much. There are still things that have to be tweaked for personal use, but hopefully it'll be a lot easier to work with.

**Himay** · 2012-05-20 00:19

Originally Posted by Motenten

Ok, think I know the problem for your whm. Do you have a Tefnut Wand build? I'm guessing not. As currently built, it cures in Tefnut Wand if you idle with Owleyes, or cures with staff if you idle with staff. If it's in Tefnut mode and you don't have it, nothing's gonna swap.

This is really far too specific to my own setup, and is problematic when used by anyone else, so I made a number of modifications to the general setup and logic. You can now set some variables in the vars section that control the behavior, so you don't have to mess around with the sets much. There are still things that have to be tweaked for personal use, but hopefully it'll be a lot easier to work with.

You're more awesome than awesome is awesome.

**Skylark** · 2012-05-21 02:37

Well after deciding to scrap the previous xml, I wrote one completely from scratch. This is my first attempt at writing one from bottom to top and was wondering if I could just get people's 2cents. It seems to have no errors when I check it, but I won't know until I go out and test it. If anyone see anything that's missing/needs to be fixed please let me know. http://pastebin.com/NSW6u4Be

**Motenten** · 2012-05-21 15:18

Originally Posted by Skylark

Well after deciding to scrap the previous xml, I wrote one completely from scratch. This is my first attempt at writing one from bottom to top and was wondering if I could just get people's 2cents. It seems to have no errors when I check it, but I won't know until I go out and test it. If anyone see anything that's missing/needs to be fixed please let me know. http://pastebin.com/NSW6u4Be

This:

Code:

                <if prefix="/ma">

Has several problems:
1) There is no 'prefix' rule; it's 'CommandPrefix'
2) CommandPrefix gets expanded to the full value for comparison, so "/ma" doesn't work; it needs to be "/magic"
3) It's almost always better to group by proper categories, such as type="WhiteMagic" (if you need separation for behavior between, say, white and black enfeebles), or just use the Skill="EnfeeblingMagic" type groupings, rather than using CommandPrefix. The instances where CommandPrefix is better do not apply to what you've written.
4) You've included additional specific spell checks after the prefix="/ma" rule (in particular, Bio and Bio 2) as <elseif>'s; these rules will never work since they would already have been trapped by the prefix check (well, they wouldn't work if the prefix check was done properly).

You have a lot of general problems with the if/elseif/else concept, it seems. Example:

Code:

            <if skill="EnfeeblingMagic">
                <if Spell="Slow*|Paralyze*|Silence|Dia*">
                    <equip when="precast|midcast" set="EnfeeblingMND">
                        <main>$%SpellElementStaff</main>
                        <sub>Reign Grip</sub>
                    </equip>
                </if>
    
                <if Spell="Bind|Gravity|Sleep*|Break*|Blind*|Dispel|Poison*">
                    <equip when="precast|midcast" set="EnfeeblingINT">
                        <main>$%SpellElementStaff</main>
                        <sub>Arbuda Grip</sub>
                    </equip>
                </if>
                <else>
                    <equip when="precast" set="MACC" />
                </else>
    
            </if>

You use two <if>s, where you should use <if><elseif>. The way it's currently written, if you cast Slow it will pass the first if check and equip EnfeeblingMND plus the staff/grip. It will then check the second if check and fail (it's not any of the specified spells), and finally pass the <else> check because it failed the <if Spell="Bind|etc."> check. That means the MACC set will override the EnfeeblingMND set you equipped earlier.

Every time it reaches an <if>, it will perform a test to see if it passes, even if it passed an earlier <if>. If you want to do an additional <if> check, but -not- let it pass if it passed an earlier check (or fail and use the <else> that goes with it), you need to use <elseif>.

Code:

                <elseif spell="Warp*|Tele*|Haste|Escape|Refresh*|Regen*">
                    <equip when="precast" set="FastCast">
                        <main>Celeritas Pole</main>
                        <sub>Arbuda Grip</sub>
                    </equip>
                    <if spell="Regen*">
                        <equip when="precast">
                            <head>Savant's Bonnet +2</head>
                        </equip>
                    </if>
    
                </elseif>

Warp/Tele spells will never get here; you used a rule at the start of the section to <return /> on those spells (to prevent crashing due to gear swaps when zoning).

Code:

            <set name="Nuke">
                <main>$%SpellElementStaff</main>
                <sub>Wise Grip</sub>
                <ammo>Witchstone</ammo>
                <head>Nefer Khat +1</head>
                <neck>Stoicheion Medal</neck>
                <lear>Novio Earring</lear>
                <rear>Hecate's Earring</rear>
                <body>Anhur Robe</body>
                <hands>Nares Cuffs</hands>
                <lring>Strendu Ring</lring>
                <rring>Diamond Ring</rring>
                <back>Searing Cape</back>
                <waist>Oneiros Sash</waist>
                <legs>Rubeus Spats</legs>
                <feet>Goliard Clogs</feet>
            </set>

....

                <if spell="Blizz*|Thund*|Water*|Stone*|Aero*|Fire*">
                    <equip when="precast|midcast" set="Nuke">
                        <main>$%SpellElementStaff</main>
                        <sub>Wise Strap</sub>
                    </equip>

You assign the staff for nukes twice, once in the set you use and once in the rules section. For consistency with how all your other spell types are set up, I'd suggest getting rid of the set entry and just use the rule.

For this:

Code:

            <action type="command" when="aftercast">spellcast var inc bioid;wait 75;input /echo [$bioid:%spell] &lt;%target&gt; Wearing off in 45s On A MuGGGGGGGGGGGGGGGGGGGGGGG</action>

Two issues:
1) You never define the variable 'bioid'. As such, its behavior will be a bit wonky. Make sure to define any variable you use in the <vars> section.
1a) You do define 'BioTimers', but never use that variable.
1b) Same thing with 'sleepid' and 'SleepTimers' (plus 'SleepTimers' is defined twice in the <vars> section).
1c) Same thing with 'breakid' and 'BreakTimers'.
2) You can convert <action type="command"> to just <command>.

That covers the issues I found on a superficial review of the code.

**Skylark** · 2012-05-21 16:18

Thanks for being patient with me, I really am trying to figure out how to completely do all of this so I can move into the more advanced aspect of spellcast coding. I'll make those changes.

**grevenilvec75** · 2012-05-21 18:11

Code:

                              <elseif spell="Drain*|Aspir*">
                                        <equip when="precast" set="Drain|Aspir">
                                                <main>Pluto's Staff</main>
                                                <sub>Arbuda Grip</sub>
                                        </equip>

                              <else>
                                        <equip when="precast" set="DarkMagic">
                                                <main>Pluto's Staff</main>
                                                <sub>Arbuda Grip</sub>
                                        </equip>
                                </else>

Your set is named DrainAspir, not Drain|Aspir. Also you might consider building your DrainAspir set off of your dark skill set (<set name="DrainAspir" BaseSet="Dark"> ) Because how you have it written currently it only equips your dark gear if the spell isnt drain or aspir.

**Nightfyre** · 2012-05-22 11:16

Has anyone else experienced issues with Trigger10 and Trigger12? Debug data suggests that Spellcast is recognizing them improperly - as Trigger0 and Trigger2, respectively. Trigger11 works fine.

**Motenten** · 2012-05-22 12:09

Yes, I had problems with them in the preliminary testing period. Spellcast seems to have issues with certain numeric bits, particularly the number 1, and possibly leading 0's for the first 9 digits (which didn't get used in the final version).

I'm also finding SpellTargetRaw doesn't work quite as advertised. "//update manual" breaks if I'm anywhere near a Field Manual, and any other partial name match (such as a nearby player) will get used instead of the actual text that was entered.

**Yugl** · 2012-05-22 16:45

If you mean preceding 0 as in 01-09, I have that working fine. I've actually opted to use that over single digits since 0-1 do not work (As you know). If you're using <cmd="inc VAR"/>, that changes the variable to a single digit, so you need a second line to add the 0 back into the value.

**Nightfyre** · 2012-05-24 17:55

Originally Posted by Motenten

Yes, I had problems with them in the preliminary testing period. Spellcast seems to have issues with certain numeric bits, particularly the number 1, and possibly leading 0's for the first 9 digits (which didn't get used in the final version).

I'm also finding SpellTargetRaw doesn't work quite as advertised. "//update manual" breaks if I'm anywhere near a Field Manual, and any other partial name match (such as a nearby player) will get used instead of the actual text that was entered.

Lovely. Guess I'll work around it for now.

DRK xml has been updated; Apoc aftermath switching works now, notably, and I've added/changed a few things. Removed the Weapon Bash rule since I still can't track down the source of Darkmagi's issue or replicate it on my own setup.

**Yugl** · 2012-05-25 02:50

If it's a huge change, may want to note that in the XML thread. I'm hoping that will be a single place for XML owners to write changes to their XML without having too many pages of bulk in between. Also, what was the Weapon Bash rule doing/supposed to do?

**Nightfyre** · 2012-05-25 09:03

I had it set up such that casting Stun twice in quick succession would automatically trigger Weapon Bash, so that you wouldn't have to fumble with a second macro if Stun was down. I've since had two reports of it causing crashing issues and I was unable to replicate said issues on my own setup.

I'll leave a note in the xmls thread.

**Sithel** · 2012-05-25 21:15

Can someone take a look at this whm xml for me. I found a basic whm xml and added a few things from other xml's that i liked and now I get a Parsing error: line 343 - Error reading end tag.

I've tried a few things and still isn't working right.
Thanks!
http://pastebin.com/etW0ggCY

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

Thread Tools

Similar Threads

Spellcast Shop Thread

time spent on ls events, helping friends and your own time

Latest Threads

Up & Coming Threads

Hottest Threads