A
armybuilder at egroups.co
Guest
------------------------------------------------------------------------
Big Groups = big savings @ beMANY!
http://click.egroups.com/1/4112/3/_/36190/_/960028405/
------------------------------------------------------------------------
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 5 messages in this issue.
Topics in this digest:
1. Re: Some Complex Augmentation File ?s
From: "Debbie Hunton" <hunton@hotmail.com>
2. Re: Some Complex Augmentation File ?s
From: Rob Bowes <rob@wolflair.com>
3. Re: Some Complex Augmentation File ?s
From: zebuleon@peoplepc.com
4. Re: Re: Some Complex Augmentation File ?s
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
5. Re: Re: Some Complex Augmentation File ?s
From: Rob Bowes <rob@wolflair.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Fri, 02 Jun 2000 21:14:34 GMT
From: "Debbie Hunton" <hunton@hotmail.com>
Subject: Re: Some Complex Augmentation File ?s
I'm trying to set the allies value to 0% for my campaign rules. I tried to
just add the rules with the following:
Race=xx
Attributes: legl:mode=pgc
xbrk:"Campaign"="Ally@0-25"
That didn't work (I get a "one or more data fields are invalid" error), so I
thought I would do it for one race at a time, so I did the following for the
Brettonnians:
Race:br
Attributes: legl:mode=pgc
xbrk:"Campaign"="Lord@?,Ret@?,Ally@0,Cstm@0-25,Mach@0-25"
I get the same error. I've tried replacing "Campaign" with "pgc", but it
didn't make a difference...
What I *really* want to do is change the list of allied races from whatever
they *did* have to a new race I'm creating with the abbreviation mc, but I'm
not sure that will be possible.
But before I can allow any of the races to take units from my Cstm
composition group, I need to be able to adjust the composition group rules.
The only other things besides those that I haven't solved are the following:
1. Allowing all characters access to the mounts I've created for the
footmen.
2. Requiring each army to have a general.
3. Allowing all missile troops except crossbowmen access to an option I'm
creating (flaming ammunition, basically).
Considering the problems I started out with, I'm pretty happy with the
progress I've made with your help.
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Fri, 02 Jun 2000 14:34:11 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Some Complex Augmentation File ?s
At 09:14 PM 6/2/00 +0000, you wrote:
>I'm trying to set the allies value to 0% for my campaign rules. I tried to
>just add the rules with the following:
>
>Race=xx
>Attributes: legl:mode=pgc
> xbrk:"Campaign"="Ally@0-25"
>
>That didn't work (I get a "one or more data fields are invalid" error), so I
>thought I would do it for one race at a time, so I did the following for the
>Brettonnians:
>
>Race:br
>Attributes: legl:mode=pgc
> xbrk:"Campaign"="Lord@?,Ret@?,Ally@0,Cstm@0-25,Mach@0-25"
>
>I get the same error. I've tried replacing "Campaign" with "pgc", but it
>didn't make a difference...
The problem is your use of "legl". You are basically telling AB to make the
race "br" (or "xx") legal only for the mode "pgc". Since the race dictates
the available modes, that doesn't work, so AB is complaining.
If you want to make "xbrk" apply only to a specific mode, use the "-mode="
qualifier on the "xbrk" attribute. Please refer to the syntax for "xbrk" on
this.
Otherwise, your above usage of "xbrk" should be working fine.
>What I *really* want to do is change the list of allied races from whatever
>they *did* have to a new race I'm creating with the abbreviation mc, but I'm
>not sure that will be possible.
There is no way to eliminate allies from an existing race. All you can do
is add them via the "ally" attribute for races.
>But before I can allow any of the races to take units from my Cstm
>composition group, I need to be able to adjust the composition group rules.
>
>The only other things besides those that I haven't solved are the following:
>
>1. Allowing all characters access to the mounts I've created for the
>footmen.
Make sure that your new mounts are assigned to the "Mnt" conflict group.
Then you need to explicitly link each mount to each unit. This is a bit of
a nuisance, but it will work. You need to go to the "Link" tab within ABC
and create new links between each unit and mount. This will be simpler if
you create a new hidden option called "Debbie's Mounts" and designate it as
"debmount". Use the "more" attribute to chain all of your new mounts to
this one option with the link nature "cost". Then all you need to do is
attach "debmount" to all character units via the Link tab and they will
inherit all your mounts at once.
>2. Requiring each army to have a general.
Easy. Use the "need" attribute for races. But I thought this was already
done in the WFB files. Wasn't it??
>3. Allowing all missile troops except crossbowmen access to an option I'm
>creating (flaming ammunition, basically).
Create the option ("flamemsl"). Then use augmentations to attach your new
option to all of the missile weapons that it can be purchased for. For
example, to add the option to the "longbow" option, you'll create an
augmentation record that specifies the attribute "more:flamemsl=cost" for
the "longbow" option. Whenever a longbow is selected a unit, they can then
purchase flaming missiles for it.
>Considering the problems I started out with, I'm pretty happy with the
>progress I've made with your help.
Yeah!
Thanks, Rob
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Fri, 02 Jun 2000 22:50:59 -0000
From: zebuleon@peoplepc.com
Subject: Re: Some Complex Augmentation File ?s
--- In armybuilder@egroups.com, "Debbie Hunton" <hunton@h...> wrote:
> What I *really* want to do is change the list of allied races from
whatever
> they *did* have to a new race I'm creating with the abbreviation
mc,
but I'm
> not sure that will be possible.
I have a suggestion that may or may not help with what your trying to
achieve.
First turn your datadef.wfb into a text file using abundef. Then
open
it and change Warhammer fantasy battles to Warhammer Campaign or some
other name. save it.
Then create a new def file, like datadef.wfc, using abdef.
then go and make a copy of the .wfb files and rename them with the
.wfc extension.
then you can go in to each of the races and delete the listed allies
races and put in the one you want.
This way you have a new file just for your campaign and your original
warhammer files remain unchanged.
If you want to go through all this it should help.
Zebuleon
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Fri, 2 Jun 2000 23:54:25 +0100
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
Subject: Re: Re: Some Complex Augmentation File ?s
One fine day in the middle of the night, zebuleon@peoplepc.com got up to
write:
>--- In armybuilder@egroups.com, "Debbie Hunton" <hunton@h...> wrote:
>
>> What I *really* want to do is change the list of allied races from
>whatever
>> they *did* have to a new race I'm creating with the abbreviation
>mc,
>but I'm
>> not sure that will be possible.
>
>I have a suggestion that may or may not help with what your trying to
>achieve.
>
>First turn your datadef.wfb into a text file using abundef. Then
>open
>it and change Warhammer fantasy battles to Warhammer Campaign or some
>other name. save it.
>
>Then create a new def file, like datadef.wfc, using abdef.
<snip>
The advantage to doing it the more complicated way is that whenever new
stuff gets added to the FB files, Debbie won't need to change hers. This
is why the Augment stuff was added.
--
'Not Colin' McAlister | License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Fri, 02 Jun 2000 20:47:12 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Re: Some Complex Augmentation File ?s
>I have a suggestion that may or may not help with what your trying to
>achieve.
>
>First turn your datadef.wfb into a text file using abundef. Then
>open
>it and change Warhammer fantasy battles to Warhammer Campaign or some
>other name. save it.
>
>Then create a new def file, like datadef.wfc, using abdef.
>
>then go and make a copy of the .wfb files and rename them with the
>.wfc extension.
>
>then you can go in to each of the races and delete the listed allies
>races and put in the one you want.
>
>This way you have a new file just for your campaign and your original
>warhammer files remain unchanged.
>
>If you want to go through all this it should help.
The problem with this approach is that when John releases new updates to
the WFB data files, she'll have to completely re-do all of her changes.
That's why the entire augmentation mechanism was integrated with AB - so
that people can keep their custom changes in separate files and continue to
use updated core files from others.
Thanks, Rob
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Big Groups = big savings @ beMANY!
http://click.egroups.com/1/4112/3/_/36190/_/960028405/
------------------------------------------------------------------------
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 5 messages in this issue.
Topics in this digest:
1. Re: Some Complex Augmentation File ?s
From: "Debbie Hunton" <hunton@hotmail.com>
2. Re: Some Complex Augmentation File ?s
From: Rob Bowes <rob@wolflair.com>
3. Re: Some Complex Augmentation File ?s
From: zebuleon@peoplepc.com
4. Re: Re: Some Complex Augmentation File ?s
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
5. Re: Re: Some Complex Augmentation File ?s
From: Rob Bowes <rob@wolflair.com>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Fri, 02 Jun 2000 21:14:34 GMT
From: "Debbie Hunton" <hunton@hotmail.com>
Subject: Re: Some Complex Augmentation File ?s
I'm trying to set the allies value to 0% for my campaign rules. I tried to
just add the rules with the following:
Race=xx
Attributes: legl:mode=pgc
xbrk:"Campaign"="Ally@0-25"
That didn't work (I get a "one or more data fields are invalid" error), so I
thought I would do it for one race at a time, so I did the following for the
Brettonnians:
Race:br
Attributes: legl:mode=pgc
xbrk:"Campaign"="Lord@?,Ret@?,Ally@0,Cstm@0-25,Mach@0-25"
I get the same error. I've tried replacing "Campaign" with "pgc", but it
didn't make a difference...
What I *really* want to do is change the list of allied races from whatever
they *did* have to a new race I'm creating with the abbreviation mc, but I'm
not sure that will be possible.
But before I can allow any of the races to take units from my Cstm
composition group, I need to be able to adjust the composition group rules.
The only other things besides those that I haven't solved are the following:
1. Allowing all characters access to the mounts I've created for the
footmen.
2. Requiring each army to have a general.
3. Allowing all missile troops except crossbowmen access to an option I'm
creating (flaming ammunition, basically).
Considering the problems I started out with, I'm pretty happy with the
progress I've made with your help.
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Fri, 02 Jun 2000 14:34:11 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Some Complex Augmentation File ?s
At 09:14 PM 6/2/00 +0000, you wrote:
>I'm trying to set the allies value to 0% for my campaign rules. I tried to
>just add the rules with the following:
>
>Race=xx
>Attributes: legl:mode=pgc
> xbrk:"Campaign"="Ally@0-25"
>
>That didn't work (I get a "one or more data fields are invalid" error), so I
>thought I would do it for one race at a time, so I did the following for the
>Brettonnians:
>
>Race:br
>Attributes: legl:mode=pgc
> xbrk:"Campaign"="Lord@?,Ret@?,Ally@0,Cstm@0-25,Mach@0-25"
>
>I get the same error. I've tried replacing "Campaign" with "pgc", but it
>didn't make a difference...
The problem is your use of "legl". You are basically telling AB to make the
race "br" (or "xx") legal only for the mode "pgc". Since the race dictates
the available modes, that doesn't work, so AB is complaining.
If you want to make "xbrk" apply only to a specific mode, use the "-mode="
qualifier on the "xbrk" attribute. Please refer to the syntax for "xbrk" on
this.
Otherwise, your above usage of "xbrk" should be working fine.
>What I *really* want to do is change the list of allied races from whatever
>they *did* have to a new race I'm creating with the abbreviation mc, but I'm
>not sure that will be possible.
There is no way to eliminate allies from an existing race. All you can do
is add them via the "ally" attribute for races.
>But before I can allow any of the races to take units from my Cstm
>composition group, I need to be able to adjust the composition group rules.
>
>The only other things besides those that I haven't solved are the following:
>
>1. Allowing all characters access to the mounts I've created for the
>footmen.
Make sure that your new mounts are assigned to the "Mnt" conflict group.
Then you need to explicitly link each mount to each unit. This is a bit of
a nuisance, but it will work. You need to go to the "Link" tab within ABC
and create new links between each unit and mount. This will be simpler if
you create a new hidden option called "Debbie's Mounts" and designate it as
"debmount". Use the "more" attribute to chain all of your new mounts to
this one option with the link nature "cost". Then all you need to do is
attach "debmount" to all character units via the Link tab and they will
inherit all your mounts at once.
>2. Requiring each army to have a general.
Easy. Use the "need" attribute for races. But I thought this was already
done in the WFB files. Wasn't it??
>3. Allowing all missile troops except crossbowmen access to an option I'm
>creating (flaming ammunition, basically).
Create the option ("flamemsl"). Then use augmentations to attach your new
option to all of the missile weapons that it can be purchased for. For
example, to add the option to the "longbow" option, you'll create an
augmentation record that specifies the attribute "more:flamemsl=cost" for
the "longbow" option. Whenever a longbow is selected a unit, they can then
purchase flaming missiles for it.
>Considering the problems I started out with, I'm pretty happy with the
>progress I've made with your help.
Yeah!
Thanks, Rob
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Fri, 02 Jun 2000 22:50:59 -0000
From: zebuleon@peoplepc.com
Subject: Re: Some Complex Augmentation File ?s
--- In armybuilder@egroups.com, "Debbie Hunton" <hunton@h...> wrote:
> What I *really* want to do is change the list of allied races from
whatever
> they *did* have to a new race I'm creating with the abbreviation
mc,
but I'm
> not sure that will be possible.
I have a suggestion that may or may not help with what your trying to
achieve.
First turn your datadef.wfb into a text file using abundef. Then
open
it and change Warhammer fantasy battles to Warhammer Campaign or some
other name. save it.
Then create a new def file, like datadef.wfc, using abdef.
then go and make a copy of the .wfb files and rename them with the
.wfc extension.
then you can go in to each of the races and delete the listed allies
races and put in the one you want.
This way you have a new file just for your campaign and your original
warhammer files remain unchanged.
If you want to go through all this it should help.
Zebuleon
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Fri, 2 Jun 2000 23:54:25 +0100
From: 'Not Colin' McAlister & The Skrills <demandred@skrill.org>
Subject: Re: Re: Some Complex Augmentation File ?s
One fine day in the middle of the night, zebuleon@peoplepc.com got up to
write:
>--- In armybuilder@egroups.com, "Debbie Hunton" <hunton@h...> wrote:
>
>> What I *really* want to do is change the list of allied races from
>whatever
>> they *did* have to a new race I'm creating with the abbreviation
>mc,
>but I'm
>> not sure that will be possible.
>
>I have a suggestion that may or may not help with what your trying to
>achieve.
>
>First turn your datadef.wfb into a text file using abundef. Then
>open
>it and change Warhammer fantasy battles to Warhammer Campaign or some
>other name. save it.
>
>Then create a new def file, like datadef.wfc, using abdef.
<snip>
The advantage to doing it the more complicated way is that whenever new
stuff gets added to the FB files, Debbie won't need to change hers. This
is why the Augment stuff was added.
--
'Not Colin' McAlister | License to Skrill
Email: demandred@skrill.org | Visit http://www.skrill.org/ today!
-----------------------------+------------------------------------
"Dovie'andi se tovya sagain" - Robert Jordan's Wheel Of Time
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Fri, 02 Jun 2000 20:47:12 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Re: Some Complex Augmentation File ?s
>I have a suggestion that may or may not help with what your trying to
>achieve.
>
>First turn your datadef.wfb into a text file using abundef. Then
>open
>it and change Warhammer fantasy battles to Warhammer Campaign or some
>other name. save it.
>
>Then create a new def file, like datadef.wfc, using abdef.
>
>then go and make a copy of the .wfb files and rename them with the
>.wfc extension.
>
>then you can go in to each of the races and delete the listed allies
>races and put in the one you want.
>
>This way you have a new file just for your campaign and your original
>warhammer files remain unchanged.
>
>If you want to go through all this it should help.
The problem with this approach is that when John releases new updates to
the WFB data files, she'll have to completely re-do all of her changes.
That's why the entire augmentation mechanism was integrated with AB - so
that people can keep their custom changes in separate files and continue to
use updated core files from others.
Thanks, Rob
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
________________________________________________________________________
________________________________________________________________________