• 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

Wish list

K

khrk2012

Active member
I would like AB to include an ability to put a stat line onto options
and/or items.

I could for see this for making stat line for weapons. Such as
ranges, damage etc. - yes I know you could just write them in the
description but the stats would be - cleaner - and adjustable with
other options.

Yes, I also am aware of the "sset" and just asigning the "unit" as a
weapon, and this is a good second best. But the weapons are then
counted in the unit- Yes I am aware you can use, "coun-no" but there
are some instance when that is inconvienent.

well it is just a thought.

i would also like a ucst attribute for Items.

Just some thoughts if you run out of things to do rob!


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Small business owners...
Tell us what you think!
http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
 
I just got back from GenCon last night and I'm now in catch-up mode. So
that's why this reply took so long.

The notion of putting a stat line onto options simply won't fly. Options
modify things - they don't have any kind of state.

Adding a stat line to items is possible, although I'm going to need a
compelling reason for why child units are not a valid solution. You can
easily attach a child unit, and the child unit can easily have a custom
stat line via "sset". You can also use attributes to control whether the
child unit actually has an impact on the model count for the unit (besides
"coun"). So I don't see a situation wherein child units fail to work. If
you can outline the details of what you're trying to accomplish, I can
either (a) offer useful suggestions on how to solve the problem and/or (b)
see the situation more clearly and understand why you really need a stat
line for items.

Please note that I've already added to the todo list support for hidden
stats for items. These would be a small number (3? 5?) of stats that are
used internally only and never displayed to the user. These stats would be
local to each item and would enable limited calculations and state to be
tracked for each item via tweaks. The values of these special stats could
then be applied to the stats of the parent unit in appropriate ways via tweaks.

As above, please provide justification for why a "ucst" attribute is needed
for items. I'm happy to put things on the todo list if a reasonable case
can be established for why those things are needed.

Thanks, Rob


At 02:42 AM 7/31/2001 +0000, you wrote:
>I would like AB to include an ability to put a stat line onto options
>and/or items.
>
>I could for see this for making stat line for weapons. Such as
>ranges, damage etc. - yes I know you could just write them in the
>description but the stats would be - cleaner - and adjustable with
>other options.
>
>Yes, I also am aware of the "sset" and just asigning the "unit" as a
>weapon, and this is a good second best. But the weapons are then
>counted in the unit- Yes I am aware you can use, "coun-no" but there
>are some instance when that is inconvienent.
>
>well it is just a thought.
>
>i would also like a ucst attribute for Items.
>
>Just some thoughts if you run out of things to do rob!


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Small business owners...
Tell us what you think!
http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
 
The stat line in options would be nice but not comepling per se.

I would like the ucst for item if only for versitility. Alhough using
the hidden stat works as you pointed out.


On another note. Is there a way to limit an option and/or item to
just a certian type.

I know lglx:type=*** isnt valid but is their another way?

Also is there a way to have the childs option selection modify the
grand-parents stat line but not its own parents stat line?


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Small business owners...
Tell us what you think!
http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
 
To limit an option to a type, use "utyp". To limit an item to a type, use
"ityp" or "itst".

You can use the "prnt" attribute on the child unit to directly modify the
stats of the parent unit.

Hope this helps,
Rob


At 05:24 PM 8/8/2001 +0000, you wrote:
>On another note. Is there a way to limit an option and/or item to
>just a certian type.
>
>I know lglx:type=*** isnt valid but is their another way?
>
>Also is there a way to have the childs option selection modify the
>grand-parents stat line but not its own parents stat line?


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Small business owners...
Tell us what you think!
http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
 
You must log in or register to reply here.
Back
Top