• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Problem with the "take" attribute

  • Thread starter Thread starter fusilier at kc.rr.com
  • Start date Start date
F

fusilier at kc.rr.com

Guest
I came across an interesting problem today. I was trying to assign a
take attribute to a unit and couldn't get it to work.

The situation is this: I have a generic class of unit; e.g.,
infantry. The user can pick "infantry" and customize the unit with
weapons, equipment, and skills. I also have a specific unit
called "rangers" which is exactly the same thing as "infantry" except
that I want to specify the exact weapons, equipment, and skills.

No problem for the things that are options. But I can't get it to
take items automatically. What I'm doing is assigning as follows:

take:NOD-perm

Save the record, save the file, switch game systems in AB, select the
rangers unit and NOD does not show up.

I tried the same thing in a couple of other data files for different
games and it worked fine, just not in this data file. And I couldn't
find any substantive differences between those files that worked and
those that didn't.

Any ideas?

Thanks.



------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
Off-hand, I can think of two things it may be.

First, and most likely, make sure that in the NOD entry, you have allowed
the item to be taken by the unit. Set a Special Attribute for this, such
as;
itst:type=infantry

Second, make sure you have allowed the "infantry" unit enough #Items to take
the NOD.

Cheers.
________
--Pr0fane of Dark Age
+++Design Team
+++Demo Teams Coordinator
+++Data Files Maintainer


-----Original Message-----
From: jizbrand [mailto:fusilier@kc.rr.com]
Sent: July 21, 2004 11:23 AM
To: ab@support.wolflair.com
Subject: [AB] Problem with the "take" attribute


I came across an interesting problem today. I was trying to assign a
take attribute to a unit and couldn't get it to work.

The situation is this: I have a generic class of unit; e.g.,
infantry. The user can pick "infantry" and customize the unit with
weapons, equipment, and skills. I also have a specific unit
called "rangers" which is exactly the same thing as "infantry" except
that I want to specify the exact weapons, equipment, and skills.

No problem for the things that are options. But I can't get it to
take items automatically. What I'm doing is assigning as follows:

take:NOD-perm

Save the record, save the file, switch game systems in AB, select the
rangers unit and NOD does not show up.

I tried the same thing in a couple of other data files for different
games and it worked fine, just not in this data file. And I couldn't
find any substantive differences between those files that worked and
those that didn't.

Any ideas?

Thanks.




To unsubscribe from this group, email

armybuilder-unsubscribe@yahoogroups.com
Yahoo! Groups Links








------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
Thanks! I know I have the second; I'll check the first. I'm kind of
puzzled by the whole thing, though, because the item shows up in the
list of items at run-time; it just doesn't automatically attach as I
thought it would.

--- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...> wrote:
> Off-hand, I can think of two things it may be.
>
> First, and most likely, make sure that in the NOD entry, you have
allowed
> the item to be taken by the unit. Set a Special Attribute for
this, such
> as;
> itst:type=infantry
>
> Second, make sure you have allowed the "infantry" unit enough
#Items to take
> the NOD.
>
> Cheers.
> ________
> --Pr0fane of Dark Age
> +++Design Team
> +++Demo Teams Coordinator
> +++Data Files Maintainer
>
>
> -----Original Message-----
> From: jizbrand [mailto:fusilier@k...]
> Sent: July 21, 2004 11:23 AM
> To: armybuilder@yahoogroups.com
> Subject: [AB] Problem with the "take" attribute
>
>
> I came across an interesting problem today. I was trying to assign
a
> take attribute to a unit and couldn't get it to work.
>
> The situation is this: I have a generic class of unit; e.g.,
> infantry. The user can pick "infantry" and customize the unit with
> weapons, equipment, and skills. I also have a specific unit
> called "rangers" which is exactly the same thing as "infantry"
except
> that I want to specify the exact weapons, equipment, and skills.
>
> No problem for the things that are options. But I can't get it to
> take items automatically. What I'm doing is assigning as follows:
>
> take:NOD-perm
>
> Save the record, save the file, switch game systems in AB, select
the
> rangers unit and NOD does not show up.
>
> I tried the same thing in a couple of other data files for different
> games and it worked fine, just not in this data file. And I
couldn't
> find any substantive differences between those files that worked and
> those that didn't.
>
> Any ideas?
>
> Thanks.
>
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@yahoogroups.com
> Yahoo! Groups Links



