[Pcgen-trackers_code] [JIRA] Created: (CODE-663) ADD:FEAT ADD:ABILITY ignore SELECT

[JIRA (f. D. R. B. ) <ji...@pc...>]

ADD:FEAT ADD:ABILITY ignore SELECT
----------------------------------

                 Key: CODE-663
                 URL: http://jira.pcgen.org/browse/CODE-663
             Project: Code
          Issue Type: Bug
          Components: Needs Verification Review
            Reporter: David R. Bender
             Fix For: 6.0.x


SF - ID: 1910541
Last Update: Settings changed ( thpr )
Details:

I'm seeing a problem with SELECT when using INT as the value. In the
MSRD
there is an advanced class called Techno Mage, if you turn off the
class
prereqs and advance a PC to level 5 there is an ADD:FEAT granting "
Arcane
Spontaneous Casting". I have this code in this hidden feat:

SELECT:INT CHOOSE:SPELLS|CLASSLIST=Techno Mage[KNOWN=YES]

If the PC's INT is 13 (+1 mod) it functions as expected the Techno Mage
knows all his 0 level spells automatically like a Wizard so this choose
presents that list.

If the PC's INT is 14 or higher (which should give him multiple spell
selections) then the pop up to select the spells never appears at all.
Submitted:

Tom Parker ( thpr ) - 2008-03-09 13:28:52 EDT
Priority:

Status:

Resolution:

Tracker:

Assigned:

 (admin)
Category:

 (admin)
Group:

 (admin)
Visibility:

Private
Response:

 (admin)
Comment:



Comments ( 11 )
Add a comment

Date: 2008-08-20 11:05:13 EDT
Sender: thprProject Admin & Donor
Hide


I would advise not using a number in ADD:FEAT as a workaround, because it
will horribly break once this issue is fixed (you'll end up with N-squared
choices)

As far as charging the feat pool or not, it's *supposed* to - it may not
right now, as a side effect of this issue. The proper behavior is
displayed in 5.12.



Date: 2008-08-20 00:34:44 EDT
Sender: amaitlandProject Admin
Hide


Yeah, after doing some testing the ADD:FEAT|x|y x overrides the SELECT
tag in the CHOOSE. So the work around for the time being is have ADD:FEAT|x
with x being your select variable.

Tom, you mentioned ADD:FEAT is charging the feat pool. I've noticed that
it isn't charging the feat pool at all, instead it is adding to the feat
pool.


Date: 2008-06-16 22:58:55 EDT
Sender: jdempseyProject Admin & Donor
Hide


Support for a single feat being added might not be too bad, but where
there are multiple feats being chosen from all of the multiple selections
would have to be in the same feat...

Deferring for 5.16 to see if a reasonable solution is doable there.


Date: 2008-04-28 22:26:23 EDT
Sender: thprProject Admin & Donor
Hide


Note that this may show signs of [ 1886541 ] CHOOSE:NUMCHOICES=/STACK not
respected across Ability Pools since it is building independent
Choosers...



Date: 2008-04-18 10:55:27 EDT
Sender: thprProject Admin & Donor
Hide


No, different issues


Date: 2008-04-18 04:23:38 EDT
Sender: kariannaSourceForge.net DonorProject Admin & DonorAccepting Donations
Hide


Moving to 5.14.1, Tom can you also look @ 1945471 and let me know if it's
a duplicate?


Date: 2008-04-17 13:27:30 EDT
Sender: thprProject Admin & Donor
Hide


I believe this is a 5.14.1 candidate - this requires gutting the entire
ADD / CHOOSE interaction, which is by no means trivial. For now, we should
document that SELECT doesn't interact well with ADD



Date: 2008-04-11 20:33:17 EDT
Sender: thprProject Admin & Donor
Hide


This is not a problem with SELECT - it is a problem with how ADD:FEAT
calls the chooser system

It is not leveraging the basic choice system, but "builds its own"
chooser... thus ignoring select.

I'm not sure this problem is tractable as presented in PCGen 5.x...
The problem is that different choices are consolidated in the ADD:FEAT
chooser. One could do:
ADD:FEAT|Dodge,Arcane Spontaneous Casting

The problem is that it expands out the choices for Arcane Spontaneous
Casting, but that means each of those choices are 1/INT cost, but Dodge is
1/1. The system is not set up to make that selection.

Due to the fact that ADD:FEAT has side effects (it charges the FEAT pool),
I'm unsure if there is a workaround for this problem.



Date: 2008-03-09 22:03:32 EDT
Sender: thprProject Admin & Donor
Hide


I believe the former (listing out the options) is the expected behavior,
based on how other ADD:FEAT items work.

The latter is a code bug, I will look into that.



Date: 2008-03-09 15:37:18 EDT
Sender: eddyanthonySourceForge.net Subscriber
Hide


Doh, I feel dumb.

OK I made the change but still see an error. Before with an INT of one I
got two popups, one to select the feat and one to select the spell. Now
with MULT:YES in place I only see one pop up with a list populated with
entries of "Arcane Spontaneous Casting(<Spell Name>)" and I'm given only 1
selection even with an INT of +2


Date: 2008-03-09 14:38:38 EDT
Sender: thprProject Admin & Donor
Hide


To use a CHOOSE, you must UNCONDITIONALLY have MULT:YES when it's an
Ability. That's in the docs

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira