Where would the process that's doing this be?

[Paragon]

Okay, I'm doing my ongoing work to patch and fill the 4e files. One of the things I do while looking through them today is to notice that there's actually no pick-req, pre-req or expr-req on the feats that have the Channel Divinity class feature as a pre-requisite--yet the program is still enforcing this. It appears its doing so because there's a tag called User.RecChanDiv present, and the program is somehow knowing that this means it needs to look for that feature before allowing the feat.

My question is, where would the information to tell the program to do that be? I thought it might be a Procedure, but the only thing that looked plausible there doesn't seem to be doing that. So where would it be storing that process? It'd be convenient to be able to add a couple others rather than having to dump the rather long string in expr-req to tell feats and such to look for Psionic Augmentation and any other pre-reqs that didn't get implemented this way.

Anyone care to speculate?

[ShadowChemosh]

Its in the Feat component. I don't know what 4e calls it in Pathfinder its "Component.BaseFeat". That component which is Part of all feats can have all the same scripts that a normal feat has. So it would have the Pre-Req script running.

I assume 4e is like Pathfinder is that you have no access to the structural files. Meaning you can't modify or add to Component scripts.

[Paragon]

Originally Posted by ShadowChemosh

Its in the Feat component. I don't know what 4e calls it in Pathfinder its "Component.BaseFeat". That component which is Part of all feats can have all the same scripts that a normal feat has. So it would have the Pre-Req script running.

I assume 4e is like Pathfinder is that you have no access to the structural files. Meaning you can't modify or add to Component scripts.

Ah, well. I was afraid that might be the case. I'll have to just continue with the expr-reqs, then. They work, they're just cumbersome.