------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
Oh, I thought of one other thing it may be.

On the Unit tab, under Local Attributes for the "infantry" unit, ensure that
your first attribute is;
spec:+weap

Where "+weap" is the category of item that NOD is in.

________
--Pr0fane of Dark Age
+++Design Team
+++Demo Teams Coordinator
+++Data Files Maintainer


-----Original Message-----
From: jizbrand [mailto:fusilier@kc.rr.com]
Sent: July 21, 2004 4:54 PM
To: ab@support.wolflair.com
Subject: Re: [AB] Problem with the "take" attribute


Thanks! I know I have the second; I'll check the first. I'm kind of
puzzled by the whole thing, though, because the item shows up in the
list of items at run-time; it just doesn't automatically attach as I
thought it would.

--- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...> wrote:
> Off-hand, I can think of two things it may be.
>
> First, and most likely, make sure that in the NOD entry, you have
allowed
> the item to be taken by the unit. Set a Special Attribute for
this, such
> as;
> itst:type=infantry
>
> Second, make sure you have allowed the "infantry" unit enough
#Items to take
> the NOD.
>
> Cheers.
> ________
> --Pr0fane of Dark Age
> +++Design Team
> +++Demo Teams Coordinator
> +++Data Files Maintainer
>
>
> -----Original Message-----
> From: jizbrand [mailto:fusilier@k...]
> Sent: July 21, 2004 11:23 AM
> To: armybuilder@yahoogroups.com
> Subject: [AB] Problem with the "take" attribute
>
>
> I came across an interesting problem today. I was trying to assign
a
> take attribute to a unit and couldn't get it to work.
>
> The situation is this: I have a generic class of unit; e.g.,
> infantry. The user can pick "infantry" and customize the unit with
> weapons, equipment, and skills. I also have a specific unit
> called "rangers" which is exactly the same thing as "infantry"
except
> that I want to specify the exact weapons, equipment, and skills.
>
> No problem for the things that are options. But I can't get it to
> take items automatically. What I'm doing is assigning as follows:
>
> take:NOD-perm
>
> Save the record, save the file, switch game systems in AB, select
the
> rangers unit and NOD does not show up.
>
> I tried the same thing in a couple of other data files for different
> games and it worked fine, just not in this data file. And I
couldn't
> find any substantive differences between those files that worked and
> those that didn't.
>
> Any ideas?
>
> Thanks.
>
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@yahoogroups.com
> Yahoo! Groups Links




To unsubscribe from this group, email

armybuilder-unsubscribe@yahoogroups.com
Yahoo! Groups Links







------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
Well, I tried them all and none worked. The definition file is set
up so that the unit can take the required item. And, indeed, when I
select that unit, I can go to the items icon and the item will show
up in the list and allow me to assign it to the unit.

But, using that take attribute, the item does not get automatically
assigned. I'm stumped. Is it possible that some kind of corruption
exists in the data file that prevents the attribute from working
properly?

--- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...> wrote:
> Oh, I thought of one other thing it may be.
>
> On the Unit tab, under Local Attributes for the "infantry" unit,
ensure that
> your first attribute is;
> spec:+weap
>
> Where "+weap" is the category of item that NOD is in.
>
> ________
> --Pr0fane of Dark Age
> +++Design Team
> +++Demo Teams Coordinator
> +++Data Files Maintainer
>
>
> -----Original Message-----
> From: jizbrand [mailto:fusilier@k...]
> Sent: July 21, 2004 4:54 PM
> To: armybuilder@yahoogroups.com
> Subject: Re: [AB] Problem with the "take" attribute
>
>
> Thanks! I know I have the second; I'll check the first. I'm kind
of
> puzzled by the whole thing, though, because the item shows up in the
> list of items at run-time; it just doesn't automatically attach as I
> thought it would.
>
> --- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...> wrote:
> > Off-hand, I can think of two things it may be.
> >
> > First, and most likely, make sure that in the NOD entry, you have
> allowed
> > the item to be taken by the unit. Set a Special Attribute for
> this, such
> > as;
> > itst:type=infantry
> >
> > Second, make sure you have allowed the "infantry" unit enough
> #Items to take
> > the NOD.
> >
> > Cheers.
> > ________
> > --Pr0fane of Dark Age
> > +++Design Team
> > +++Demo Teams Coordinator
> > +++Data Files Maintainer
> >
> >
> > -----Original Message-----
> > From: jizbrand [mailto:fusilier@k...]
> > Sent: July 21, 2004 11:23 AM
> > To: armybuilder@yahoogroups.com
> > Subject: [AB] Problem with the "take" attribute
> >
> >
> > I came across an interesting problem today. I was trying to
assign
> a
> > take attribute to a unit and couldn't get it to work.
> >
> > The situation is this: I have a generic class of unit; e.g.,
> > infantry. The user can pick "infantry" and customize the unit
with
> > weapons, equipment, and skills. I also have a specific unit
> > called "rangers" which is exactly the same thing as "infantry"
> except
> > that I want to specify the exact weapons, equipment, and skills.
> >
> > No problem for the things that are options. But I can't get it to
> > take items automatically. What I'm doing is assigning as follows:
> >
> > take:NOD-perm
> >
> > Save the record, save the file, switch game systems in AB, select
> the
> > rangers unit and NOD does not show up.
> >
> > I tried the same thing in a couple of other data files for
different
> > games and it worked fine, just not in this data file. And I
> couldn't
> > find any substantive differences between those files that worked
and
> > those that didn't.
> >
> > Any ideas?
> >
> > Thanks.
> >
> >
> >
> >
> > To unsubscribe from this group, email
> >
> > armybuilder-unsubscribe@yahoogroups.com
> > Yahoo! Groups Links
>
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@yahoogroups.com
> Yahoo! Groups Links



------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
Corruption is highly doubtful.

Make sure that the unit is not limited in some way by an ipts attribute. If you want, you can email me the files as an attachment off-list, and I will have a quick peek at them.

Cheers,

jizbrand <fusilier@kc.rr.com> wrote:
Well, I tried them all and none worked. The definition file is set
up so that the unit can take the required item. And, indeed, when I
select that unit, I can go to the items icon and the item will show
up in the list and allow me to assign it to the unit.

But, using that take attribute, the item does not get automatically
assigned. I'm stumped. Is it possible that some kind of corruption
exists in the data file that prevents the attribute from working
properly?

--- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...> wrote:
> Oh, I thought of one other thing it may be.
>
> On the Unit tab, under Local Attributes for the "infantry" unit,
ensure that
> your first attribute is;
> spec:+weap
>
> Where "+weap" is the category of item that NOD is in.
>
> ________
> --Pr0fane of Dark Age
> +++Design Team
> +++Demo Teams Coordinator
> +++Data Files Maintainer
>
>
> -----Original Message-----
> From: jizbrand [mailto:fusilier@k...]
> Sent: July 21, 2004 4:54 PM
> To: armybuilder@yahoogroups.com
> Subject: Re: [AB] Problem with the "take" attribute
>
>
> Thanks! I know I have the second; I'll check the first. I'm kind
of
> puzzled by the whole thing, though, because the item shows up in the
> list of items at run-time; it just doesn't automatically attach as I
> thought it would.
>
> --- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...> wrote:
> > Off-hand, I can think of two things it may be.
> >
> > First, and most likely, make sure that in the NOD entry, you have
> allowed
> > the item to be taken by the unit. Set a Special Attribute for
> this, such
> > as;
> > itst:type=infantry
> >
> > Second, make sure you have allowed the "infantry" unit enough
> #Items to take
> > the NOD.
> >
> > Cheers.
> > ________
> > --Pr0fane of Dark Age
> > +++Design Team
> > +++Demo Teams Coordinator
> > +++Data Files Maintainer
> >
> >
> > -----Original Message-----
> > From: jizbrand [mailto:fusilier@k...]
> > Sent: July 21, 2004 11:23 AM
> > To: armybuilder@yahoogroups.com
> > Subject: [AB] Problem with the "take" attribute
> >
> >
> > I came across an interesting problem today. I was trying to
assign
> a
> > take attribute to a unit and couldn't get it to work.
> >
> > The situation is this: I have a generic class of unit; e.g.,
> > infantry. The user can pick "infantry" and customize the unit
with
> > weapons, equipment, and skills. I also have a specific unit
> > called "rangers" which is exactly the same thing as "infantry"
> except
> > that I want to specify the exact weapons, equipment, and skills.
> >
> > No problem for the things that are options. But I can't get it to
> > take items automatically. What I'm doing is assigning as follows:
> >
> > take:NOD-perm
> >
> > Save the record, save the file, switch game systems in AB, select
> the
> > rangers unit and NOD does not show up.
> >
> > I tried the same thing in a couple of other data files for
different
> > games and it worked fine, just not in this data file. And I
> couldn't
> > find any substantive differences between those files that worked
and
> > those that didn't.
> >
> > Any ideas?
> >
> > Thanks.
> >
> >
> >
> >
> > To unsubscribe from this group, email
> >
> > armybuilder-unsubscribe@yahoogroups.com
> > Yahoo! Groups Links
>
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@yahoogroups.com
> Yahoo! Groups Links



To unsubscribe from this group, email

armybuilder-unsubscribe@yahoogroups.com


Yahoo! Groups SponsorADVERTISEMENT


---------------------------------
Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/armybuilder/

To unsubscribe from this group, send an email to:
armybuilder-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



--
Graham Tracey
(Imhotep The Architect)
http://ab40k3.homelinux.net : 40k Datafile Tech Support Site


---------------------------------
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!

[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
Thanks so much for the offer. I've found a workaround (I'm not
entirely happy with it, but it works). I assign a hidden option to
the unit; the option makes the mods to the stat line directly rather
than assigning the item. Seems to work.

