• 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

Questions about PowerMods.??? tags

TCArknight

Well-known member
Ok, I'm playing around with this to find the best way to deal with Mega Modifiers for Savage Rifts... :)

20. OK, big one: I've added Arcane Power Modifiers as a complete tag set, tagged up the spells, and created a powModifiers field and populated it with a dynamic list of the Modifier names.

I have no problem adding a new PowerMods.? tag as long as I add it before Setup/2000 when the field[powModifiers] is populated.

The one thing I can do is this:
~ add Mega Modifier to PsionicArcane Protection
var adddesc as string
foreach pick in hero from Power where "thingid.powArcaneProtect & Arcane.arcPsionicSWADE"
perform eachpick.assign[PowerMods.2ExaltedArcPro]

adddesc = "{br}{br}{b}MEGA MODIFIERS{/b}{br}{indent -10} • EXALTED ARCANE PROTECTION (+2): Hostile powers suffer a −4 penalty (–6 with a raise)."

perform state.thing[powArcaneProtect].amendthing[description,state.thing[powArcaneProtect].field[descript].text & adddesc]

nexteach
Doing it this way however, makes all versions of the Arcane Protection power show the Mega Modifier, even those selected through the Magic Arcane Background.

Is there a better way to handle this?

Would it maybe be possible to add a field to the powers where additions to the description could be stored and the normal mouseover/descript procedure automagically append the two together?
 
When you do the second perform (perform state.thing), I think you need to include the eachpick.
No luck. I get:
Hero Lab was forced to stop compilation after the following errors were detected:

Syntax error in 'eval' script for Thing 'racSRAAltara' (Eval Script '#1') on line 9
-> Script reference is invalid under the circumstances
That line 9 is eachpick.amendthing[...]

I found a thread I had about amendthing: https://forums.wolflair.com/showthread.php?t=55973&highlight=amendthing

In it, Mathias mentions that amendthing isn't available for pick, just the overall thing and that best way to handle (similar to this situation) would be to have an additional field, that if it wasn't empty would get appended to the description field in the mouseinfo procedure..
 
Back
Top