Lone Wolf Development Forums  

Go Back   Lone Wolf Development Forums > Army Builder Forums > Army Builder
Register FAQ Community Today's Posts Search

Notices

Reply
 
Thread Tools Display Modes
VanMan4311 at aol.com
Guest
 
Posts: n/a

Old August 14th, 2002, 07:46 PM
I want to have an option adjust the stat values of its grandparent. Is there
any way to do this within the program?
Thanks,
Brad VanMiddlesworth


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


------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXi....GAA/IMSolB/TM
---------------------------------------------------------------------~->
  #1 Reply With Quote
demandred at skrill.org
Guest
 
Posts: n/a

Old August 14th, 2002, 08:01 PM
At 09:55 PM 8/14/2002 -0400, you wrote:
>I want to have an option adjust the stat values of its grandparent. Is there
>any way to do this within the program?

There is, but it involves craziness. I assume that by its grandparent you mean:

Unit A (needs stat adjusted)
|
|
Unit B
|
|
Unit C (with option)

You could do it by having Unit C assign unit B a type which activated an
option which changed the stat value of unit A, or that gave unit A a type
which activated an option which changed it's own stat value. It's a bit of
a guddle, as you can no doubt see.

Or I could be misinterpreting you (i.e. you want to make Unit C change the
stat of unit B), in which case just use the prnt: attribute.


--
Colen McAlister, demandred@skrill.org
http://www.incompetence-central.co.uk | http://www.skrill.org/
"It's time to toss the dice"


------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXi....GAA/IMSolB/TM
---------------------------------------------------------------------~->
  #2 Reply With Quote
VanMan4311 at aol.com
Guest
 
Posts: n/a

Old August 15th, 2002, 04:17 AM
In a message dated 8/15/2002 12:02:24 AM Eastern Daylight Time,
demandred@skrill.org writes:


> You could do it by having Unit C assign unit B a type which activated an
> option which changed the stat value of unit A, or that gave unit A a type
> which activated an option which changed it's own stat value. It's a bit of
> a guddle, as you can no doubt see.
>

You understood me correctly, but I don't understand you completely. How do
you get an option to be activated by assigning a unit a type?
Brad


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


------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXi....GAA/IMSolB/TM
---------------------------------------------------------------------~->
  #3 Reply With Quote
imhotepthearchitect at ya
Guest
 
Posts: n/a

Old August 15th, 2002, 08:34 AM
I'll answer this since you have been waiting for a few hours :P
Create an option, for argements sake we'll call it AdjStat. I has the following attributes hide; prnt:Save+1; utyp:setByChild
The utyp attribute will prevent the option from being available unit the unit it is given to has the type setByChild assigned to it. Now AdjStat is linked to unit B by an incl so that it will automatically be turned on once it is legal.
Create another option with the following attribute type:setByParent-grand and assignt that to unit C via a selectable option, as a more: from another option, or however you want it to become enabled.
Once the attribute with the type:setByParent is selected in unit C, it assigns setByParent to unit B which in turn enables the adjStat option in unit B, which adjust the stat value of unit A.
You could also do this, by carrying the type assignment on up the ladder and have unit A adjust its own stat value.

Note: I did all this off the top of my head, so doublecheck with the attribute descriptions for usage
VanMan4311@aol.com wrote:In a message dated 8/15/2002 12:02:24 AM Eastern Daylight Time,
demandred@skrill.org writes:
You understood me correctly, but I don't understand you completely. How do
you get an option to be activated by assigning a unit a type?
Brad


--
Graham H. Tracey - aka ImhotepTheArchitect
I'd rather have a full bottle in front of me than a full frontal labotomy.
40k3 AB Group: groups.yahoo.com/group/ab-40k3
40k3 AB Files: groups.yahoo.com/group/ab-files/


---------------------------------
Do You Yahoo!?
HotJobs, a Yahoo! service - Search Thousands of New Jobs

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


------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXi....GAA/IMSolB/TM
---------------------------------------------------------------------~->
  #4 Reply With Quote
VanMan4311 at aol.com
Guest
 
Posts: n/a

Old August 15th, 2002, 12:51 PM
Alright this is what I have, and I can't see to get it to work.

Hero (Stat=HP)
|
Artefact (UnitB)
|
Rune on Artefact (UnitC)

Artefact has option RuneLvl1 (Link Nature:Auto; utyp:RLvl1;prnt:HP-5-base)
and option Rune (Link Nature:Cost; unit:Rune@abs=1)

Rune has option Level1 (Link Nature:Auto; type:RLvl1-grand)

So I start it up, Hero with artefact. I debug type on Artefact it shows none.
Debug Options on Artefact= RuneLvl1 Compliant:no Selected:no. Now I select
option Rune. Debug type for Artefact, RLvl1. Debug Options on Artefact=
RuneLvl1 Compliant:no Selected:no.

I don't understand the problem. From what I can guess, the type legality is
determined when the link RuneLvl1 is first evaluated, then not again. How can
I get AB to evaluate it again? Does anyone know a datafile where I can see an
example?
Brad VanMiddlesworth

In a message dated 8/15/2002 12:35:47 PM Eastern Daylight Time,
imhotepthearchitect@yahoo.com writes:


> I'll answer this since you have been waiting for a few hours :P
> Create an option, for argements sake we'll call it AdjStat. I has the
> following attributes hide; prnt:Save+1; utyp:setByChild
> The utyp attribute will prevent the option from being available unit the
> unit it is given to has the type setByChild assigned to it. Now AdjStat is
> linked to unit B by an incl so that it will automatically be turned on once
> it is legal.
> Create another option with the following attribute type:setByParent-grand
> and assignt that to unit C via a selectable option, as a more: from another
> option, or however you want it to become enabled.
> Once the attribute with the type:setByParent is selected in unit C, it
> assigns setByParent to unit B which in turn enables the adjStat option in
> unit B, which adjust the stat value of unit A.
> You could also do this, by carrying the type assignment on up the ladder
> and have unit A adjust its own stat value.



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


------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXi....GAA/IMSolB/TM
---------------------------------------------------------------------~->
  #5 Reply With Quote
VanMan4311 at aol.com
Guest
 
Posts: n/a

Old August 15th, 2002, 12:51 PM
Aha! I got it. Thanks for ya'lls help. The problem was that the option that
depended on the type HAD NO NAME. For some reason, I put a name on it and it
magically worked.
All is well that ends well I guess.
Brad VanMiddlesworth


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


------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXi....GAA/IMSolB/TM
---------------------------------------------------------------------~->
  #6 Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
question about adjusting unit size tneva82 at yahoo.com Army Builder 2 April 10th, 2003 12:53 AM
Adjusting Parent unit size with a child option mobo at adelphia.net Army Builder 8 June 24th, 2002 08:06 PM


All times are GMT -8. The time now is 12:21 AM.


Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.