Something like exprreq

[RavenX]

Covered early but unless you've done it a few times you might not remember it. You shouldn't need to forward the tags with hero.childlives[] in a macro. That line of code looks up the career in question to see if its on the actor. Unless you need bootstrap conditions based on the tags, forwarding a tag shouldn't be needed.

[Mathias]

I recommend tag-based exprreqs, as opposed to hero.childfound[] based exprreqs.

First, when you get into dealing with packages, where not every book may be loaded on all characters, it's easier to define the tag you need in tags.1st, in order to remove the error than it is to copy that item into a shared file.

Second, if another ability counts as this one for the purpose of prereqs, you can simply assign the same tag and the prereq will work, instead of having to rewrite the prereq to look for the other thing.

[RavenX]

Originally Posted by Mathias

I recommend tag-based exprreqs, as opposed to hero.childfound[] based exprreqs.

First, when you get into dealing with packages, where not every book may be loaded on all characters, it's easier to define the tag you need in tags.1st, in order to remove the error than it is to copy that item into a shared file.

Second, if another ability counts as this one for the purpose of prereqs, you can simply assign the same tag and the prereq will work, instead of having to rewrite the prereq to look for the other thing.

I had not considered the counts as... Tags before. I haven't had to worry about that with the files I created yet.

[AndrewD2]

I generally work with forwarding a tag to the hero and checking that pre-reqs. The only time I've ever done a childfound check for a pre-req in PF is checking for a classes custom abilities or a specific selection in an array.