A
armybuilder at yahoogroup
Guest
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Win a Marvel vs. CapCom 2 Arcade System!
Click Here to Enter...
http://us.click.yahoo.com/9YX7sC/o58CAA/9ZuFAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 8 messages in this issue.
Topics in this digest:
1. inquisitor custom output extension?
From: scratchy45@yahoo.com
2. Re: inquisitor custom output extension?
From: Fred <frederic_de_bovee@yahoo.fr>
3. Re: Mein Panzer
From: beyond_the_heresy@yahoo.ca
4. I'm NOT an idiot (really)
From: jizbrand@kc.rr.com
5. RE: I'm NOT an idiot (really) [maybe I am!]
From: jizbrand@kc.rr.com
6. Re: RE: I'm NOT an idiot (really) [maybe I am!]
From: Rob Bowes <rob@wolflair.com>
7. Re: RE: I'm NOT an idiot (really) [maybe I am!]
From: jizbrand@kc.rr.com
8. Re: RE: I'm NOT an idiot (really) [maybe I am!]
From: Rob Bowes <rob@wolflair.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Tue, 28 Aug 2001 14:15:44 -0000
From: scratchy45@yahoo.com
Subject: inquisitor custom output extension?
Has anyone worked on or seen such an animal?
Timothy Colonna
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 28 Aug 2001 16:49:32 +0200 (CEST)
From: Fred <frederic_de_bovee@yahoo.fr>
Subject: Re: inquisitor custom output extension?
--- scratchy45@yahoo.com a écrit : > Has anyone worked on or seen such
an animal?
>
>
> Timothy Colonna
>
>
I develop an independant soft for Inquisitor character creation, but
there is no link with AB, and it is in French. You may easyly translate
the ressources files, and have a full english output version. The soft
isn't very well designed, so you will have to search a little to find
what you want...
Else, there are files for AB in the ML files, but no custom output
extension...
Garfunkel
___________________________________________________________
Do You Yahoo!? -- Un e-mail gratuit @yahoo.fr !
Yahoo! Courrier : http://fr.mail.yahoo.com
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Tue, 28 Aug 2001 15:51:36 -0000
From: beyond_the_heresy@yahoo.ca
Subject: Re: Mein Panzer
When you do have a Mein Panzer ab file out could you please post a
message on the Mein Panzer group.
http://groups.yahoo.com/group/meinpanzer
Alain
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Tue, 28 Aug 2001 17:20:38 -0000
From: jizbrand@kc.rr.com
Subject: I'm NOT an idiot (really)
I'm starting to understand the mindset it takes to make AB work
correctly, but I'm still having a couple of difficulties.
My files have a number of races, each with characters and units.
Each unit inherits type:Troops from a generic xUnit. Each character
inherits type:Character from a generic xChar. I'm trying to model a
couple of rule restrictions: first, an army can contain a non-racial
characters but must have at least one troop unit corresponding to the
same racial type for each character. An army can contain racial
characters at the rate of two racial characters per racial troop
unit. I had that covered with trat attributes.
Any character can lead a unit, whether of his own race or any other.
So I thought I'd use the list:xx*=Character attribute to accomplish
that. That works fine except for one little problem. Validation
reports non-racial characters commanding racial units as not
belonging to any valid composition class. I tried first to magnetize
children, but then the non-racial character seems to be treated as a
racial character. In fact, even a racial character doesn't count
toward the limit on characters.
I also tried assigning type:Character to the unit to reflect the
assignment of a character, but that doesn't validate correctly either.
I'm looking for something along the Clan War line where non-native
characters can command native troops (but without the CW oathing).
Just a hint in the right direction would be appreciated.
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Tue, 28 Aug 2001 18:43:10 -0000
From: jizbrand@kc.rr.com
Subject: RE: I'm NOT an idiot (really) [maybe I am!]
Solved the composition class problem (duh). But still can't validate
requirements for non-racial characters in racial units.
From: jizbrand@k...
Date: Tue Aug 28, 2001 12:20 pm
Subject: I'm NOT an idiot (really)
I'm starting to understand the mindset it takes to make AB work
correctly, but I'm still having a couple of difficulties.
My files have a number of races, each with characters and units.
Each unit inherits type:Troops from a generic xUnit. Each character
inherits type:Character from a generic xChar. I'm trying to model a
couple of rule restrictions: first, an army can contain a non-racial
characters but must have at least one troop unit corresponding to the
same racial type for each character. An army can contain racial
characters at the rate of two racial characters per racial troop
unit. I had that covered with trat attributes.
Any character can lead a unit, whether of his own race or any other.
So I thought I'd use the list:xx*=Character attribute to accomplish
that. That works fine except for one little problem. Validation
reports non-racial characters commanding racial units as not
belonging to any valid composition class. I tried first to magnetize
children, but then the non-racial character seems to be treated as a
racial character. In fact, even a racial character doesn't count
toward the limit on characters.
I also tried assigning type:Character to the unit to reflect the
assignment of a character, but that doesn't validate correctly either.
I'm looking for something along the Clan War line where non-native
characters can command native troops (but without the CW oathing).
Just a hint in the right direction would be appreciated.
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Tue, 28 Aug 2001 15:53:06 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: RE: I'm NOT an idiot (really) [maybe I am!]
I would solve this using type-based wildcards. From your description, this
ought to be consistent with your current model, except that you'll need to
scrap the inheritance of the type assignments from the generic units.
Instead, you'll either need generic units for each race or will have to
assign the proper types directly to each unit. Here's my idea....
Instead of using the type names "Troops" and "Character", use the type
names "Unit" and "Char". These shorter names allow this technique to be
used. Then append the RACE to the type name for each unit. For example, if
the race is "Orc", assign the type names "UnitOrc" and "CharOrc" to the
appropriate units. You can now define "trat" attributes that verify the
presence of an Orc character also includes an Orc unit by comparing the
number of "UnitOrc" to the number of "CharOrc". This will work for all
races. Now for the type wildcards (see the manual for more details). You
can define the "list" attribute to use the wildcard designation to get all
characters, which would be "Char?" (the '?' would match characters from
every race). For your "trat" that verifies the two characters per unit
ratio, you would use the types "Char?" and "Unit?", which will generically
match all characters and units, respectively.
This method ought to be easy to implement and is consistent with the model
you've already adopted. Let me know if you have additional questions on it,
or if any of this isn't clear.
Thanks, Rob
At 06:43 PM 8/28/2001 +0000, you wrote:
>Solved the composition class problem (duh). But still can't validate
>requirements for non-racial characters in racial units.
>
>
>From: jizbrand@k...
>Date: Tue Aug 28, 2001 12:20 pm
>Subject: I'm NOT an idiot (really)
>
>
>I'm starting to understand the mindset it takes to make AB work
>correctly, but I'm still having a couple of difficulties.
>
>My files have a number of races, each with characters and units.
>Each unit inherits type:Troops from a generic xUnit. Each character
>inherits type:Character from a generic xChar. I'm trying to model a
>couple of rule restrictions: first, an army can contain a non-racial
>characters but must have at least one troop unit corresponding to the
>same racial type for each character. An army can contain racial
>characters at the rate of two racial characters per racial troop
>unit. I had that covered with trat attributes.
>
>Any character can lead a unit, whether of his own race or any other.
>So I thought I'd use the list:xx*=Character attribute to accomplish
>that. That works fine except for one little problem. Validation
>reports non-racial characters commanding racial units as not
>belonging to any valid composition class. I tried first to magnetize
>children, but then the non-racial character seems to be treated as a
>racial character. In fact, even a racial character doesn't count
>toward the limit on characters.
>
>I also tried assigning type:Character to the unit to reflect the
>assignment of a character, but that doesn't validate correctly either.
>
>I'm looking for something along the Clan War line where non-native
>characters can command native troops (but without the CW oathing).
>Just a hint in the right direction would be appreciated.
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 7
Date: Wed, 29 Aug 2001 00:20:31 -0000
From: jizbrand@kc.rr.com
Subject: Re: RE: I'm NOT an idiot (really) [maybe I am!]
Actually, I had already done that, but backwards, of course (OrcUnit,
ElfChar). So I changed them all, but I'm still having the same
problem (BTW, those types are assigned directly to the units, not
inherited). So here's a more complete description (I hope):
I have two trat's. Here's what it looks like for the Orc race:
trat:TrpsOrc@1u:CharOrc@2m [2 orc characters per native orc unit]
trat:TrpsElf@1u:CharElf@1m [1 elf character per allied elf unit]
For the Elf race, the trat's are reversed:
trat:TrpsOrc@1u:CharOrc@1m [1 orc character per allied orc unit]
trat:TrpsElf@1u:CharElf@2m [2 elf characters per native elf unit]
The tricky part is that an Elf character can be leading an Orc unit
in either army, and vice versa. My list attribute looks like:
list:xx*=Char?, which gives me all the characters for any race.
So far, so good. But no matter what race I pick the leader from,
that leader doesn't get counted against the proper trat.
All units have an option "Assign Leader" which contains just the
list:xx*=Char?
And that's where I'm lost!
--- In armybuilder@y..., Rob Bowes <rob@w...> wrote:
> I would solve this using type-based wildcards. From your
description, this
> ought to be consistent with your current model, except that you'll
need to
> scrap the inheritance of the type assignments from the generic
units.
> Instead, you'll either need generic units for each race or will
have to
> assign the proper types directly to each unit. Here's my idea....
>
> Instead of using the type names "Troops" and "Character", use the
type
> names "Unit" and "Char". These shorter names allow this technique
to be
> used. Then append the RACE to the type name for each unit. For
example, if
> the race is "Orc", assign the type names "UnitOrc" and "CharOrc" to
the
> appropriate units. You can now define "trat" attributes that verify
the
> presence of an Orc character also includes an Orc unit by comparing
the
> number of "UnitOrc" to the number of "CharOrc". This will work for
all
> races. Now for the type wildcards (see the manual for more
details). You
> can define the "list" attribute to use the wildcard designation to
get all
> characters, which would be "Char?" (the '?' would match characters
from
> every race). For your "trat" that verifies the two characters per
unit
> ratio, you would use the types "Char?" and "Unit?", which will
generically
> match all characters and units, respectively.
>
> This method ought to be easy to implement and is consistent with
the model
> you've already adopted. Let me know if you have additional
questions on it,
> or if any of this isn't clear.
>
> Thanks, Rob
>
>
> At 06:43 PM 8/28/2001 +0000, you wrote:
> >Solved the composition class problem (duh). But still can't
validate
> >requirements for non-racial characters in racial units.
> >
> >
> >From: jizbrand@k...
> >Date: Tue Aug 28, 2001 12:20 pm
> >Subject: I'm NOT an idiot (really)
> >
> >
> >I'm starting to understand the mindset it takes to make AB work
> >correctly, but I'm still having a couple of difficulties.
> >
> >My files have a number of races, each with characters and units.
> >Each unit inherits type:Troops from a generic xUnit. Each
character
> >inherits type:Character from a generic xChar. I'm trying to model
a
> >couple of rule restrictions: first, an army can contain a non-
racial
> >characters but must have at least one troop unit corresponding to
the
> >same racial type for each character. An army can contain racial
> >characters at the rate of two racial characters per racial troop
> >unit. I had that covered with trat attributes.
> >
> >Any character can lead a unit, whether of his own race or any
other.
> >So I thought I'd use the list:xx*=Character attribute to accomplish
> >that. That works fine except for one little problem. Validation
> >reports non-racial characters commanding racial units as not
> >belonging to any valid composition class. I tried first to
magnetize
> >children, but then the non-racial character seems to be treated as
a
> >racial character. In fact, even a racial character doesn't count
> >toward the limit on characters.
> >
> >I also tried assigning type:Character to the unit to reflect the
> >assignment of a character, but that doesn't validate correctly
either.
> >
> >I'm looking for something along the Clan War line where non-native
> >characters can command native troops (but without the CW oathing).
> >Just a hint in the right direction would be appreciated.
>
>
> --------------------------------------------------------------------
-------
> Rob Bowes (rob@w...) (650) 726-9689
> Lone Wolf Development
www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 8
Date: Tue, 28 Aug 2001 21:31:39 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: RE: I'm NOT an idiot (really) [maybe I am!]
This more detailed explanation helps a LOT to explain what's going on. So
the problem is that the leaders aren't triggering their validation rules,
right? Then I would guess that you haven't assigned a "forc" attribute to
the characters. Except where explicitly noted otherwise, validation rules
ONLY apply to TOP-LEVEL units. Since the characters are being selected via
options, they are child units. That means their validation rules aren't
being processed. You can force their validation rules to be processed at
all times by including the "forc" attribute.
Hope this helps,
Rob
P.S. Yes, this is flagged in the manual, but it's a common mistake. If you
have a suggestion on how to make this more blatant in the documentation,
please let me know.
At 12:20 AM 8/29/2001 +0000, you wrote:
>Actually, I had already done that, but backwards, of course (OrcUnit,
>ElfChar). So I changed them all, but I'm still having the same
>problem (BTW, those types are assigned directly to the units, not
>inherited). So here's a more complete description (I hope):
>
>I have two trat's. Here's what it looks like for the Orc race:
>
>trat:TrpsOrc@1u:CharOrc@2m [2 orc characters per native orc unit]
>trat:TrpsElf@1u:CharElf@1m [1 elf character per allied elf unit]
>
>For the Elf race, the trat's are reversed:
>
>trat:TrpsOrc@1u:CharOrc@1m [1 orc character per allied orc unit]
>trat:TrpsElf@1u:CharElf@2m [2 elf characters per native elf unit]
>
>The tricky part is that an Elf character can be leading an Orc unit
>in either army, and vice versa. My list attribute looks like:
>
>list:xx*=Char?, which gives me all the characters for any race.
>
>So far, so good. But no matter what race I pick the leader from,
>that leader doesn't get counted against the proper trat.
>
>All units have an option "Assign Leader" which contains just the
>list:xx*=Char?
>
>And that's where I'm lost!
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Win a Marvel vs. CapCom 2 Arcade System!
Click Here to Enter...
http://us.click.yahoo.com/9YX7sC/o58CAA/9ZuFAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 8 messages in this issue.
Topics in this digest:
1. inquisitor custom output extension?
From: scratchy45@yahoo.com
2. Re: inquisitor custom output extension?
From: Fred <frederic_de_bovee@yahoo.fr>
3. Re: Mein Panzer
From: beyond_the_heresy@yahoo.ca
4. I'm NOT an idiot (really)
From: jizbrand@kc.rr.com
5. RE: I'm NOT an idiot (really) [maybe I am!]
From: jizbrand@kc.rr.com
6. Re: RE: I'm NOT an idiot (really) [maybe I am!]
From: Rob Bowes <rob@wolflair.com>
7. Re: RE: I'm NOT an idiot (really) [maybe I am!]
From: jizbrand@kc.rr.com
8. Re: RE: I'm NOT an idiot (really) [maybe I am!]
From: Rob Bowes <rob@wolflair.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Tue, 28 Aug 2001 14:15:44 -0000
From: scratchy45@yahoo.com
Subject: inquisitor custom output extension?
Has anyone worked on or seen such an animal?
Timothy Colonna
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 28 Aug 2001 16:49:32 +0200 (CEST)
From: Fred <frederic_de_bovee@yahoo.fr>
Subject: Re: inquisitor custom output extension?
--- scratchy45@yahoo.com a écrit : > Has anyone worked on or seen such
an animal?
>
>
> Timothy Colonna
>
>
I develop an independant soft for Inquisitor character creation, but
there is no link with AB, and it is in French. You may easyly translate
the ressources files, and have a full english output version. The soft
isn't very well designed, so you will have to search a little to find
what you want...
Else, there are files for AB in the ML files, but no custom output
extension...
Garfunkel
___________________________________________________________
Do You Yahoo!? -- Un e-mail gratuit @yahoo.fr !
Yahoo! Courrier : http://fr.mail.yahoo.com
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Tue, 28 Aug 2001 15:51:36 -0000
From: beyond_the_heresy@yahoo.ca
Subject: Re: Mein Panzer
When you do have a Mein Panzer ab file out could you please post a
message on the Mein Panzer group.
http://groups.yahoo.com/group/meinpanzer
Alain
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Tue, 28 Aug 2001 17:20:38 -0000
From: jizbrand@kc.rr.com
Subject: I'm NOT an idiot (really)
I'm starting to understand the mindset it takes to make AB work
correctly, but I'm still having a couple of difficulties.
My files have a number of races, each with characters and units.
Each unit inherits type:Troops from a generic xUnit. Each character
inherits type:Character from a generic xChar. I'm trying to model a
couple of rule restrictions: first, an army can contain a non-racial
characters but must have at least one troop unit corresponding to the
same racial type for each character. An army can contain racial
characters at the rate of two racial characters per racial troop
unit. I had that covered with trat attributes.
Any character can lead a unit, whether of his own race or any other.
So I thought I'd use the list:xx*=Character attribute to accomplish
that. That works fine except for one little problem. Validation
reports non-racial characters commanding racial units as not
belonging to any valid composition class. I tried first to magnetize
children, but then the non-racial character seems to be treated as a
racial character. In fact, even a racial character doesn't count
toward the limit on characters.
I also tried assigning type:Character to the unit to reflect the
assignment of a character, but that doesn't validate correctly either.
I'm looking for something along the Clan War line where non-native
characters can command native troops (but without the CW oathing).
Just a hint in the right direction would be appreciated.
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Tue, 28 Aug 2001 18:43:10 -0000
From: jizbrand@kc.rr.com
Subject: RE: I'm NOT an idiot (really) [maybe I am!]
Solved the composition class problem (duh). But still can't validate
requirements for non-racial characters in racial units.
From: jizbrand@k...
Date: Tue Aug 28, 2001 12:20 pm
Subject: I'm NOT an idiot (really)
I'm starting to understand the mindset it takes to make AB work
correctly, but I'm still having a couple of difficulties.
My files have a number of races, each with characters and units.
Each unit inherits type:Troops from a generic xUnit. Each character
inherits type:Character from a generic xChar. I'm trying to model a
couple of rule restrictions: first, an army can contain a non-racial
characters but must have at least one troop unit corresponding to the
same racial type for each character. An army can contain racial
characters at the rate of two racial characters per racial troop
unit. I had that covered with trat attributes.
Any character can lead a unit, whether of his own race or any other.
So I thought I'd use the list:xx*=Character attribute to accomplish
that. That works fine except for one little problem. Validation
reports non-racial characters commanding racial units as not
belonging to any valid composition class. I tried first to magnetize
children, but then the non-racial character seems to be treated as a
racial character. In fact, even a racial character doesn't count
toward the limit on characters.
I also tried assigning type:Character to the unit to reflect the
assignment of a character, but that doesn't validate correctly either.
I'm looking for something along the Clan War line where non-native
characters can command native troops (but without the CW oathing).
Just a hint in the right direction would be appreciated.
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Tue, 28 Aug 2001 15:53:06 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: RE: I'm NOT an idiot (really) [maybe I am!]
I would solve this using type-based wildcards. From your description, this
ought to be consistent with your current model, except that you'll need to
scrap the inheritance of the type assignments from the generic units.
Instead, you'll either need generic units for each race or will have to
assign the proper types directly to each unit. Here's my idea....
Instead of using the type names "Troops" and "Character", use the type
names "Unit" and "Char". These shorter names allow this technique to be
used. Then append the RACE to the type name for each unit. For example, if
the race is "Orc", assign the type names "UnitOrc" and "CharOrc" to the
appropriate units. You can now define "trat" attributes that verify the
presence of an Orc character also includes an Orc unit by comparing the
number of "UnitOrc" to the number of "CharOrc". This will work for all
races. Now for the type wildcards (see the manual for more details). You
can define the "list" attribute to use the wildcard designation to get all
characters, which would be "Char?" (the '?' would match characters from
every race). For your "trat" that verifies the two characters per unit
ratio, you would use the types "Char?" and "Unit?", which will generically
match all characters and units, respectively.
This method ought to be easy to implement and is consistent with the model
you've already adopted. Let me know if you have additional questions on it,
or if any of this isn't clear.
Thanks, Rob
At 06:43 PM 8/28/2001 +0000, you wrote:
>Solved the composition class problem (duh). But still can't validate
>requirements for non-racial characters in racial units.
>
>
>From: jizbrand@k...
>Date: Tue Aug 28, 2001 12:20 pm
>Subject: I'm NOT an idiot (really)
>
>
>I'm starting to understand the mindset it takes to make AB work
>correctly, but I'm still having a couple of difficulties.
>
>My files have a number of races, each with characters and units.
>Each unit inherits type:Troops from a generic xUnit. Each character
>inherits type:Character from a generic xChar. I'm trying to model a
>couple of rule restrictions: first, an army can contain a non-racial
>characters but must have at least one troop unit corresponding to the
>same racial type for each character. An army can contain racial
>characters at the rate of two racial characters per racial troop
>unit. I had that covered with trat attributes.
>
>Any character can lead a unit, whether of his own race or any other.
>So I thought I'd use the list:xx*=Character attribute to accomplish
>that. That works fine except for one little problem. Validation
>reports non-racial characters commanding racial units as not
>belonging to any valid composition class. I tried first to magnetize
>children, but then the non-racial character seems to be treated as a
>racial character. In fact, even a racial character doesn't count
>toward the limit on characters.
>
>I also tried assigning type:Character to the unit to reflect the
>assignment of a character, but that doesn't validate correctly either.
>
>I'm looking for something along the Clan War line where non-native
>characters can command native troops (but without the CW oathing).
>Just a hint in the right direction would be appreciated.
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 7
Date: Wed, 29 Aug 2001 00:20:31 -0000
From: jizbrand@kc.rr.com
Subject: Re: RE: I'm NOT an idiot (really) [maybe I am!]
Actually, I had already done that, but backwards, of course (OrcUnit,
ElfChar). So I changed them all, but I'm still having the same
problem (BTW, those types are assigned directly to the units, not
inherited). So here's a more complete description (I hope):
I have two trat's. Here's what it looks like for the Orc race:
trat:TrpsOrc@1u:CharOrc@2m [2 orc characters per native orc unit]
trat:TrpsElf@1u:CharElf@1m [1 elf character per allied elf unit]
For the Elf race, the trat's are reversed:
trat:TrpsOrc@1u:CharOrc@1m [1 orc character per allied orc unit]
trat:TrpsElf@1u:CharElf@2m [2 elf characters per native elf unit]
The tricky part is that an Elf character can be leading an Orc unit
in either army, and vice versa. My list attribute looks like:
list:xx*=Char?, which gives me all the characters for any race.
So far, so good. But no matter what race I pick the leader from,
that leader doesn't get counted against the proper trat.
All units have an option "Assign Leader" which contains just the
list:xx*=Char?
And that's where I'm lost!
--- In armybuilder@y..., Rob Bowes <rob@w...> wrote:
> I would solve this using type-based wildcards. From your
description, this
> ought to be consistent with your current model, except that you'll
need to
> scrap the inheritance of the type assignments from the generic
units.
> Instead, you'll either need generic units for each race or will
have to
> assign the proper types directly to each unit. Here's my idea....
>
> Instead of using the type names "Troops" and "Character", use the
type
> names "Unit" and "Char". These shorter names allow this technique
to be
> used. Then append the RACE to the type name for each unit. For
example, if
> the race is "Orc", assign the type names "UnitOrc" and "CharOrc" to
the
> appropriate units. You can now define "trat" attributes that verify
the
> presence of an Orc character also includes an Orc unit by comparing
the
> number of "UnitOrc" to the number of "CharOrc". This will work for
all
> races. Now for the type wildcards (see the manual for more
details). You
> can define the "list" attribute to use the wildcard designation to
get all
> characters, which would be "Char?" (the '?' would match characters
from
> every race). For your "trat" that verifies the two characters per
unit
> ratio, you would use the types "Char?" and "Unit?", which will
generically
> match all characters and units, respectively.
>
> This method ought to be easy to implement and is consistent with
the model
> you've already adopted. Let me know if you have additional
questions on it,
> or if any of this isn't clear.
>
> Thanks, Rob
>
>
> At 06:43 PM 8/28/2001 +0000, you wrote:
> >Solved the composition class problem (duh). But still can't
validate
> >requirements for non-racial characters in racial units.
> >
> >
> >From: jizbrand@k...
> >Date: Tue Aug 28, 2001 12:20 pm
> >Subject: I'm NOT an idiot (really)
> >
> >
> >I'm starting to understand the mindset it takes to make AB work
> >correctly, but I'm still having a couple of difficulties.
> >
> >My files have a number of races, each with characters and units.
> >Each unit inherits type:Troops from a generic xUnit. Each
character
> >inherits type:Character from a generic xChar. I'm trying to model
a
> >couple of rule restrictions: first, an army can contain a non-
racial
> >characters but must have at least one troop unit corresponding to
the
> >same racial type for each character. An army can contain racial
> >characters at the rate of two racial characters per racial troop
> >unit. I had that covered with trat attributes.
> >
> >Any character can lead a unit, whether of his own race or any
other.
> >So I thought I'd use the list:xx*=Character attribute to accomplish
> >that. That works fine except for one little problem. Validation
> >reports non-racial characters commanding racial units as not
> >belonging to any valid composition class. I tried first to
magnetize
> >children, but then the non-racial character seems to be treated as
a
> >racial character. In fact, even a racial character doesn't count
> >toward the limit on characters.
> >
> >I also tried assigning type:Character to the unit to reflect the
> >assignment of a character, but that doesn't validate correctly
either.
> >
> >I'm looking for something along the Clan War line where non-native
> >characters can command native troops (but without the CW oathing).
> >Just a hint in the right direction would be appreciated.
>
>
> --------------------------------------------------------------------
-------
> Rob Bowes (rob@w...) (650) 726-9689
> Lone Wolf Development
www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 8
Date: Tue, 28 Aug 2001 21:31:39 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: RE: I'm NOT an idiot (really) [maybe I am!]
This more detailed explanation helps a LOT to explain what's going on. So
the problem is that the leaders aren't triggering their validation rules,
right? Then I would guess that you haven't assigned a "forc" attribute to
the characters. Except where explicitly noted otherwise, validation rules
ONLY apply to TOP-LEVEL units. Since the characters are being selected via
options, they are child units. That means their validation rules aren't
being processed. You can force their validation rules to be processed at
all times by including the "forc" attribute.
Hope this helps,
Rob
P.S. Yes, this is flagged in the manual, but it's a common mistake. If you
have a suggestion on how to make this more blatant in the documentation,
please let me know.
At 12:20 AM 8/29/2001 +0000, you wrote:
>Actually, I had already done that, but backwards, of course (OrcUnit,
>ElfChar). So I changed them all, but I'm still having the same
>problem (BTW, those types are assigned directly to the units, not
>inherited). So here's a more complete description (I hope):
>
>I have two trat's. Here's what it looks like for the Orc race:
>
>trat:TrpsOrc@1u:CharOrc@2m [2 orc characters per native orc unit]
>trat:TrpsElf@1u:CharElf@1m [1 elf character per allied elf unit]
>
>For the Elf race, the trat's are reversed:
>
>trat:TrpsOrc@1u:CharOrc@1m [1 orc character per allied orc unit]
>trat:TrpsElf@1u:CharElf@2m [2 elf characters per native elf unit]
>
>The tricky part is that an Elf character can be leading an Orc unit
>in either army, and vice versa. My list attribute looks like:
>
>list:xx*=Char?, which gives me all the characters for any race.
>
>So far, so good. But no matter what race I pick the leader from,
>that leader doesn't get counted against the proper trat.
>
>All units have an option "Assign Leader" which contains just the
>list:xx*=Char?
>
>And that's where I'm lost!
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/