[Pcgen-trackers] [ pcgen-Feature Requests-942075 ] Disengage CHOOSE tag from MULT:YES

[SourceForge.net <no...@so...>]

Feature Requests item #942075, was opened at 2004-04-25 22:34
Message generated for change (Comment added) made by tir-gwaith
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=384722&aid=942075&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: BONUS/CHOOSE/DEFINE tags
Group: None
>Status: Deleted
>Resolution: Rejected
Priority: 6
Submitted By: Jenni Merrifield (strawberryjamm)
>Assigned to: Nobody/Anonymous (nobody)
Summary: Disengage CHOOSE tag from MULT:YES

Initial Comment:
Currently, one must specify MULT:YES in order for the 
CHOOSE tag to work in the context of a feat.

This is just weird. What on earth does having a choice 
have to do with being able to select a feat multiple 
times?  It is not difficult to conceive of a feat that a 
character may only be able to take once, but where he 
must also make some kind of choice when that feat is 
taken.

MULT:YES and CHOOSE should not be tied together in 
this way.  Hence this feature request to have them 
disengaged from one another.

----------------------------------------------------------------------

>Comment By: Andrew McDougall (tir-gwaith)
Date: 2005-09-29 05:40

Message:
Logged In: YES 
user_id=208239

Yes, taht is a fundamental change to how feats are stored, 
esp. for Toughness.

CHOOSE is too fragile at this time to go mucking up with this.

Let's give the code team a chance to clean up the 
undercarriage, then when we overhaul CHOOSE into a stable 
system, we will discuss this type of functionality as part of 
that spec.

----------------------------------------------------------------------

Comment By: Jenni Merrifield (strawberryjamm)
Date: 2005-07-28 08:56

Message:
Logged In: YES 
user_id=931361

An added benefit is that using the CHOOSE tag with feats 
becomes less prone to error.  

You also shouldn't need to change anything about how the 
objects are stored:
  
1) Leave MULT as is.  Primarily for feats, like Toughness, that 
have no choices but can be taken more than once.

2) Change the parsing process so that when a CHOOSE is 
encountered as part of a feat definition the (mandatory) 
MULT:YES is *assumed* to be present, even if it isn't.  Any 
explicit MULT entry on the line can be ignored (since MULT:YES 
is assumed and MULT:NO is illegal)

End effects:
* No change required to how feat objects are stored
* Old feats with both tags will not be broken
* Data monkeys will no long encounter errors with feats that 
specify CHOOSE without specifying MULT:YES


----------------------------------------------------------------------

Comment By: Andrew McDougall (tir-gwaith)
Date: 2005-07-25 18:22

Message:
Logged In: YES 
user_id=208239

You are talking about fundamentally changing how the objects
are stored.  That is a huge change, and not exactly one I'd
like to really see, without a great reason to (as in, added
benefit), and less complications on the other end.

----------------------------------------------------------------------

Comment By: Jenni Merrifield (strawberryjamm)
Date: 2005-07-25 13:57

Message:
Logged In: YES 
user_id=931361

  No one has touched this FREQ since December 2004 and no 
one has commented on it since it was created in June 2004.

  Is there any chance someone might take a look and see if it 
could be implemented in the 5.10 / 6.0 timeframe?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=384722&aid=942075&group_id=25576