Racial mechanics, early bootstrap conditionals

[TobyFox2002]

I have a question regarding creating mechanics. I've been working on ways to link core races/classes so we don't need to use multiple races (for the same race) that have different abilities across different systems.

Especially useful when working with worlds that allow for crossover content, or in situations where a person wants to allow feats/spells/classes from one system in another.

The easiest way to do it is to invert all of the show/hide options for the races/deities so that one has to have them selected in order to show those options. But that would mean using the exact opposite setting than what is currently used. I DO NOT like that idea because that could cause a lot of disruption to games.

The next easiest option is to use mechanics to bootstrap things to races/classes. The only problem that I have run into is creating a Bootstrap condition that checks for what race a hero has because the bootstrap condition occurs much too late to use for bootstrap condition. Roughly First/600. I need to have a bootstrap condition at First/85 at the latest.

Normally, I'd use an script and set the an abValue, the problem is neither mechanics or simple things have any fields that are remotely useful for this purpose. Which is frustrating.

I have two questions

1)How can I create a race checking bootstrap condition at First/100?

2) Is there any chance that herolabs can add all of the normal fields to both mechanics and simple things? That would make the storing and passing of variables much, much easier.

[ShadowChemosh]

See THIS thread for how I got an archetype to apply automatically when a specific Class is taken. The concept is pretty much the same for a Race.