NPC Builder Update

[Doublebond]

Thanks very much!

[Psion]

Alright, something seriously weird is going on with the importer.

I paste in this exact stat block:

Dire Ape (Large Beast Walker — 94 XP): Str 18, Dex 12, Con 16, Int 7, Wis 12, Cha 10; SZ L (2×2, Reach 1); Spd 40 ft. ground; Init IV; Atk VII; Def IV; Resilience V; Health VI; Comp I; Skills: Acrobatics IV, Athletics VI, Intimidate VI; Qualities: always ready, charge attack, damage reduction 1, darkvision I, feat (Iron Will), grappler, improved sense (smell), rend, superior climber III, tough I.
Attacks/Weapons: Bite II, Claw III × 2
Treasure: 2T

And a few things happen.

Dire disappears in the box and it just says ape; still says dire ape in the printed block. If I type in Dire in the box, it says "Dire Dire Ape" in the stat block.

Size in the drop-down list says small, but it says large in the stat block. I change it to large in the box, it changes to gargantuan in the stat block.

The footprint says 1 x 1 in the boxes and 4 x 4 (wrong) in the stat block, and I can't really fix it.

I start from scratch, none of this happens.

[Psion]

I think I found the problem. I put "Dire" in the name, it tries to slap on the Dire template.

[meadicus]

Yup, that's how the templating works. When it loads an NPC it assumes that if its names starts with a template, then the NPC has said template. Not sure how else to do it really. I'm open to suggestions.

[meadicus]

My current thinking is to make templates added by the NPC Builder feature in the NPC's name as, say "Dire(T)" or "Ancient(T)". That way they won't conflict with NPCs that have those words at the beginning of their name but not through template usage.

Anyone have any issues with that?

[Doublebond]

My current thinking is to make templates added by the NPC Builder feature in the NPC's name as, say "Dire(T)" or "Ancient(T)". That way they won't conflict with NPCs that have those words at the beginning of their name but not through template usage.

Anyone have any issues with that?

Sounds appropriate.

[Moebius]

Very nice program. I appreciate the web based-ness (as a Linux user and all that).

[Khaalis]

Ok, I've been I trying to add say a base creature from the book so I can do some modifications, but upon clicking ok, it just sits. It won't import. Anyone else having this issue?

[Doublebond]

Ok, I've been I trying to add say a base creature from the book so I can do some modifications, but upon clicking ok, it just sits. It won't import. Anyone else having this issue?

That happens whenever there's something unorthodox about the npc you're importing. Which NPC is it in question?

[Khaalis]

That happens whenever there's something unorthodox about the npc you're importing. Which NPC is it in question?

I see what you mean. I'm only seeing issues with certain entries. The one in particular that was giving me the biggest fit was the Nightmare. A few others but can't remember exactly which.

[mirror]

I've noticed what I think is an error in the builder.  On a FantasyCraft character when you add signature skills the cost should be the difference between the signature skill rating and the competence rating of the npc but the builder is just taking the rating as the cost.

Example: an NPC with a competence rating of II gets an Acrobatics signature skill rating of IV, the cost should be 2xp but the builder is placing the cost at 4xp.

[Antilles]

Hmm... I've always thought signature skills cost their grade in xp, but looking over the text it seems to suggest mirror's interpretation is correct. On the other hand, the examples given under signature skills  clearly use the full trait price, and a quick glance at a couple of the rogues gallery npc's seem to indicate they've been built with full trait price as well, so I guess it's a case of an unfortunately worded phrase in the book.

[meadicus]

Having just looked over the signature skills the sentence is a bit ambiguous. But the two examples which follow it clearly show the XP is increased by the full skill grade.

[meadicus]

Ok, I've been I trying to add say a base creature from the book so I can do some modifications, but upon clicking ok, it just sits. It won't import. Anyone else having this issue?

That happens whenever there's something unorthodox about the npc you're importing. Which NPC is it in question?

Thanks for answering this Doublebond

I see what you mean. I'm only seeing issues with certain entries. The one in particular that was giving me the biggest fit was the Nightmare. A few others but can't remember exactly which.

I'll have a look at the Nightmare as soon as I can. If you can find any other specific NPCs which don't work please let me know.

[meadicus]

My current thinking is to make templates added by the NPC Builder feature in the NPC's name as, say "Dire(T)" or "Ancient(T)". That way they won't conflict with NPCs that have those words at the beginning of their name but not through template usage.

This change is now in place. So if you want to edit a templated NPC you've built with the builder before, you should add "(T)" after every template name, for the npc builder to read it as a template. That should sort out the problems templating has been causing for some people.