Pathfinder Creature Parser V2

[Milke]

I certainly do get use out of it. And you're always on here giving pointers. I never really considered trying online gaming 'til I saw FG. And this parser makes what would've been the daunting task of loading all these monsters a snap.
The only thing I can think of I can't figure out is if there is a way for the creatures to not be permanently "locked" when they appear in FG.

[Blahness98]

They are locked because they are in a library module. Drag the links from the library module into your campaign's NPC listing and you will be able to edit them, change tokens and do whatever else you wanted to do with them at your leisure.

[Milke]

Just saw this. You're right. Thank you so much.
It's like having a hive mind!

[Blackfoot]

Here's one I haven't come across before...
I have a stat block with advancement and level adjustment listed... but the parser seems to be confused by them even though the PF character sheet does have places for these values. Where in the stat block are they supposed to go? By default they were after treasure in the AP and that didn't work (dumped it into treasure) I tried moving it up above ecology but that dumped it into SQ.
Where is the right place for this stuff?

Advancement 23–28 HD (Gargantuan); 29–39 HD (Colossal)
Level Adjustment —

[Trenloe]

Here's one I haven't come across before...
I have a stat block with advancement and level adjustment listed... but the parser seems to be confused by them even though the PF character sheet does have places for these values. Where in the stat block are they supposed to go? By default they were after treasure in the AP and that didn't work (dumped it into treasure) I tried moving it up above ecology but that dumped it into SQ.
Where is the right place for this stuff?

Advancement 23–28 HD (Gargantuan); 29–39 HD (Colossal)
Level Adjustment —

The Paizo statblock standard doesn't include advancement or level adjustment: https://paizo.com/pathfinderRPG/prd/...roduction.html

Which AP did you see this in? And for which creature/s?

[Blackfoot]

Its in some of the creatures in the 6th book of Legacy of Fire. I'm really not making use of this information, I was just wondering what the proper format is for handling it. I think it's a remnant from 3.5... I can't really see it in use in PF anywhere. (I was trying to find the position in the statblock so I did some searching)
The creatures that use it are mostly the big monsters in the bestiary at the end.

I really was just A: trying to figure out if it was implemented or not.. and B: letting you know that if it wasn't implemented.. that ..well.. it wasn't implemented.

[Trenloe]

Ah, OK - it's a 3.5E thing, detailed here: https://www.d20srd.org/srd/monsters/intro.htm

Hence why it's not implemented in the Pathfinder parser, as it isn't a part of the Paizo statblock standard: https://paizo.com/pathfinderRPG/prd/...roduction.html

[Milke]

Yea. The first four Pathfinder Adventure Paths were for v3.5 D&D rules. Then the 5th one, Council of Thieves, was the first one produced with the then-new Pathfinder RPG rules. So anything taken from the original Rise of the Runelords printing, Curse of the Crimson Throne, Second Darkness, or Legacy of Fire will have some slight variations from the PFRPG stat blocks (though they are very similar).

[Nylanfs]

Speaking from a PCGen point of view, there are multiple Paizo statblocks.

[swest]

So, getting closer all the time to restarting my PFRPG campaign (I think our final Deadlands session will be tomorrow night)... so I am continuing my quest to be better prepared. I actually thought that, with enough time and energy, I could become completely fluent in all-things-Fantasy-Grounds (from the user interface, of course, not the internals, although it's hard to tell where that boundary is sometimes). Boy was that a pipe dream!

So, anyway, I am back to refreshing my understanding and use of the 'PF FG Parser', now at version 2.0.0.8 (!). I went through this entire thread, bringing myself up-to-date. And, then, I decided to jump in and parse all the RotRL Skinsaw Murders NPCs (I actually have them in the material that Stargrove supplied me for my campaign, but I'm bent on putting my own mark on Chapter 2's module, and so I am re-working some of it... anyway, a big Thank You! to Stargrove for that material).

All the NPCs parsed out quite nicely with v.2.0.0.8... no real problems (of course I had to re-learn the stat-block foibles in Paizo's own material, but, I remembered most of that from the last time I did this.)


Now to my question. As I said, I have read through all 30 pages, and I still am unclear on the fundamental problem(s) presented by the, apparently, ever-problematic "Spell-Like Abilities"

Two of my NPCs have some problems in that area. I will ask about one of them... the Justice Ironbriar NPC. Again, everything else (including his Spells) about that NPC parses out nicely. However, this section:

.
.
Spell-Like Abilities (CL 6th; concentration +8)
5/day—copycat (6 rounds), dazing touch
.
.

produces the following output in the logging window:

Reading data file: C:\Users\swest\Desktop\PFRPG Creature Parser tmp\justice_ironbriar.txt
Logging to: C:\Users\swest\Desktop\PFRPG Creature Parser tmp\justice_ironbriar.txt.log
Formatting creature stat block: JUSTICE IRONBRIAR CR 7
Processing creature: JUSTICE IRONBRIAR
Cannot find spell XML element with name <copycat> cannot parse this spell - skipping.
Cannot find spell XML element with name <dazingtouch> cannot parse this spell - skipping.
Written definition.xml and db.xml to : C:\Users\swest\Desktop\PFRPG Creature Parser tmp\justice_ironbriar
Module file created: C:\Users\swest\Desktop\PFRPG Creature Parser tmp\justice_ironbriar.mod
Module file copied to : C:\Users\swest\AppData\Roaming\Fantasy Grounds\modules\justice_ironbriar.mod
Parsing ended - check text above for errors.

Is the bottom line here that this is something I can do nothing about? i.e., it's just the way it is? I'd really like for that to work, because I'm almost sure to mess it up by doing it manually.

If the answer is spelled out somewhere in the thread, I'm sorry... I just couldn't put it all together to answer it for myself... sorry.

Thanks.

- s.west