Hiding options from specific races
 

I'm learning as I go along, so bear with me if I'm not explaining clearly enough or you need more detail. I'm reading through the tutorials and manuals, but I can only absorb so much at a time :)

I'm creating a data file to act as holding place for item, option, and unit shared to multiple races.

Now for an option as part of a shared unit, how can I hide / null this option if its not available for a particular race?

Is it through script using the "Live" section under Option? If so, can anyone post a basic script that might do this?

tks

In the Live script, you need:
!roster.racename

or if you want to kill the option for more than one race.
!(roster.racename1 | roster.racename2 | roster.racename3)

or the equivalent
!roster.racename1 & !roster.racename2 & !roster.racename3
but that has one more letter to type ;-)


That stops the option from appearing if the roster primary race is "racename".
Use the datafile debugging aids in AB to see what tags are applied to the unit the options are linked to just to confirm you've got the right one.

Russell.

Hiding options from specific races
 

For entities, you'll need to utilize the Member tag expression to control visibility based on race and ruleset. There is a topic about this in the Applying the Concepts (i.e. How To) chapter of the docs. It's called Controlling Which Entities Are Shown. The same concepts apply to the use of Live tag expression on links and options. The examples cited by Russell are exactly the technique you should be using.

-Rob

At 03:05 PM 1/27/2006, you wrote:

Hiding options from specific races
 

Quick Note!!!

When I point out where to find stuff in the docs, it's *NOT* a complaint that you haven't found the pertinent section in the docs. The docs are huge and it's quite difficult due to that size to find things unless you know what you're looking for.

The intent is to point you to the topic so that you'll have (a) more details on the issue, (b) more examples to refer to, and (c) links from that section in the docs to related sections that might prove useful. The goal is to educate, so please take the comments in the spirit they are intended. :-)

-Rob