Skeleton Stats don't match Bestiary

[Dragnmoon]

I noticed when I import the Human Skeleton that the stats don't fully match the Bestiary ones, Is this an issue with Hero Labs or just me? Specifically the the base attack which makes all the weapon attacks wrong. Also his full attack with Scimitar is Scimitar + Claw which I can't seem to input in.

 

[Mathias]

Please be more specific about what's different.

 

[Sendric]

It appears that the Human Skeleton (same with the Bloody and Burning Skeletons) have a -4 Base attack bonus when they are imported. If you create a new hero, make it human and add the Skeleton Template, this issue doesn't happen.

 

[Mathias]

The fix is to add an Armor Proficiency (Light) adjustment on the Adjust tab. The skeleton template removes all the feats the base creature had, but doesn't say to add back in armor or weapon proficiencies.

However, the statblock in the Bestiary lists it as using a Scimitar and Chain Shirt, so by the Undead Type (Bestiary pg. 310), it's supposed to be proficient with simple weapons and whatever armor it's described as wearing (which still doesn't fix the fact that a Scimitar is a martial weapon).

Without armor proficiency, the armor check penalty of armor is applied to the attack bonus - and this chain shirt is broken, which makes its armor check penalty -4.

So, this sort of wierdness, where the author can't agree with themself, is what the adjust tab is for. I just hadn't applied the armor proficiency adjustment along with the weapon proficiency adjustment, and I'll fix that in the next update.

 

[Dragnmoon]

So, this sort of wierdness, where the author can't agree with themself, is what the adjust tab is for. I just hadn't applied the armor proficiency adjustment along with the weapon proficiency adjustment, and I'll fix that in the next update.

Thanks!

What about Fixing it so It Shows the full attack with the Scimitar. The Full attack with the Scimitar is Scimitar + Claw, which is not a choice in attacks on herolabs, you just have Scimitar or 2 claws.

 

[Mathias]

That's an large amount of work to accomplish, compared to the ease with which a human can figure out that one of the claws is being used to hold the scimitar. It's not currently worth the effort, but it's a project I have been keeping it in mind for a while as something I ought to do.

 

[Dragnmoon]

That's an large amount of work to accomplish, compared to the ease with which a human can figure out that one of the claws is being used to hold the scimitar. It's not currently worth the effort, but it's a project I have been keeping it in mind for a while as something I ought to do.

To tell the Truth, Since I spent the Money Just for the purpose of having matching stats in the bestiary, to me it is worth it the effort.

If your product can't support it, that should be mentioned before I buy the extra Data Set.

This is not the only problem I have had, and the lack of meeting expectations is starting to upset me. If you pretty much where not the only game in town, and my preferred program was no longer being supported, I would have never gotten this program.

I know Programming takes time, but certain things should be known upfront so we can go in with the prober expectations. Your APG is a good example, I knew upfront it was not complete so I came in prepared for that, but the bestiary on the other hand is complete but as my example above shows, it is not.

 

[Sendric]

You are allowed to test the product before purchasing any licenses beforehand. If you had done that, you would see what features are and aren't supported.

 

[Dragnmoon]

You are allowed to test the product before purchasing any licenses beforehand. If you had done that, you would see what features are and aren't supported.

The bestiary is an extra dataset, So no, I could not have tested it...