• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Poison attacks and custom output (bug?)

grotberg

New member
Hi all,

I'm using Hero Lab primarily for DMing, and I end up using a homemade custom output to print statblocks on index cards for easy management during the game.

The one hiccup that I've run in to is with poison attacks. There are many, many different kinds of poison effects in the bestiary, and this information appears to be in the hero lab bestiaries, but the only data actually sent to the .XML for the custom output appears to be the fact that there is a poison attack, but not any of the details.

For example, take the Tatzylwyrm (Bestiary 3). In hero lab, it gives you the following text on the "Specials" tab:
Poison: Breath - Inhaled (DC 12) (Ex) (Tatzylwyrm)
Poison deals 1d2 STR damage, 1/round for 2 rds, cure 1 save.

But when you custom output the XML file and check out the entry for that special, you only get the following information:
HTML:
<special name="Poison: Breath - Inhaled (DC 12) (Ex)" type="Extraordinary Ability" sourcetext="Tatzlwyrm" shortname="Poison: Breath - Inhaled (DC 12)">
     <description>You have a poison attack.</description>
     <specsource>Tatzlwyrm</specsource>
</special>

It seems like the wrong bit of text is getting sent to the XML in the description section, as "You have a poison attack" is redundant at that point, and what you really need are the actual details of the poison effect.

Am I going crazy and missing something obvious? Is this just a bug? Any easy fix?

Am I even posting this in the right place?

Cheers,
-G
 
I see that you've already posted this in our bug reporting system. That was the correct place to report it.
 
Back
Top