Adding ruleset membership via an ext file

[harkan]

Is it possible to add a ruleset membership through an ext file? I've looked at the ext documentation and as far a I can see you can extend a rule to be part of a ruleset but not add a unit into a ruleset.

cheers

[harkan]

Also. is there a way to have more than one rule start selected in the options within the same context?

[rob]

At 02:00 AM 6/4/2005 -0400, you wrote:
>Is it possible to add a ruleset membership through an ext file? I've
>looked at the ext documentation and as far a I can see you can extend a
>rule to be part of a ruleset but not add a unit into a ruleset.

Er, add a UNIT into a RULESET? I'm utterly confused. How in the world would
you add units to rulesets? Please explain.

-Rob

---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (408) 927-9880
Lone Wolf Development www.wolflair.com

[rob]

At 06:15 AM 6/4/2005 -0400, you wrote:
>Also. is there a way to have more than one rule start selected in the options?

How are rules being used in conjunction with options? I think the problem
is that you are jumbling up terms. Please use the terms that are
established within AB so that I know what you are talking about. Options
and rules are completely unrelated things, so one of those terms is being
misused. Please clarify.

-Rob

---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (408) 927-9880
Lone Wolf Development www.wolflair.com

[harkan]

OK, within the 40K files some files use the ext files to extend the IG into them as available units, i.e. WH. However some of the IG units have specific 'doctrines' applied to them which mean that the unit is only available if that doctrine is selected for the IG. However the WH don't use the doctrines and therefore when the ext file extends the unit into the WH list the unit does not show.

To try and avoid crossing over between files and adding membeship tags in the IG file for the WH so the unit is visible I was wondering if there was a way that the ruleset for the doctrine could be applied via the ext file, or the membership statement could be extended in some way in it? Does that make any more sense?

[harkan]

Originally Posted by rob

At 06:15 AM 6/4/2005 -0400, you wrote:
>Also. is there a way to have more than one rule start selected in the options?

How are rules being used in conjunction with options? I think the problem
is that you are jumbling up terms. Please use the terms that are
established within AB so that I know what you are talking about. Options
and rules are completely unrelated things, so one of those terms is being
misused. Please clarify.

Within one context group is there a way to have all the rulesets start enabled, i.e. for Kill team rules there are immutable and mutable rules (represented by two context groups with rulesets in each), the player is penalised for each immutable rule they disregard, but initially all rules start off enabled. For usability it would be significantly better if all the rulesets representing the game rules start selected instead of forcing the user to go through and select 13 different rulesets

[rob]

At 03:43 AM 6/5/2005 -0400, you wrote:
>To try and avoid crossing over between files and adding membeship tags in
>the IG file for the WH so the unit is visible I was wondering if there was
>a way that the ruleset for the doctrine could be applied via the ext file,
>or the membership statement could be extended in some way in it? Does that
>make any more sense?

One thing we've already slated for the upcoming release of AB is something
to address exactly this issue. Specifically, you'll be able to extend the
Member tagexpr of entities via extension files. This ought to give you
exactly what you need. And this functionality is due out reasonably soon
for Beta testing.

-Rob


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (408) 927-9880
Lone Wolf Development www.wolflair.com

[rob]

At 03:58 AM 6/5/2005 -0400, you wrote:
>Within one context group is there a way to have all the rulesets start
>enabled, i.e. for Kill team rules there are immutable and mutable rules,
>the player is penalised for each immutable rule they disregard, but
>initially all rules start off enabled. For usability it oulw be
>significantly better if all the rules start selected instead of forcing
>the user to go through and select 13 different rules

OK, so within a given rule context whose behavior is "select any", you want
to be able to have all the rulesets be designated as selected by default.
Is that right?

-Rob

---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (408) 927-9880
Lone Wolf Development www.wolflair.com

[harkan]

Originally Posted by rob

At 03:58 AM 6/5/2005 -0400, you wrote:
>Within one context group is there a way to have all the rulesets start
>enabled, i.e. for Kill team rules there are immutable and mutable rules,
>the player is penalised for each immutable rule they disregard, but
>initially all rules start off enabled. For usability it oulw be
>significantly better if all the rules start selected instead of forcing
>the user to go through and select 13 different rules

OK, so within a given rule context whose behavior is "select any", you want
to be able to have all the rulesets be designated as selected by default.
Is that right?

yup

[rob]

I just verified that there is nothing that precludes this from being done. All you need to do is designate all of the rulesets as "default" and AB ought to work fine.

-Rob

At 01:04 AM 6/5/2005, you wrote:

rob wrote:
At 03:58 AM 6/5/2005 -0400, you wrote:
>Within one context group is there a way to have all the rulesets start
>enabled, i.e. for Kill team rules there are immutable and mutable rules,
>the player is penalised for each immutable rule they disregard, but
>initially all rules start off enabled. For usability it oulw be
>significantly better if all the rules start selected instead of forcing
>the user to go through and select 13 different rules

OK, so within a given rule context whose behavior is "select any", you want
to be able to have all the rulesets be designated as selected by default.
Is that right?



yup