Menu
▾
▴
[Pcgen-trackers] [ pcgen-Feature Requests-1212315 ] LEVELS tag
|
From: SourceForge.net <no...@so...> - 2006-01-12 14:13:48
|
Feature Requests item #1212315, was opened at 2005-05-31 18:49 Message generated for change (Comment added) made by eddyanthony You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1212315&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: Race Support Group: None Status: Open Resolution: None Priority: 6 Submitted By: Eddy Anthony (eddyanthony) >Assigned to: Devon Jones (soulcatcher) Summary: LEVELS tag Initial Comment: the LEVEL and HD tags for template lines are little used and problematic. They were not designed to grant choices in feats selected and they have all kinds of issues with checking with prereqs and using the feat pool points correctly. Rather than try and rewrite these tags to be something they were not designed for lets create a new tag specificly geared to do what we need it to. I propose the LEVELS tag: Doc Entry: Tag Name: LEVELS:x,x|y Variables Used (x): Number or formula (Character levels at which the tag is applied) Variables Used (y): ADD:FEAT(v,v)v Variables Used (y): FEATAUTO:v|v Variables Used (y): TEMPLATE:v Variables Used (y): TEMPLATE:CHOOSE:v Variables Used (v): Variable belonging to the specified tag What it does: Allows specific global tags to be applied at specific character levels. LEVELS can be used multiple times in races and templates. Where it is used: in race and template lines. Example: LEVELS:1,5,10|ADD:FEAT(TYPE=Sneaky)1 The ADD:FEAT tag will be applied at character levels 1, 5 and 10 and allow a choice of TYPE Sneaky feats. LEVELS:2|TEMPLATE:Ultra Sneaky The template Ultra Sneaky is applied at 2nd level LEVELS:5|TEMPLATE:CHOOSE:Celestial|Outsider The race can choose either the "Celestial" or "Outsider" template at level 5 ======================================= Notes: Once the new Ability object has been implemented there should be two additional tags usable for LEVELS, ADD:ABILITY and ABILITYAUTO or whatever the equivalent syntax ends up being. Also there is interest in being able to control the retroactivity of this tag when used in a template. Currenty the LEVEL tag is retroactive so if you apply a template to a 10th level PC which has a LEVEL:2 tag in it that will be applied the next time the character is leveled up. The desire is that one could specify if the LEVELS tag would grant the specified object if the template was aquired after the specific level. Why allow a formula for variable x? Well there is one neat trick this would make possible, the formula (HD+1) would allow you to have a LEVELS tag in a template that would grant whatever it grants at the PC's first character class level regardless of how many hit dice or monster levels it has. This would eliminate the need for two tags. The LEVEL and HD tags are essentially the same tag only LEVEL is activated on total levels and HD is activated on monster levels. Allowing a formula would take care of this issue and provide additional capability. Originally the idea was for LEVELS to be able to apply any global tags, I'm not opposed to this but in this request I have narrowed it down to four specific tags. Here's why: these four tags provide a way to add feats and templates, one with a choice and one without. Since most any other global tags you might need can be put in a template or feat these four tags provide all the functionality we need. Limiting it to four tags means there is much less to have to trouble shoot as well, verifying that all four tags are working is much less of a task than checking all the global tags. But I'm not a programmer and if the CM's tell me it's no problem to hook up all the global tags to it hey I'll take it :-) ---------------------------------------------------------------------- >Comment By: Eddy Anthony (eddyanthony) Date: 2006-01-12 09:13 Message: Logged In: YES user_id=886893 Yes. unless the code team has any objections and wants us to rework or clarify anything then I have approved it. ---------------------------------------------------------------------- Comment By: Devon Jones (soulcatcher) Date: 2006-01-11 22:06 Message: Logged In: YES user_id=107647 why is this assigned to me - are you approving this syntax for us to implement? ---------------------------------------------------------------------- Comment By: Eddy Anthony (eddyanthony) Date: 2005-09-29 11:38 Message: Logged In: YES user_id=886893 Well that makes no sense to me, you want this tag to be able to take back the object it grants? The LEVEL tag does not do this now, VFEAT with PRExxx is the only thing I can think of that comes close. I don't think it's needed, the Ability object should have the functionality to cover the example you give with 3 possible way to implement it, either it can be coded as one ability or two abilities and the first one is hidden when the second one is added or the first one is removed by the second one when it is added. ---------------------------------------------------------------------- Comment By: Andrew McDougall (tir-gwaith) Date: 2005-09-29 11:23 Message: Logged In: YES user_id=208239 What this doesn't cover, specifically, is the ability to grant something for a given portion of levels. Like from 3-5, grant "X abilty" and from 6-9 instead grant "Y ability" For example: the Races of the Wild has several races that have abilities improve as they gain class levels. Glide goes to short bursts of flight, which goes to full flight, or something like that in the winged race. I'm just saying this tag needs some improvements. I like haveing everything in one tag, so we aren't having to maintain different code paths. ---------------------------------------------------------------------- Comment By: Eddy Anthony (eddyanthony) Date: 2005-09-29 09:28 Message: Logged In: YES user_id=886893 LEVEL is broken in more ways than that, I've been saying that for a year and a half. A new tag was Devons suggestion, the same sort of thing that was done for SPELL to SPELLS. I disagree that this tag should cover all of levels functions, DR, SR and CR should all be handles via BONUS with PRELEVEL tags. SA is being phased out, that just leaves feat. I want LEVELS to handle adding feats, templates and abilities in two modes, one which provides choices and the other which is a straight add. If you think it needs more design work, get specific, I've posted this and got imput on it at experimental. The bottom line is that I can go with this tag and I can go with having the existing tags fixed so they work correctly. Getting the existing tags to set all global tags sounds good to me as well but I'd like Devon and the programmers to evaluate and decide which option they want to implement. This is needed, we've needed it for a while now, it doesn't need to go back to design unless the coders say so. (BTW the LEVEL DR function is broken as well) ---------------------------------------------------------------------- Comment By: Andrew McDougall (tir-gwaith) Date: 2005-09-29 05:37 Message: Logged In: YES user_id=208239 I think this needs to actually be incorporated into the current HD and LEVEL tags. Both of those tags need to be expanded to cover ALL global tags. If we want to go to a new tag, we need to incorporate the functionality of the LEVEL and HD tags completely. This needs more design work. BTW: LEVEL apparently is broken. Originally, it was only N/PC levels, and HD was only Monster HD. We need to have a discussion of all the different ways we want to incorporate this kind of thing, especially with the new Ability object thingy. (That isn't the end-all cure everyone keeps reporting it to be - those things never are) ---------------------------------------------------------------------- Comment By: Martijn Verburg (karianna) Date: 2005-09-27 08:39 Message: Logged In: YES user_id=252169 Needed? - K ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1212315&group_id=25576 |