• 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

One option, entire army?

  • Thread starter Thread starter rjs at inorbit.com
  • Start date Start date
R

rjs at inorbit.com

Guest
This may have been asked before...
Is there any way to, when an option is selected for a particular
unit, that option is then automatically made available and selected
for every other unit in the army?

It's a long shot I know :-)

Russell.


-------------------------- eGroups Sponsor -------------------------~-~>
Create your business web site your way now at Bigstep.com.
It's the fast, easy way to get online, to promote your business,
and to sell your products and services. Try Bigstep.com now.
http://click.egroups.com/1/9183/1/_/36190/_/974844135/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
One fine day in the middle of the night, Rus1sell Sparkes
<rjs@inorbit.com> got up to write:

>This may have been asked before...
>Is there any way to, when an option is selected for a particular
>unit, that option is then automatically made available and selected
>for every other unit in the army?
>
>It's a long shot I know :-)

Nope.

Sorry :)

What are you trying to do? The "tloc" attribute and / or the -istype
qualifier may be of some help to you...

--
'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

-------------------------- eGroups Sponsor -------------------------~-~>
Create your business web site your way now at Bigstep.com.
It's the fast, easy way to get online, to promote your business,
and to sell your products and services. Try Bigstep.com now.
http://click.egroups.com/1/9183/1/_/36190/_/974846306/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
--- In armybuilder@egroups.com, 'Not Colin' McAlister & The Skrills
<demandred@s...> wrote:
>
> >This may have been asked before...
> >Is there any way to, when an option is selected for a particular
> >unit, that option is then automatically made available and
> >selected for every other unit in the army?
> >
>
> What are you trying to do? The "tloc" attribute and / or the -istype
> qualifier may be of some help to you...

For Crucible, the Thane Druid can take a spell which costs x points
per model. If taken, it must be taken (and costed) for every model in
the army.

Ideas?

Russell.


-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/36190/_/974847127/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
> For Crucible, the Thane Druid can take a spell which costs x points
> per model. If taken, it must be taken (and costed) for every model in
> the army.
Army Builder already keeps track of the number of models in the army. I
would guess that it's a variable kept somewhere. Just use that. Having
said that, I don't have any more of a idea. :)

-Michael


-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/36190/_/974847877/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
One fine day in the middle of the night, Russell Sparkes
<rjs@inorbit.com> got up to write:

>--- In armybuilder@egroups.com, 'Not Colin' McAlister & The Skrills
><demandred@s...> wrote:
>>
>> >This may have been asked before...
>> >Is there any way to, when an option is selected for a particular
>> >unit, that option is then automatically made available and
>> >selected for every other unit in the army?
>> >
>>
>> What are you trying to do? The "tloc" attribute and / or the -istype
>> qualifier may be of some help to you...
>
>For Crucible, the Thane Druid can take a spell which costs x points
>per model. If taken, it must be taken (and costed) for every model in
>the army.

There's no "nice" way to do this... the only way I can think of is have
an option that's always available to every unit, but throws up
validation errors when you take invalid combinations (i.e., it must be
all or nothing, and a Thane Druid must be required). Would that be
adequate?

--
'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

-------------------------- eGroups Sponsor -------------------------~-~>
eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9699/1/_/36190/_/974848590/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
--- In armybuilder@egroups.com, 'Not Colin' McAlister & The Skrills
<demandred@s...> wrote:
> One fine day in the middle of the night, Russell Sparkes
> <rjs@i...> got up to write:
> >
> >For Crucible, the Thane Druid can take a spell which costs x
> >points per model. If taken, it must be taken (and costed) for
> >every model in the army.
>
> There's no "nice" way to do this... the only way I can think of is
> have an option that's always available to every unit, but throws
> up validation errors when you take invalid combinations (i.e., it
> must be all or nothing, and a Thane Druid must be required). Would
> that be adequate?

Yuck. I had already thought of that and hoped there was another way.
Hopefully Rob will have a scathingly brilliant idea :-) Rob?
(he says hopefully :-)

Thanks,
Russell.


-------------------------- eGroups Sponsor -------------------------~-~>
Create your business web site your way now at Bigstep.com.
It's the fast, easy way to get online, to promote your business,
and to sell your products and services. Try Bigstep.com now.
http://click.egroups.com/1/9183/1/_/36190/_/974848903/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
--- In armybuilder@egroups.com, I wrote:
>
> Yuck. I had already thought of that and hoped there was another way.
> Hopefully Rob will have a scathingly brilliant idea :-) Rob?
> (he says hopefully :-)

Rob had no better ideas :-(

Thanks for your ideas people,
Russell


-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/36190/_/974861890/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
At 02:58 AM 11/22/00 +0000, you wrote:
>--- In armybuilder@egroups.com, I wrote:
> >
> > Yuck. I had already thought of that and hoped there was another way.
> > Hopefully Rob will have a scathingly brilliant idea :-) Rob?
> > (he says hopefully :-)
>
>Rob had no better ideas :-(

Hey! I thought that my idea was at least a LITTLE better - at least from
the user's perspective. :-)

Now, I admit my idea wasn't "scathingly brilliant". Heck, it doesn't even
qualify as mediocre. :-) But it didn't require the as much hoop-junping for
the user. :-)

