Favored class option for single class but all races

[frumple]

I have some favored class options that apply to a single class but should be available to all races. Normally you have to specify race and class for a FCO, but in this case I want it for all possible races. Is this doable?

[AndrewD2]

Is it all races for one class?

I'm not sure if there's an IsRace.All tag for the item, but you do have to bootstrap them to either the race or class or a mechanic (if you don't have access to one of the other).

[Aaron]

Maybe add an eval script to the FCO which finds the hero's race and pulls the IsRace tag for the present race to itself? That way you wouldn't need an "All" tag.

[frumple]

Yep that did it! Thanks Aaron.

[frumple]

...and another challenge. Turns out these FCO should only show if they are on the 1st level of the specific class. This is even if it is not the first level on the hero.

Ideas?

[frumple]

Yes! Figured it out!!!

I put the following code on the class level (not the class helper)

Final/10005

~ only do this on 1st level
doneif (field[cThisIndex].value <> 1)

foreach pick in hero from BaseClLev where "{thingid.XXX of the class level}"
  if (eachpick.field[cThisIndex].value = 1) then
    eachpick.field[cFavorExpr].text &= " | ({list of thingid.XXX of the FCOs})"
    endif
nexteach

[AndrewD2]

Not the best option, but create the effect with a custom special and then have the FCB set the table count to 1 (and do it really really late so that you don't have a chance of getting over written) Then maybe toss on an eval rule that if they take it more than once it throws an error.

[frumple]

I actually did that but it didn't do quite what I needed.

To clarify, these are not your typical FCOs. They state if they are taken at 1st level of the class (and only 1st level) then they effect the spellbook of the class in a specific way (basically expands it to include another specific class's spells). They never need to take the FCO again to gain a spell. This is the reason I wanted them to only show on the 1st level of the class and never again. Having them show on later levels will do nothing and potentially confuse users.

[JustinThomason]

Maybe you should do it with archetypes or a selectable class feature that is set at level 1? The trick is if it is only available if it is a favored class, I am not sure how you would enforce it.