• 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

Bootstrap within if statement.

BoomerET

Well-known member
I have a thing (Fighter class).

When the user selects the fighter class, a few items are bootstrapped, but there's a couple that I don't want on the class until they reach a certain level.

Code:
<eval value="1" phase="PreTraits" priority="5000">
   <before name="Calc trtFinal"/>
   <![CDATA[
      herofield[acCashNet].value = 24000
      herofield[acHPMax].value = 10
      #traitprisec[attrStr] = 1
      if (hero.child[resLevel].field[resMax].value >= 4) then
         perform assign[ClassAbil.abComDom]
         perform forward[ClassAbil.abExtAtt]
      elseif (hero.child[resLevel].field[resMax].value >= 10) then
         perform assign[ClassAbil.abExtAtt]
         perform forward[ClassAbil.abExtAtt]
      endif
   ]]>
</eval>

Doing this, I can then see Class.abComDom in the list of tags, but it doesn't appear in the list of abilities (populated on another tab, which does show the original bootstrapped items.

I also find it strange that I have to assign it, then forward.

Truthfully, I have limited understanding of the perform assign/forward commands.

Hope this make some sense, it's driving me crazy.


BoomerET
 
d20/pathfinder handles their class abilities by having them always be present, but each one has a tag to record what level it comes active at - each one checks the class it was added to, and if that tag's value is > the class' currently level, the ability disables and hides itself.
 
Last edited:
d20/pathfinder handles their class abilities by having them always be present, but each one has a tag to record what level it comes active at - each one checks the class it was added to, and if that tag's value is > the class' currently level, the ability disables and hides itself.

So are you saying the abilities are enmassed to the hero and only activated if the right tags are present along with the level requirement?
 
So are you saying the abilities are enmassed to the hero and only activated if the right tags are present along with the level requirement?

No, they're bootstrapped by the class, not enmassed, and then only activated if the right tags are present.
 
Back
Top