Cutting feat taxes

[Mathias]

Originally Posted by TobyFox2002

If you take the dodge feat for example, you would add this:

hero.childfound[fDodge].assign[Helper.Helper]

That will mark the Dodge feat as being a "helper" feat and prevent it from showing up in the feat selection dialog box and in most class, race and configurable bonus feat custom ability. You do not need to have a Thing on the hero to assign tags to it. Just make sure you use childfound and not just child.

At least, that's how I would try and work it. Are you saying that wouldn't work?

Have you tested this and actually gotten it to work?

As ShadowChemosh said, it's very important to remember the difference between things and picks, and consider what changes are allowed while something's still a thing.

[wdmartin]

Well, I finally got a chance to sit down and really study this.

The problem portfolios in question had somehow gotten their polarities reversed, so to speak. That is, "Eliminate Feat Taxes" was disabled, but the character had the version of the feat from my code selected instead of the default version, and so it quite correctly threw an error.

I really have no idea how that happened. Both the portfolios in question predate the World is Square project by several years, and so far as I know neither one has ever actually had the "Eliminate Feat Taxes" option enabled. It's really weird.

Deleting the feats in question, making sure that the module was disabled, and then adding them again corrected the problem.

Thanks for the suggestions, and sorry for firing off requests for help before I'd taken the time to investigate thoroughly.

[Angela2013]

This is probably a stupid question but what are feat taxes? Do you mean the perquisites for a feat.

[ShadowChemosh]

Originally Posted by Angela2013

This is probably a stupid question but what are feat taxes? Do you mean the perquisites for a feat.

Yes. Some people think having to meet a requirement is a "tax" or a really bad thing. To take Cleave you need Power Attack and many people don't like that idea as Power Attack in example should just be a normal combat option not a feat.

Sense you get so FEW feats a person should only ever take feats that give a BIG bang for the buck.

[charlieluce]

My pet peeve in feat taxes is Mobility, which as far as I can tell pretty much exists only to make everything that it's a prerequisite for cost an extra Feat.

[TheIronGolem]

Mobility is a feat tax, but Combat Expertise is the Feat IRS.

[TobyFox2002]

Originally Posted by Mathias

Have you tested this and actually gotten it to work?

As ShadowChemosh said, it's very important to remember the difference between things and picks, and consider what changes are allowed while something's still a thing.

I am so sorry, I didn't even see this question Mathais. Following so many threads it must have gotten buried in my emails.

To answer you, no I haven't I am just working on instinct and what feels intuitive. As for what actually works, I am not sure. I realize that what feels right and what would actually work can be very different, and my knowledge of the difference between a Pick and a Thing is shaky at best. I'm not a technical programmer, and the vocabulary makes my head spin, even and is made even worse when I try read up on it. LOL

If you say it wont work, then it wont. I was just throwing out my ideas to brainstorm possible solutions. If it seemed otherwise, I did not intend so.