|
Senior Member
Join Date: Oct 2010
Location: Cincinnati, OH
Posts: 328
|
I have a flaw that removes Darkvision and replaces it with Low-light.
Code:
First 510 perform hero.childfound[raDarkVis].delete[Helper.ShowSpec] perform hero.childfound[raDarkVis].assign[Helper.SpcDisable] perform hero.delete[thingid.raDarkVis] Doesn't work either if (hero.picklives[raDarkVis] <> 0) then hero.child[raDarkVis].field[abValue].value = 0 ~Makes it so deepsight isn't a valid feat. endif How do I actually remove it so that feats requiring Darkvision don't validate? I see the alternate racial abilities uses RaReplace, but I can't get it to work. edit: tried perform hero.childfound[raDarkVis].delete[HasAbility.raDarkVis], which makes it so character doesn't qualify for flaw. Code:
#hasability[raDarkVis] <= @ispick and Code:
#hasability[raDarkVis] <> 0 As I said, perform hero.childfound[raDarkVis].delete[HasAbility.raDarkVis] makes the flaw invalid. Also I just bootstrapped Low-Light vision, but I wouldn't mind an example of how to assign it in code either if anyone knows. Cuz Code:
perform hero.assign[HasAbility.raLowLight] Last edited by Pezmerga; February 10th, 2012 at 08:36 AM. |
#1 |
Senior Member
Join Date: Oct 2010
Location: Cincinnati, OH
Posts: 328
|
I used
Code:
validif (hero.picklives[raDarkVis] <> 0) Code:
First 510 if (hero.picklives[raDarkVis] <> 0) then perform hero.childfound[raDarkVis].delete[Helper.ShowSpec] perform hero.childfound[raDarkVis].assign[Helper.SpcDisable] perform hero.childfound[raDarkVis].delete[HasAbility.raDarkVis] hero.child[raDarkVis].field[abValue].value = 0 endif Now I just hope someone can tell me how to add something like Low-Light vision in an eval script. Just thought it'd be good to know. Last edited by Pezmerga; February 10th, 2012 at 09:02 AM. |
#2 |
Junior Member
Join Date: Mar 2019
Posts: 12
|
Quote:
|
|
#3 |
Member
Join Date: May 2021
Posts: 84
|
You can't add picks from an eval script, only from UI elements like tables and actions.
The suggested way to add optional picks associated with another pick is to bootstrap all the optional picks so that they are always added with the original pick, and just change whether or not they are live using bootstrap conditions. Hero Lab Scripting 401: Bootstrap Conditions http://forums.wolflair.com/showthread.php?t=47611 |
#4 |
Spy
Join Date: Jan 2011
Location: Van Nuys, California
Posts: 1,220
|
At least in the d20 files, having a value of 0 in the Value field of a special ability turns it off. So in the case above, if you just set the darkvision abValue to 0, I think that will turn it off. If something later comes along and adds something to abValue (such as from a magic item), it should then reappear. At least that is how it works in the d20 files with the Value field. Someone can correct me if I'm wrong regarding PF files.
|
#5 |
|
|