Problems with bootstrapping template with Condition

[Lawful_g]

I'm encountering an issue. My bootstrap condition seems to be working the opposite of how I would expect it to, and that is confusing me.

Here is what I want to do, if the feat's checkbox is active on the in play tab, and if we are not a natural lycanthrope, then forward a custom tag to the hero. If the custom tag is on the hero, bootstrap the afflicted lycanthrope template, otherwise add bonuses to our stats.

Here are the codes I am using:

First 500
~ If our related feat is not active, stop now.
doneif (hero.childfound[fFeatname].field[abilActive].value = 0)

~ If we have no Natural Werewolf template, forward a tag to the hero that says it is ok to bootstrap the Afflicted Werewolf template.
if (hero.picklives[tmLyWolfN] = 0) then
perform hero.assign[Custom.LycAfflict]
endif


Pre Attributes 10000
~ If we do not have the custom tag but the feat is active, then we were already a natural lycanthrope and should boost our stats.
if (hero.childfound[fFeatname].field[abilActive].value <> 0) then
if (hero.tagis[Custom.LycAfflict] = 0) then
hero.child[aSTR].field[aNormMod].value += 2
hero.child[aCON].field[aNormMod].value += 2
endif
endif

The Afflicted Werewolf template is being bootstrapped with the following condition:
First 500
count:Custom.LycAfflict <> 0

Now, the code seems to be working, the Custom tag is being forwarded to the hero when the ability is active, but it seems to be having the opposite effect, and not bootstrapping the template when the tag is present. Instead, the template starts bootstrapped, and when you check the box to make the feat active, it disappears.

As I understand it, once the condition is true, the bootstrap should go through, which is why "count:Classes.Whatever >= X" works for bootstrapping things based on more than X class levels. Is that incorrect? If I reverse the Bootstrap condition to "count:Custom.LycAfflict = 0" then it seems to work correctly...

HAVE I GONE MAAAD!?!?

[Mathias]

Aren't you assigning the tag and then checking for it, both at First/500? Won't it be random whether or not the tag generation script runs before the tag testing condition?

Bootstrap conditions are looking at the tags on the pick doing the bootstrapping, rather than the hero (that's why fieldval:abilActive <> 0 - looking at the abilActive field of the thing doing the bootstrapping, works)

hero#Custom.LycAfflict <> 0

should work to test the hero's tags instead. I'm not sure why you're getting the reverse of what you expect though - both of the things I noted should produce wierd or non-functional results, not reversed results.

[Lawful_g]

I had a typo on the first script, it was running at First 450 actually, so that wasn't the problem...

I used "hero#Custom.LycAfflict <> 0" as my bootstrap condition but I seem to still be getting opposites of what I expect. Possibly a similar issue cropped up in another racial custom ability... I have been getting some timing errors from other pathfinder files in my folder. I am going to try isolating only the things I am working on to eliminate the timing error and see if things work as expected then.

[Lawful_g]

The other racial custom ability works fine, no problem.

The first one is still backwards and I don't know why, but I flipped the bootstrap condition to "hero#Custom.LycAfflict = 0"and it works, so I guess I'll just remain puzzled.

Now I have another problem on further testing. When the Natural Werewolf template is present, the afflicted template is always bootstrapped, regardless of whether the feat's abilActive is checked or not.