Bugs item #1910541, was opened at 2008-03-10 04:28
Message generated for change (Settings changed) made by jdempsey
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=384719&aid=1910541&group_id=25576
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
>Group: To be fixed For 5.16.1
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Tom Parker (thpr)
Assigned to: Nobody/Anonymous (nobody)
Summary: ADD:FEAT ADD:ABILITY ignore SELECT
Initial Comment:
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.
----------------------------------------------------------------------
Comment By: Tom Parker (thpr)
Date: 2008-08-21 01:05
Message:
Logged In: YES
user_id=1037926
Originator: YES
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.
----------------------------------------------------------------------
Comment By: LegacyKing (amaitland)
Date: 2008-08-20 14:34
Message:
Logged In: YES
user_id=1286039
Originator: NO
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.
----------------------------------------------------------------------
Comment By: James Dempsey (jdempsey)
Date: 2008-06-17 12:58
Message:
Logged In: YES
user_id=558288
Originator: NO
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.
----------------------------------------------------------------------
Comment By: Tom Parker (thpr)
Date: 2008-04-29 12:26
Message:
Logged In: YES
user_id=1037926
Originator: YES
Note that this may show signs of [ 1886541 ] CHOOSE:NUMCHOICES=/STACK not
respected across Ability Pools since it is building independent
Choosers...
----------------------------------------------------------------------
Comment By: Tom Parker (thpr)
Date: 2008-04-19 00:55
Message:
Logged In: YES
user_id=1037926
Originator: YES
No, different issues
----------------------------------------------------------------------
Comment By: Martijn Verburg (karianna)
Date: 2008-04-18 18:23
Message:
Logged In: YES
user_id=252169
Originator: NO
Moving to 5.14.1, Tom can you also look @ 1945471 and let me know if it's
a duplicate?
----------------------------------------------------------------------
Comment By: Tom Parker (thpr)
Date: 2008-04-18 03:27
Message:
Logged In: YES
user_id=1037926
Originator: YES
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
----------------------------------------------------------------------
Comment By: Tom Parker (thpr)
Date: 2008-04-12 10:33
Message:
Logged In: YES
user_id=1037926
Originator: YES
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.
----------------------------------------------------------------------
Comment By: Tom Parker (thpr)
Date: 2008-03-10 13:03
Message:
Logged In: YES
user_id=1037926
Originator: YES
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.
----------------------------------------------------------------------
Comment By: Eddy Anthony (eddyanthony)
Date: 2008-03-10 06:37
Message:
Logged In: YES
user_id=886893
Originator: NO
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
----------------------------------------------------------------------
Comment By: Tom Parker (thpr)
Date: 2008-03-10 05:38
Message:
Logged In: YES
user_id=1037926
Originator: YES
To use a CHOOSE, you must UNCONDITIONALLY have MULT:YES when it's an
Ability. That's in the docs
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=384719&aid=1910541&group_id=25576
|