[Pcgen-team-code] [JIRA] Updated: (CODE-1095) Template tag ADDLEVEL not being applied when a template is applied from within a Race object.

[JIRA (f. J. D. ) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/CODE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Dempsey updated CODE-1095:
--------------------------------

    Status: Confirmed  (was: Open)

Confirmed with PFRPG black dragons of various ages. Weirdly I can see the class being added in the code but it doesn't seem to stick.

> Template tag ADDLEVEL not being applied when a template is applied from within a Race object.
> ---------------------------------------------------------------------------------------------
>
>                 Key: CODE-1095
>                 URL: http://jira.pcgen.org/browse/CODE-1095
>             Project: Code
>          Issue Type: Bug
>    Affects Versions: 5.17.3 (Alpha) , 5.17.4 (Alpha) , 5.17.5, 5.17.6, 5.17.7, 5.17.8
>            Reporter: Eric C. Smith
>            Assignee: Stefan Radermacher
>
> The Template tag ADDLEVEL tag is not being applied when the template is called from within a Race object.
> Symptom:
> 1) Load Pathfinder Core Rules and Bestiary.
> 2) Create new character and apply any Ancient Dragon kit. -> An error pops up telling you there are not enough skill point/Feat slots available.
> 3) Abort kit. Note that the Summary tab show 4 Dragon HD.
> 4) Quit PCGen and edit pbf_templates_dragons.lst in the bestiary_core folder to make any Great Wyrm template VISIBLE:YES and save.
> 5) Relaunch PCGen and load the Pathfinder Core Rules and Bestiary
> 6) Create new character, select an alignment and add the the Great Wyrm race for which you modified the template. Note that Summary tab shows 4 Dragon HD.
> 7) Switch to the Template subtab and remove the Great Wyrm template and then reapply it. This may require the moving away from the Race/Template tab and then returning.
> 8) The Summary tab should now display a number of Dragon HD appropriate for the Great Wyrm desired.
> I have verified this issue exist back to 5.17.3 but do not have any earlier dev versions to check. Note that 5.16.4 does not have this problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira