Menu
▾
▴
[Pcgen-trackers] [ pcgen-Bugs-900842 ] Feats not checked when granted from TEMPLATE
|
From: SourceForge.net <no...@so...> - 2004-09-09 17:13:27
|
Bugs item #900842, was opened at 2004-02-19 22:05 Message generated for change (Comment added) made by eddyanthony You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384719&aid=900842&group_id=25576 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ratheof Blithwyn (blithwyn) Assigned to: Devon Jones (soulcatcher) Summary: Feats not checked when granted from TEMPLATE Initial Comment: I am trying to use templates as a way to solve racial progression for a new source and I have come across a bit of a problem. My template that is autogranted to the race looks a bit like this: Dwarf Racial Talents LEVEL:1:FEAT:TYPE.DwarfRacialTalent LEVEL:2:FEAT:TYPE.DwarfRacialTalent (lots of stuff omitted) with a bunch hidden feats with the following theme: Feat 1 ..yaddayaddayadda.. Feat 2 ..yaddayaddayadda.. PREFEAT:1,Feat 1 Another Feat ..yaddayaddayadda.. PREFEAT:1,Dodge Yet Another Feat ..yaddayaddayadda.. At first all seems good, the template fires a chooser with Feat 1 and Yet Another Feat. I pick Feat 1 and move on. Then I pick Dodge as normal feat. Next level I get a chooser with Feat 1, Another Feat, Yet Another Feat. This is not as expected. (Note that the Feat 1 hows up ok in the OS so it is in there somewhere;) I should be able to choose Feat 2 and not be able to choose Feat 1 again (MULT:NO). I have also tried PRESA with similar result. It looks as if feats granted from the _template_ is overlooked when I get to the chooser. At least if the chooser is fired from a template. To get around the problem I tried a different approach by using LEVEL:1:FEAT:AddDwarfRacialTalent in the template and let the hidden feat AddDwarfRacialTalent fire a chooser with ADD:FEAT (TYPE=DwarfRacialTalent) But that didn't fire a chooser at all. This might possibly a different issue. (Using 5.6 RC 2 with gamemode 3.5) So does this affect any of the current sources? I have no idea but possibly not. ---------------------------------------------------------------------- >Comment By: Eddy Anthony (eddyanthony) Date: 2004-09-09 13:13 Message: Logged In: YES user_id=886893 From discussion on the boards it has been asserted that this is not a bug but in fact the way the tag was designed to work. What is needed is an expansion of this tag to allow it to call any global tag, which is a FREQ. I've opened a feature request for this: [ 1025273 ] LEVEL & HD tags need to be able to call all global tags ---------------------------------------------------------------------- Comment By: Eric Beaudoin (ericbeaudoin) Date: 2004-07-11 23:27 Message: Logged In: YES user_id=324612 This was assign to me when K. went away I think. I'm assigning to Devon as it is a code issue. Someone with debug skills will have to take a look. ---------------------------------------------------------------------- Comment By: Ratheof Blithwyn (blithwyn) Date: 2004-03-09 15:48 Message: Logged In: YES user_id=677457 Not quite Barak, the feeling I have is that not all possible sources for feats are iterated through when checking PREFEAT. It works for feats gained "normally" but not for feats gained earlier from the template. It might be worth noting that PREVARs work ok. So it is possible to work around if one wants to clutter up the LST with a lot of variables (which I don't). Another thing, after doing some more research of Dawnforge I realise I really need _both_ issues resolved:( ---------------------------------------------------------------------- Comment By: Chris Chandler (barako) Date: 2004-03-07 09:37 Message: Logged In: YES user_id=607889 Eric.Kar, you pop a chooser using LEVEL:#:FEAT:TYPE=blah. The chooser will fire allowing you to pick from all feats with TYPE=blah. The problem is that the PREREQS (or at least PREFEATs) are being ignored when the chooser pops up... which leads me to believe the VFEAT chooser is popping up rather than the FEAT chooser... but I'm not a code monkey so I could be completely wrong. :p ---------------------------------------------------------------------- Comment By: Ratheof Blithwyn (blithwyn) Date: 2004-02-26 16:24 Message: Logged In: YES user_id=677457 As for the second issue, that was an attempt to achieve a similar effect in another way. Expanding on that. I was not aware that it wasn't supposed to work. I use it in a number of places in the Path books. I have a ADD:FEAT(TYPE=BunchOfFeats) on a class line and get a chooser from that. The feat I choose has also a ADD:FEAT(TYPE=AnotherBunchOfFeats) which fires a second chooser. This works fine for which I am very glad. That's why I tried it in templates as well (skipping the first chooser). LEVEL:1:FEAT:FeatFromBunchOfFeats where that feat has ADD:FEAT(TYPE=AnotherBunchOfFeats). That didn't work however. I think it would be good if that worked as well, it is a very powerful tool. The Path books as well as Dawnforge from FFG are full of these kind of two step choices. In the Path books I don't have to use templates. Dawnforge is another matter. A solution with templates like in the "prototype" file will be very neat in my opinion to solve the racial progression. PS @Eric: It is the LEVEL:1:FEAT:TYPE.DwarfRacialTalent that fires the chooser. DS ---------------------------------------------------------------------- Comment By: Ratheof Blithwyn (blithwyn) Date: 2004-02-26 10:39 Message: Logged In: YES user_id=677457 Ok, I'll try again=) The main issue is what is described first. Namely the problem with PREFEAT using feats granted from the template. To illustrate I have attached (I hope) dawnforge_prototyp.zip. Unzip under the data->FantasyFlightGames. Instruction to reproduce the problem: 1. Start PCGen 2. Select gamemode 3.5e 3. Load 3.5 RSRD and Fantasy Flight Games -> Dawnforge 4. Press "Create new character" (the stats shoudn't be important, I used 10 across the border) 5. Choose any alignment 6. Choose Race "Dwarf (DF)" First level up: 7. Level up once. Lets say pick a level of fighter. This fires the chooser with "Feat 1" and "Feat A", that's ok. 8. Pick "Feat A" 9. Pick Improved Initiative from next chooser. 10. Pick any outfit. At this point one can verify Feat A by checking the print preview for example. Second level up: 11. Pick one more level of fighter This fires the chooser with "Feat 1", "Feat A" and "Pre Initiative" This is wrong. "Feat B" should show up instead of "Feat A" since B has A as PREFEAT "Pre Initiative" is correct and shows that PREFEAT works for Improved Initiative. (hence my comment about PREFEAT not working for feats previously gained from the template) ---------------------------------------------------------------------- Comment By: Eric Beaudoin (ericbeaudoin) Date: 2004-02-25 19:40 Message: Logged In: YES user_id=324612 I'm lost to. There seams to be a problem with the way the feat are handle with TEMPLATE and the LEVEL tag but I got lost somewhere with the "Another Feat" and "Yet Another Feat" feats. I don't even see where the call to the chooser was put in. LEVEL:x:FEAT:xxx doesn't usualy call a chooser, it just add the feat. PRESA has always been flaky and not reliable. We've deprecated its use since we started working with hidden feats. For the third thing, if a feat can call ADD:FEAT, it's a new thing. I'm not saying it's not possible but it used not to be possible. Attaching a couple of files that demonstrates both problems would go a long way to help us understand the issues here. ---------------------------------------------------------------------- Comment By: Martijn Verburg (karianna) Date: 2004-02-25 17:27 Message: Logged In: YES user_id=252169 I'm lost Eric, is this actually a problem? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384719&aid=900842&group_id=25576 |
