• 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

More than 2 activation options?

CNYGamer

Well-known member
In the Editor, you can set two different names for an activated ability:

Activation Name (which corresponds with the abilActive field)

Activation #2 Name (which corresponds with the abilAct2 field)

Is there a way to have more than two different names (abilAct3, abilAct4, etc.)?

I copied some code from the werewolf Shapechanger ability to use for the wereraven from Curse of Strahd, and it worked quite nicely. The wereraven has only two forms (not counting his natural human form, of course). I wanted to use similar code for Strahd von Zarovich, who, in addition to his true form, has three forms: bat, wolf, and mist.
 
Each ability can only have "two" activation's as its hard-coded to the UI.

So what you do is create a "General->Ability" that you bootstrap to your (you never said) Feat, Class Ability, Racial Special, etc. This bootstrapped generic Ability is where you put your logic for your additional two activation.

This is the same logic I used for some of the feats in the Community Pack because I needed to select "4" weapons but a feat can only have "two" selectors.
 
If you have the community Pack you can look at the COM_5ePack_PHB - Feats.user file for the three "Weapon Master" feats. You see one bootstraps the other two.

You can also see it HERE on github.
 
Alternately, you could set up an array with X number of options (that represent different disparate states) and use a single activation button to turn on whatever is chosen by the selector.
 
Alternately, you could set up an array with X number of options (that represent different disparate states) and use a single activation button to turn on whatever is chosen by the selector.
I see how you are. You wait until "after" I say something and then make a post. But you won't post before I saw something.

I am on to you now sir!!!! :D :eek:

P.S. - Both the above would solve the issue actually. Aaron's is nicer in that it lowers the number of activation buttons on the In-Play tab or the iPad.
 
Last edited:
Back
Top