From: SourceForge.net <no...@so...> - 2010-07-17 12:41:46
|
Feature Requests item #832758, was opened at 2003-10-29 19:00 Message generated for change (Comment added) made by papa_drb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384722&aid=832758&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: Feat Support Group: Unscheduled >Status: Deleted Resolution: None Priority: 1 Private: No Submitted By: Jayme Cox (jaymecox) Assigned to: Nobody/Anonymous (nobody) Summary: VFEAT support for PRExxx tags Initial Comment: VFEAT: tag needs to support PRExxx tags Question is, how do we notify the user that they don't need the PRExxx tags for a feat? BTW, the code to allow VFEAT: in any file is done and it will support the PRExxx syntax However, I still havn't written the code to check the PRExxx yet. ---------------------------------------------------------------------- >Comment By: David R. Bender (papa_drb) Date: 2010-07-17 08:41 Message: http://jira.pcgen.org/browse/NEWTAG-184 ---------------------------------------------------------------------- Comment By: Tom Parker (thpr) Date: 2008-07-29 22:30 Message: Logged In: YES user_id=1037926 Originator: NO This adds an entirely new "Nature" behavior, which is out of scope of PCGen currently ---------------------------------------------------------------------- Comment By: LegacyKing (amaitland) Date: 2007-09-24 05:54 Message: Logged In: YES user_id=1286039 Originator: NO Isn't the purpose of VFEAT to bypass the PRExxx found normally in the feat? If the desired behavior is to only get VFEAT on certain feats, you use ADD:VFEAT|choice1,choice2,choice3, example of this in use is the Monk class. I don't think we need VFEAT to honor certain PRExxx. It defeats the point. We have plenty of ways to limit VFEAT. Comments from others? ---------------------------------------------------------------------- Comment By: Martijn Verburg (karianna) Date: 2006-08-14 09:17 Message: Logged In: YES user_id=252169 Yo Eric, comment please! ---------------------------------------------------------------------- Comment By: Andrew McDougall (tir-gwaith) Date: 2005-09-15 06:40 Message: Logged In: YES user_id=208239 This defeats the point of VFEAT. I'm not sure what is wanted here. Eric? ---------------------------------------------------------------------- Comment By: Martijn Verburg (karianna) Date: 2005-09-14 11:15 Message: Logged In: YES user_id=252169 Tir, do we need this? - K ---------------------------------------------------------------------- Comment By: Eric Beaudoin (ericbeaudoin) Date: 2003-12-26 02:09 Message: Logged In: YES user_id=324612 OK, VFEAT by default allow any FEAT, even the ones that the PC doesn't qualify for. I think that the syntax VFEAT:<feat list>|<prereq> is already there. We need to add an optional parameter that tell if only the qualified feat should be added. The House Rules section of the preferences use FEATPRE for Bypass Feat Pre-requisit. Maybe we could use FEATPRE=<YES/NO> as the optional parameter? The default value has to be YES for backward compatibility. Some examples: VFEAT:TYPE.Fighter VFEAT:FEATPRE=YES|TYPE.Fighter add all the Fighter feats as virtual feats. VFEAT:FEATPRE=NO|TYPE.Fighter add only the Fighter Feats for which the PC qualify. Assinging to Doug for comment. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384722&aid=832758&group_id=25576 |