Found a little bug with this, a feat with this can be selected an unlimited number of times, once the feat pool reaches 0 additional selections push the poolMessage 1 of 14 , Dec 1 10:02 PMView SourceFound a little bug with this, a feat with this can be selected an unlimited
number of times, once the feat pool reaches 0 additional selections push the
pool into negative numbers and does not prevent the feat from being added as
> Eddy Anthony scribed:--
>> [ 1371400 ] Document CHOOSE:NOCHOICE tag
> And here it is:
> *** New 5.9.4
> Tag Name: CHOOSE:NOCHOICE
> What it does:
> This CHOOSE tag will NOT produce a pop up window. This is useful in feats
> which use MULT:YES to allow them to be selected multiple times. A feat with
> this tag will simply be added to the character without a chooser window,
> after the first time it is added a (x2), (x3) etc. will be displayed
> indicating how many times the feat was chosen.
> The feat is added without a chooser window.
~ Eddy Anthony (MoSaT)
~ PCGen Content Silverback
Something to consider (minor possibility) PREFEAT:1,Toughness(+3 HP) wouldn t work after that change for someone that does what you did... Not too big aMessage 1 of 14 , Dec 1 10:47 PMView SourceSomething to consider (minor possibility) PREFEAT:1,Toughness(+3 HP)
wouldn't work after that change for someone that does what you did...
Not too big a possibility, but something to consider.... I don't think
it will effect many, if any at all...
> Closed PCGen and changed Toughness to use CHOOSE:NOCHOICEbefore
> When I reopended the PC the character still has the feat exactly as
> with the +3 HP,+3 HP next to it in the feat pane. He also has the hitjust
> points. When I remove the feat there is no chooser window the +3 HP
> goes away one at a time. When added back I get (x2) thereafter.
> So no breakage that I can see.
Hi all, ... And _this_ is the reason we need to finish off all of our existing doc bugs and freqs (We re starting to get through them, but I need moreMessage 1 of 14 , Dec 2 1:56 AMView SourceHi all,
> Ok, now we have another walkthrough of CHOOSE to implement this niceAnd _this_ is the reason we need to finish off all of our existing doc
> feature. I wonder how long that's been there....
bugs and freqs (We're starting to get through them, but I need more
volunteers) and be vigilant when we create new ones....