• 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

Attribute modifier up for some down for others

frumple

Well-known member
I have been banging my head on this one.

I have an insanity mechanism that applies a penalty to Wisdom for skills, saves, and checks, but for any other abilities that use Wisdom it is a bonus (so it is new WIS = old WIS +/- insanity points [IP]).

Currently I have it implemented as a penalty to aPostMod in aWIS (since this is an insanity mechanism I want their wisdom to be displayed as Old Wis/New Wis in the attributes tab). Now I need to be able to select all abilities that use Wisdom that aren't skills, saves, and checks and give them the bonus (which will be 2*IP to remove the penalty in aPostMod. I don't think a simple adding the bonus to everything from a foreach will work since abilities put their calculated abilities in different fields and at different phases/timings.

Ideally, I think the solution would be to modify the #attrvalue and the #attrmod macros (maybe with a tag that tells the macro to make the value it returns negative or not?), but that is not something us users can do.

Ideas?
 
First sorry don't have any good ideas.

Ideally, I think the solution would be to modify the #attrvalue and the #attrmod macros (maybe with a tag that tells the macro to make the value it returns negative or not?), but that is not something us users can do.
Just an FYI that this would not even help as a macro from my understanding is pretty much a simple single line script. It can't do any type of "logic". :(

You would need a Procedure that was called everywhere or a new field on the Attribute component to hold this new 'negative value'.
 
Hmmm.... maybe a "hidden" attribute that holds the boosted score. Then I could use the standard ability score replacement tags. Got to play a bit with the raw XML to see if it will work...
 
Back
Top