• 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

Beastmorph Mutagen adjustment help

H

Hirsute

Active member
Hey all,

I'm trying to put in an adjustment that will add Pounce to my beastmorph alchemist when a mutagen is consumed.

Copying the Racial ability, Darkvision adjustment, I created the adjustment, took off the counter because this one doesn't need it, and bootstrapped raPounce to it.

I added the following condition to the bootstrap:
fieldval:pIsOn <> 0

And added the following evaluation script to the adjustment:
~ If we're not enabled, get out now
doneif (field[pIsOn].value = 0)

Now, when I add the adjustment to the hero, Pounce (Ex) is listed as I'd expect, but when I disable (without removing) the adjustment, Pounce (Ex) remains, unlike the Racial ability, Darkvision adjustment I looked at here.

How do I make it so that when the adjustment is disabled, Pounce disappears from the character?

edit:
I changed the subtype from Special Abilities to Race Modifications and now it works as I'd expect. Not exactly sure why this made a difference, but leaving this here for posterity.
 
Last edited:
Did you just use Test Now! on this adjustment, or did you quick reload the data files? Test Now can't apply bootstrap conditions - it leaves them as condition-less bootstraps.
 
Mathias: Ultimately, at this point, I'm unsure. My general routine is "Test Now". If that works, I tell it to compile the file, save it, and close the editor, then add (or remove and re-add in the case of something that wasn't working as expected) the ability to character to see if it's functioning in action like I expect it to.

It is possible that I used "Test Now" and got distracted and did not recompile before saving the .user file and exiting the editor.
 
Hirsute said:
Mathias: Ultimately, at this point, I'm unsure. My general routine is "Test Now". If that works, I tell it to compile the file, save it, and close the editor, then add (or remove and re-add in the case of something that wasn't working as expected) the ability to character to see if it's functioning in action like I expect it to.

It is possible that I used "Test Now" and got distracted and did not recompile before saving the .user file and exiting the editor.
Click to expand...
You can save time by just using "CTRL-R" to do a quick reload. No need to close down the editor or anything. :)
 
You must log in or register to reply here.
Back
Top