ShadowChemosh
Well-known member
Some questions I get from others I think are best listed out on the forums so that others can get the information also. The questions below refer to the free community Package for Eberron.
In this case I would recommend making an ART (Alternate Racial Trait) actually that is set to the Kalashtar race but don't have it replace anything. You would make two ART's one for for Wild Talent and one for Psionic Talent. Then simply have the gamer select the correct version.
More advanced would require a bootstrap condition. So the ART would bootstrap both feats and the feats would be setup to appear/not appear based on a tag on the Hero. The thing is that v2.0 of PU coming out very soon will have these tags you can look for. So its not worth setting up right now as its just going to change soon.
Hopefully that helps some....
Their is no way to actually attach/assign a feat to a character through a script. You actually have to either have the feat get selected through a portal or it has to be bootstrapped to something else.juan said:Hey man! Me and my players decided to follow some set of rules that we saw on the site https://sites.google.com/site/eberronpathfinder/
or at least, some part of it.
I am trying to implement this:
Bonus Feat: All Kalashtar gain the Wild Talent feat as a bonus feat. If they ever take a level in a class that gives them a manifester level, that bonus feat is replaced with the Psionic Talent feat instead.
but i am kind of stuck. I started with something like this:
if (#levelcount[Psion] = 0) then
#bonusfeat[fPUWildTal] ~dont even know if this ~exists
endif
But i doubt i am doing it the best way.
by the way, how can i know all the methods that starts with # ? Like #levelcount
they are really helpfull.
In this case I would recommend making an ART (Alternate Racial Trait) actually that is set to the Kalashtar race but don't have it replace anything. You would make two ART's one for for Wild Talent and one for Psionic Talent. Then simply have the gamer select the correct version.
More advanced would require a bootstrap condition. So the ART would bootstrap both feats and the feats would be setup to appear/not appear based on a tag on the Hero. The thing is that v2.0 of PU coming out very soon will have these tags you can look for. So its not worth setting up right now as its just going to change soon.
Hopefully that helps some....