Guest
Posts: n/a
|
Hi,
I have come across an interesting problem and was wondering if I am going quietly mad or if there is a way round it. I have a main unit (Infantry Battalion) which is linked to several child units (HQ, gun company, etc) via an option - this works fine. Because I do not want the child units to be selectable individually, I have added the 'x' to the front of their unique id. Since I also want the child units to start off with certain items, I have linked these to the specific child units via options and the 'take' syntax. When running the resulting file within Army builder, the defaulted items are not allocated to the child units, nor am I able to assign the items manually (I get the 'Cannot currently be given any items' message). The parent and each child unit has the number of allowed items set to 9999. If, however, I return to the creator package and remove the 'x' from the unique id on the child units, then my items are included on the child units when I pick the parent unit (excellent), but the child units are also selectable individually within the system (not so excellent). Anyone know of a way round this ? (I'm running version 2.2c) Cheers, Simon. [Non-text portions of this message have been removed] ------------------------ Yahoo! Groups Sponsor ---------------------~--> Buy Stock for $4 and no minimums. FREE Money 2002. http://us.click.yahoo.com/k6cvND/n97...SFAA/IMSolB/TM ---------------------------------------------------------------------~-> |
#1 |
Guest
Posts: n/a
|
If you add the Ex. attribute "hide" to the child units, that should remove them form the list of units at the top of AB. The user will never be able to select those child units unless another unit gives them the option to select them. Hope this helps.
Thanks, Keith ----- Original Message ----- From: Simon Day To: Army Builder List Sent: Sunday, April 14, 2002 2:55 PM Subject: [AB] Attaching items to child units Hi, I have come across an interesting problem and was wondering if I am going quietly mad or if there is a way round it. I have a main unit (Infantry Battalion) which is linked to several child units (HQ, gun company, etc) via an option - this works fine. Because I do not want the child units to be selectable individually, I have added the 'x' to the front of their unique id. Since I also want the child units to start off with certain items, I have linked these to the specific child units via options and the 'take' syntax. When running the resulting file within Army builder, the defaulted items are not allocated to the child units, nor am I able to assign the items manually (I get the 'Cannot currently be given any items' message). The parent and each child unit has the number of allowed items set to 9999. If, however, I return to the creator package and remove the 'x' from the unique id on the child units, then my items are included on the child units when I pick the parent unit (excellent), but the child units are also selectable individually within the system (not so excellent). Anyone know of a way round this ? (I'm running version 2.2c) Cheers, Simon. [Non-text portions of this message have been removed] Yahoo! Groups Sponsor ADVERTISEMENT To unsubscribe from this group, email armybuilder-unsubscribe@egroups.com Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. [Non-text portions of this message have been removed] ------------------------ Yahoo! Groups Sponsor ---------------------~--> Buy Stock for $4 and no minimums. FREE Money 2002. http://us.click.yahoo.com/k6cvND/n97...SFAA/IMSolB/TM ---------------------------------------------------------------------~-> |
#2 |
Guest
Posts: n/a
|
It is docuemnted that units without a valid race prefix (ie.
starting with x) cannot take items. As Keith suggested, use the hide attribute. Cheers, Russell. --- In armybuilder@y..., "Keith" <mobo@a...> wrote: > If you add the Ex. attribute "hide" to the child units, that should remove them form the list of units at the top of AB. The user will never be able to select those child units unless another unit gives them the option to select them. Hope this helps. > > ----- Original Message ----- > From: Simon Day > To: Army Builder List > Sent: Sunday, April 14, 2002 2:55 PM > Subject: [AB] Attaching items to child units > > > Hi, > > I have come across an interesting problem and was wondering if I am going quietly mad or if there is a way round it. > > I have a main unit (Infantry Battalion) which is linked to several child units (HQ, gun company, etc) via an option - this works fine. Because I do not want the child units to be selectable individually, I have added the 'x' to the front of their unique id. > > Since I also want the child units to start off with certain items, I have linked these to the specific child units via options and the 'take' syntax. > ------------------------ Yahoo! Groups Sponsor ---------------------~--> Buy Stock for $4 and no minimums. FREE Money 2002. http://us.click.yahoo.com/orkH0C/n97...SFAA/IMSolB/TM ---------------------------------------------------------------------~-> |
#3 |
Guest
Posts: n/a
|
Thanks guys - I'll give that a try.
Cheers, Simon Day > -----Original Message----- > From: rjsoz [SMTP:rjs@inorbit.com] > Sent: 15 April 2002 07:44 > To: armybuilder@yahoogroups.com > Subject: Re: [AB] Attaching items to child units > > It is docuemnted that units without a valid race prefix (ie. > starting with x) cannot take items. As Keith suggested, use the hide > attribute. > > Cheers, > Russell. > > --- In armybuilder@y..., "Keith" <mobo@a...> wrote: > > If you add the Ex. attribute "hide" to the child units, that > should remove them form the list of units at the top of AB. The > user will never be able to select those child units unless another > unit gives them the option to select them. Hope this helps. > > > > ----- Original Message ----- > > From: Simon Day > > To: Army Builder List > > Sent: Sunday, April 14, 2002 2:55 PM > > Subject: [AB] Attaching items to child units > > > > > > Hi, > > > > I have come across an interesting problem and was wondering if I > am going quietly mad or if there is a way round it. > > > > I have a main unit (Infantry Battalion) which is linked to > several child units (HQ, gun company, etc) via an option - this > works fine. Because I do not want the child units to be selectable > individually, I have added the 'x' to the front of their unique id. > > > > Since I also want the child units to start off with certain > items, I have linked these to the specific child units via options > and the 'take' syntax. > > > > > > > To unsubscribe from this group, email > > armybuilder-unsubscribe@egroups.com > > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > > > > __________________________________________________ ______________________ > This email has been scanned for all viruses by the MessageLabs SkyScan > service. For more information on a proactive anti-virus service working > around the clock, around the globe, visit http://www.messagelabs.com > __________________________________________________ ______________________ __________________________________________________ ______________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com __________________________________________________ ______________________ ------------------------ Yahoo! Groups Sponsor ---------------------~--> Buy Stock for $4 and no minimums. FREE Money 2002. http://us.click.yahoo.com/orkH0C/n97...SFAA/IMSolB/TM ---------------------------------------------------------------------~-> |
#4 |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Multiple child units | Damix | Army Builder | 4 | August 28th, 2007 03:52 PM |
Issuses with child units. | rkajdi | Army Builder | 4 | August 23rd, 2006 01:44 AM |
More fun with AB3 child units. | Warmonger | Army Builder | 3 | February 9th, 2005 01:55 PM |
Attaching Units to Units | schreiber at freek-inc.co | Army Builder | 3 | January 10th, 2000 03:30 AM |