Just nitpicking.... :-> It's been a weird last couple of days.....

Later, Rob

---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com

-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/36190/_/974928779/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
--- In armybuilder@egroups.com, Rob Bowes <rob@w...> wrote:
> At 02:58 AM 11/22/00 +0000, you wrote:
> >--- In armybuilder@egroups.com, I wrote:
> >Rob had no better ideas :-(
>
> Hey! I thought that my idea was at least a LITTLE better - at least
> from the user's perspective. :-)
>
> Now, I admit my idea wasn't "scathingly brilliant". Heck, it
> doesn't even qualify as mediocre. :-) But it didn't require
> as much hoop-junping for the user. :-)

Is there a way to flag a validation error if I take the option for
one unit but not all? Assume I have the option assign a type:Mist.
I'd like the army to contain 0% type Mist, or 100% type Mist. I
couldn't really figure out how to do this with trat: or tlmt:
Maybe it's not possible?

Russell.


-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/36190/_/974941318/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
While I don't like the approach where the option must be selected for every
unit, it's the only way to solve the problem in a validated fashion. I
don't like it because it is a ROYAL nuisance for the user. :-)

However, if you are going to implement it that way, the best solution I can
come up with is as follows:

1. When the spell is selected for the Druid, assign him the type "Mist".
2. For all units in the army, have the option available for selection.
3. For all units in the army, use a "must" attribute with a min=1 and an
"istype=Mist". This ensures that the option is selected for everyone if the
Druid takes the spell.
4. Do the same as #3 with a max=0 and an "istype=!Mist". This ensures that
the option is NOT selected by anyone if the Druid does not take the spell.

Hope this helps,
Rob


At 01:01 AM 11/23/00 +0000, you wrote:
>Is there a way to flag a validation error if I take the option for
>one unit but not all? Assume I have the option assign a type:Mist.
>I'd like the army to contain 0% type Mist, or 100% type Mist. I
>couldn't really figure out how to do this with trat: or tlmt:
>Maybe it's not possible?
>
>Russell.


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com

-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/36190/_/974944293/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
--- In armybuilder@egroups.com, Rob Bowes <rob@w...> wrote:
> While I don't like the approach where the option must be selected
> for every unit, it's the only way to solve the problem in a
> validated fashion. I don't like it because it is a ROYAL nuisance
> for the user. :-)
>
> However, if you are going to implement it that way, the best
> solution I can come up with is as follows:
>
> 1. When the spell is selected for the Druid, assign him the
> type "Mist".
> 2. For all units in the army, have the option available for
> selection.
> 3. For all units in the army, use a "must" attribute with a min=1
> and an "istype=Mist". This ensures that the option is selected for
> everyone if the Druid takes the spell.
> 4. Do the same as #3 with a max=0 and an "istype=!Mist". This
> ensures that the option is NOT selected by anyone if the Druid
> does not take the spell.
>
As it turns out, The Druid is using Warp Magic, so it needs to be
setup like the Goblins. ie. Each spell is assigned to a specific unit
at design time. The Mist of Norka is therefore not something taken by
the Druid specifically, but more taken for each unit.
Here I was, trying to figure out a race attribute to do the
validation, when there's a perfectly good unit one :-)

Thanks Rob, that's just what I was after. I know it may not be ideal,
but at least it'll be validated.

Russell.


-------------------------- eGroups Sponsor -------------------------~-~>
Create your business web site your way now at Bigstep.com.
It's the fast, easy way to get online, to promote your business,
and to sell your products and services. Try Bigstep.com now.
http://click.egroups.com/1/9183/1/_/36190/_/975017067/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
--- In armybuilder@egroups.com, Rob Bowes <rob@w...> wrote:
> I believe that "istype" didn't properly recognize the "!" form in
> the original V2.0 release. This means you should flag to users
> that they need the latest version of AB (and ABLite) to use the
> Principate data files.
>
> Thanks, Rob

Will do. I think it's probably good practice just to say people will
need whatever version of Army Builder I'm using to test the files
anyway.

Cheers,
Russell.


-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/36190/_/975276460/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
I believe that "istype" didn't properly recognize the "!" form in the
original V2.0 release. This means you should flag to users that they need
the latest version of AB (and ABLite) to use the Principate data files.

Thanks, Rob


At 10:04 PM 11/23/00 +0000, you wrote:
>As it turns out, The Druid is using Warp Magic, so it needs to be
>setup like the Goblins. ie. Each spell is assigned to a specific unit
>at design time. The Mist of Norka is therefore not something taken by
>the Druid specifically, but more taken for each unit.
>Here I was, trying to figure out a race attribute to do the
>validation, when there's a perfectly good unit one :-)
>
>Thanks Rob, that's just what I was after. I know it may not be ideal,
>but at least it'll be validated.
>
>Russell.


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com

-------------------------- eGroups Sponsor -------------------------~-~>
Create your business web site your way now at Bigstep.com.
It's the fast, easy way to get online, to promote your business,
and to sell your products and services. Try Bigstep.com now.
http://click.egroups.com/1/9183/1/_/36190/_/975275761/
---------------------------------------------------------------------_->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
 
You must log in or register to reply here.
Back
Top