toggle quoted messageShow quoted text
The solution is simple. No PREVAR, but a hard
PREABILITY:1,CATEGORY=blah,Name of Ability Or TYPE with uniqueID
Easy peasy. You choose whether KEY or TYPE is your method so you
aren't checking for 2 things to keep it clean, but that's the
On 5/10/2019 7:37 AM, markjmeans wrote:
I’m not truing to modify any feats or
talents, that was just an example. There is a situation in PFS
that would benefit from an ordered list, but rather than
getting bogged down in unimportant details, I asked in a more
generic way. Plus a generic solution could be useful if any
other situation arises that could benefit from an
implementation of an ordered list.
<firstname.lastname@example.org> On Behalf Of mike55young@...
Sent: Friday, May 10, 2019 00:26
To: Andrew Maitland <drew0500@...>;
Subject: Re: [pcgen] DATA question
Sounds like he is trying to do dependencies
in talents (or possibly in feats) a bit more efficiently? Only
thing is that this idea assumes a single dependency which
isn't always the case.