--- In armybuilder@yahoogroups.com, ImhotepTheArchitect
<imhotepthearchitect@y...> wrote:
> Corruption is highly doubtful.
>
> Make sure that the unit is not limited in some way by an ipts
attribute. If you want, you can email me the files as an attachment
off-list, and I will have a quick peek at them.
>
> Cheers,
>
> jizbrand <fusilier@k...> wrote:
> Well, I tried them all and none worked. The definition file is set
> up so that the unit can take the required item. And, indeed, when
I
> select that unit, I can go to the items icon and the item will show
> up in the list and allow me to assign it to the unit.
>
> But, using that take attribute, the item does not get automatically
> assigned. I'm stumped. Is it possible that some kind of
corruption
> exists in the data file that prevents the attribute from working
> properly?
>
> --- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...> wrote:
> > Oh, I thought of one other thing it may be.
> >
> > On the Unit tab, under Local Attributes for the "infantry" unit,
> ensure that
> > your first attribute is;
> > spec:+weap
> >
> > Where "+weap" is the category of item that NOD is in.
> >
> > ________
> > --Pr0fane of Dark Age
> > +++Design Team
> > +++Demo Teams Coordinator
> > +++Data Files Maintainer
> >
> >
> > -----Original Message-----
> > From: jizbrand [mailto:fusilier@k...]
> > Sent: July 21, 2004 4:54 PM
> > To: armybuilder@yahoogroups.com
> > Subject: Re: [AB] Problem with the "take" attribute
> >
> >
> > Thanks! I know I have the second; I'll check the first. I'm
kind
> of
> > puzzled by the whole thing, though, because the item shows up in
the
> > list of items at run-time; it just doesn't automatically attach
as I
> > thought it would.
> >
> > --- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...>
wrote:
> > > Off-hand, I can think of two things it may be.
> > >
> > > First, and most likely, make sure that in the NOD entry, you
have
> > allowed
> > > the item to be taken by the unit. Set a Special Attribute for
> > this, such
> > > as;
> > > itst:type=infantry
> > >
> > > Second, make sure you have allowed the "infantry" unit enough
> > #Items to take
> > > the NOD.
> > >
> > > Cheers.
> > > ________
> > > --Pr0fane of Dark Age
> > > +++Design Team
> > > +++Demo Teams Coordinator
> > > +++Data Files Maintainer
> > >
> > >
> > > -----Original Message-----
> > > From: jizbrand [mailto:fusilier@k...]
> > > Sent: July 21, 2004 11:23 AM
> > > To: armybuilder@yahoogroups.com
> > > Subject: [AB] Problem with the "take" attribute
> > >
> > >
> > > I came across an interesting problem today. I was trying to
> assign
> > a
> > > take attribute to a unit and couldn't get it to work.
> > >
> > > The situation is this: I have a generic class of unit; e.g.,
> > > infantry. The user can pick "infantry" and customize the unit
> with
> > > weapons, equipment, and skills. I also have a specific unit
> > > called "rangers" which is exactly the same thing as "infantry"
> > except
> > > that I want to specify the exact weapons, equipment, and skills.
> > >
> > > No problem for the things that are options. But I can't get it
to
> > > take items automatically. What I'm doing is assigning as
follows:
> > >
> > > take:NOD-perm
> > >
> > > Save the record, save the file, switch game systems in AB,
select
> > the
> > > rangers unit and NOD does not show up.
> > >
> > > I tried the same thing in a couple of other data files for
> different
> > > games and it worked fine, just not in this data file. And I
> > couldn't
> > > find any substantive differences between those files that
worked
> and
> > > those that didn't.
> > >
> > > Any ideas?
> > >
> > > Thanks.
> > >
> > >
> > >
> > >
> > > To unsubscribe from this group, email
> > >
> > > armybuilder-unsubscribe@yahoogroups.com
> > > Yahoo! Groups Links
> >
> >
> >
> >
> > To unsubscribe from this group, email
> >
> > armybuilder-unsubscribe@yahoogroups.com
> > Yahoo! Groups Links
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@yahoogroups.com
>
>
> Yahoo! Groups SponsorADVERTISEMENT
>
>
> ---------------------------------
> Yahoo! Groups Links
>
> To visit your group on the web, go to:
> http://groups.yahoo.com/group/armybuilder/
>
> To unsubscribe from this group, send an email to:
> armybuilder-unsubscribe@yahoogroups.com
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
>
>
>
> --
> Graham Tracey
> (Imhotep The Architect)
> http://ab40k3.homelinux.net : 40k Datafile Tech Support Site
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other providers!
>
> [Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
One thing to look at. In your datadef, your item categories are linked to to unit categories. For example, if the two units you referred to are of a different unit category. Example from 40k dae for daemons and hq for well... hq: an item that is in an item category marked as available only to hq will not be given to a daemon even with a take attribute. The deamon must be given a spec +hq attribute as well to be able to access the item.

Hope that helps you get it done the way you want.

Cheers,
Graham

jizbrand <fusilier@kc.rr.com> wrote:
Thanks so much for the offer. I've found a workaround (I'm not
entirely happy with it, but it works). I assign a hidden option to
the unit; the option makes the mods to the stat line directly rather
than assigning the item. Seems to work.


--
Graham Tracey
(Imhotep The Architect)
http://ab40k3.homelinux.net : 40k Datafile Tech Support Site


---------------------------------
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!

