Is this a new NPC opened for the first time in 3.0.4, or has it been opened before?
I've just opened a new NPC in 3.0.4 and the spells parsed out OK.
Printable View
Hmm.. so if I don't set that parse flag.. then it won't try and build it and I could set the bits up manually? So .. for example .. a Mephit has a generic 'summon' spell that cannot be parsed by the parser because it is not a standard spell (it is a variation of summon monster obviously) .. I'm thinking it would be 'best' if I brought it in with an effect 'summon mephit' with a duration of 6 (caster level of the mephit).
Do you know where those codes/tags might be found by any chance?
This is a lot of work for the higher level summonables.. but it seems like it would be worth it as it makes them usable immediately... many parsed spell actions are 'casts' that don't do anything.
These are existing NPCs in modules that I created previous to 3.0.4. If open these modules either in the campaign I used to create the modules, or my main campaign which loads the modules, all my spell-using NPCs so far that I've seen have had empty damage and healing entries in their spells. I have had to go back and fill in all the healing and damage entries by hand. I haven't tried deleting the spells and re-dragging them over from the library modules though, is there a chance that might work better? (I'm not at home right now so I can't try it, but I will looking at this more tonight)
In my module creation campaigns I usually have all extensions disabled, but I'll double check when I get home.
In my main campaign that loads the modules, I have the extensions that have been identified as problematic with 3.0.4 disabled, but I suppose some other extension might be causing problems. Again, I'll check when I get home tonight.
Thanks darrenan - when you have time tonight could you please check and if there are still issues provide steps to recreate. Including posting the modules you are using (with just the NPC content). Thanks.
Note that it is only NPCs created in V2 creature parser that have the <parse> flag set initially. Once they have been opened within the campaign this flag may no longer be set and so won't try to parse the spells.
Hrm. I tried removing the <parse> tag and setting it to 0... in both cases it went ahead and parsed the spell and ignored the code I put in there to setup an effect... I guess I'm not quite as clever as I was hoping I was.
Code:<actions>
<id-00001>
<durdice type="dice"></durdice>
<durmod type="number">0</durmod>
<durmult type="number">1</durmult>
<durstat type="string">cl</durstat>
<durunit type="string">min</durunit>
<label type="string">Summon Mephit</label>
<order type="number">1</order>
<targeting type="string">self</targeting>
<type type="string">effect</type>
</id-00001>
</actions>