Senior Member
Join Date: Nov 2011
Location: South Riding, VA
Posts: 841
|
When testing a tag expression for a bootstrap condition does that tag always need to be on the hero? Is there a way to force the context to look at the thing that is bootstrapping the 2nd thing?
For example, I have a thing (lets call it Thing1) that selects from a group of things with a tag group XXXX.? and pulls the appropriate XXXX.? tag from the selector to it. On Thing1 I am bootstrapping another thing (let's call it Thing2) with the bootstrap condition "XXXX.YYYY" at a timing after the XXXX.? tags are pulled onto Thing1. However, the only way the bootstrap condition seems to work is if I then push the pulled XXXX tag onto the hero. Is there a way to force the bootstrap condition to look for the XXXX tag on Thing1 instead? |
#1 |
Senior Member
Join Date: Feb 2015
Posts: 676
|
If there's a way to do this, I haven't found it. What I sometimes do instead is use an abValue field as a flag, by having a script that checks the pick for whatever tag and then sets the field to 1 if present. The bootstrap condition can then be "fieldval:abValue = 1" or suchlike.
EDIT: Though, now that I think about it, I haven't done that much lately. More often I'll either just go ahead and forward the tag, or make a new one to apply to the hero (depending on whether the original tag would seem out-of-place on the hero). That's probably CPU-cheaper than my numeric-flag hack anyway. Last edited by TheIronGolem; July 25th, 2016 at 09:15 AM. |
#2 |
Senior Member
Join Date: Nov 2011
Location: South Riding, VA
Posts: 841
|
Yeah that is what I do sometimes as well. It just seems if we could limit the scope to the thing bootstrapping us it would allow folks to reuse tags without having to worry about accidentally bootstrapping something they do not mean to.
|
#3 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729
|
Keep in mind its not actually the "hero" being checked it is the container being checked. Most of the time that is the hero but I think its Gizmo's where you end up checking the Gizmo not the hero. Unless you added the hero# part in front of the tag.
Using the fieldval is also what I do to get around checking the Pick instead of the container. Hero Lab Resources: Pathfinder - d20pfsrd and Pathfinder Pack Setup 3.5 D&D (d20) - Community Server Setup 5E D&D - Community Server Setup Hero Lab Help - Hero Lab FAQ, Editor Tutorials and Videos, Editor & Scripting Resources. Created by the community for the community - Realm Works kickstarter backer (Alpha Wolf) and Beta tester.- d20 HL package volunteer editor. |
#4 |
Senior Member
Join Date: Nov 2011
Location: South Riding, VA
Posts: 841
|
Makes me with for a "pick#"
|
#5 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729
|
Totally agree. I know we all go to Gen Con and stand in front of Colen and tell him he "has" to add this feature. Or Else!!!
Hero Lab Resources: Pathfinder - d20pfsrd and Pathfinder Pack Setup 3.5 D&D (d20) - Community Server Setup 5E D&D - Community Server Setup Hero Lab Help - Hero Lab FAQ, Editor Tutorials and Videos, Editor & Scripting Resources. Created by the community for the community - Realm Works kickstarter backer (Alpha Wolf) and Beta tester.- d20 HL package volunteer editor. |
#6 |
Senior Member
Join Date: Feb 2015
Posts: 676
|
|
#7 |
Senior Member
Join Date: Nov 2011
Location: South Riding, VA
Posts: 841
|
My guess it is not a simple addition though. Since it is checking the container and picks are not a container. :/
|
#8 |
|
|