[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
And another weirdness. Take just doesn't work with this set of files
at all. In my personal files for other game systems, it works fine.

So, I tried adding an Option that also had the take attribute,
figuring that I could assign the option as auto with the option
hidden, and that would force the item to be automatically added.
That doesn't work either.

I'm so confused!

--- In armybuilder@yahoogroups.com, "jizbrand" <fusilier@k...> wrote:
> Well, I tried them all and none worked. The definition file is set
> up so that the unit can take the required item. And, indeed, when
I
> select that unit, I can go to the items icon and the item will show
> up in the list and allow me to assign it to the unit.
>
> But, using that take attribute, the item does not get automatically
> assigned. I'm stumped. Is it possible that some kind of
corruption
> exists in the data file that prevents the attribute from working
> properly?
>
> --- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...> wrote:
> > Oh, I thought of one other thing it may be.
> >
> > On the Unit tab, under Local Attributes for the "infantry" unit,
> ensure that
> > your first attribute is;
> > spec:+weap
> >
> > Where "+weap" is the category of item that NOD is in.
> >
> > ________
> > --Pr0fane of Dark Age
> > +++Design Team
> > +++Demo Teams Coordinator
> > +++Data Files Maintainer
> >
> >
> > -----Original Message-----
> > From: jizbrand [mailto:fusilier@k...]
> > Sent: July 21, 2004 4:54 PM
> > To: armybuilder@yahoogroups.com
> > Subject: Re: [AB] Problem with the "take" attribute
> >
> >
> > Thanks! I know I have the second; I'll check the first. I'm
kind
> of
> > puzzled by the whole thing, though, because the item shows up in
the
> > list of items at run-time; it just doesn't automatically attach
as I
> > thought it would.
> >
> > --- In armybuilder@yahoogroups.com, "Pr0fane" <pr0fane@s...>
wrote:
> > > Off-hand, I can think of two things it may be.
> > >
> > > First, and most likely, make sure that in the NOD entry, you
have
> > allowed
> > > the item to be taken by the unit. Set a Special Attribute for
> > this, such
> > > as;
> > > itst:type=infantry
> > >
> > > Second, make sure you have allowed the "infantry" unit enough
> > #Items to take
> > > the NOD.
> > >
> > > Cheers.
> > > ________
> > > --Pr0fane of Dark Age
> > > +++Design Team
> > > +++Demo Teams Coordinator
> > > +++Data Files Maintainer
> > >
> > >
> > > -----Original Message-----
> > > From: jizbrand [mailto:fusilier@k...]
> > > Sent: July 21, 2004 11:23 AM
> > > To: armybuilder@yahoogroups.com
> > > Subject: [AB] Problem with the "take" attribute
> > >
> > >
> > > I came across an interesting problem today. I was trying to
> assign
> > a
> > > take attribute to a unit and couldn't get it to work.
> > >
> > > The situation is this: I have a generic class of unit; e.g.,
> > > infantry. The user can pick "infantry" and customize the unit
> with
> > > weapons, equipment, and skills. I also have a specific unit
> > > called "rangers" which is exactly the same thing as "infantry"
> > except
> > > that I want to specify the exact weapons, equipment, and skills.
> > >
> > > No problem for the things that are options. But I can't get it
to
> > > take items automatically. What I'm doing is assigning as
follows:
> > >
> > > take:NOD-perm
> > >
> > > Save the record, save the file, switch game systems in AB,
select
> > the
> > > rangers unit and NOD does not show up.
> > >
> > > I tried the same thing in a couple of other data files for
> different
> > > games and it worked fine, just not in this data file. And I
> > couldn't
> > > find any substantive differences between those files that
worked
> and
> > > those that didn't.
> > >
> > > Any ideas?
> > >
> > > Thanks.
> > >
> > >
> > >
> > >
> > > To unsubscribe from this group, email
> > >
> > > armybuilder-unsubscribe@yahoogroups.com
> > > Yahoo! Groups Links
> >
> >
> >
> >
> > To unsubscribe from this group, email
> >
> > armybuilder-unsubscribe@yahoogroups.com
> > Yahoo! Groups Links




------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~->
 
You must log in or register to reply here.
Back
Top