• 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

Stupid Tag Question

M

Mettius

Well-known member
From the AB Kit docs...
The primary advantage of accrued tags is that you can have Army Builder automatically keep track of information that spans the various levels of
the roster hierarchy. For example, by defining an accrued tag and assigning it to all entities that must be tracked for a particular rule, Army Builder
will tally up the tags for each entity at every level, allowing you to readily determine the count at any level and perform validation appropriately.
Click to expand...

Okay, I'm daft I admit. How do I assign a tag so that each "member" of a given unit has a tag and I can keep track how how many of them there are presently on the roster?

For example: Trooper_Bob is a squad which can have from 1 to 10 fellow clone troopers. For each member of squad Trooper_Bob how do I assign a private tag? I'm looking to be able to look at how many members of squad Trooper_Bob exist so I can ultimately enable a special weapon option for every multiple of 5 tha the squad contains. Help? :)
 
Assuming that you have a single unit of 1-10 clone troopers, tags wouldn't really be best for this - you probably want to have a private unit stat with a Calculate script that takes the number of models in the unit, then divides by 5 to get the number of special weapon options that are allowed

Then, you can use the value of that stat as the maximum in an exclusion group, which will limit the number of selections to the value of the stat.

Hope this helps!
 
Well technically I was hoping that I could come up with something which would work across multiple units.

The particular game I'm modeling has 1 model per unit, but some weapon options are only available based on the total number of models of that "type" present.

---
But, forgetting the above and assuming a single multi-model unit...
OK, I create a private stat SpcGunSt_A
I'm not sure I follow how to get it to have a value of "1" for each member of the unit?

*Edit - OK I figured it out. I set the SpcGunSt_A in the post link script based on a ratio of count[effective].
 
Last edited:
If you are wanting to tag multiple models across multiple units to limit them across the roster then you could try using accumulated tags and a statcalc
 
Ah, you want it to work across multiple units? Can each unit have just one weapon, or could one unit have multiple weapons?

Assuming the former, you could use an option evaluate script to add a tag if the option is selected. Then, write a rule for the roster that totals up the number of units and tags, and figure out how many you should have and how many you're allowed.
 
Colen said:
Ah, you want it to work across multiple units? Can each unit have just one weapon, or could one unit have multiple weapons?
Click to expand...

Each Tpr_Bob unit has multiple weapons (pistol, rifle, grenades), one of which (rifle) can be replaced by a special weapon (e.g. sniper rifle, bazooka, flame-thrower), for every five Tpr_Bob models on the roster.
 
You could have a statcalc to count Tpr_Bob and a script in postlink that if the special weapon is selected then to tag the parent with an accrued tag. Then use a rule to count the number of Tpr_Bob from the statcalc and divide by 5 (use round as well - or you could handle that in the statcalc) and check the number of accrued tags there are against this
 
You must log in or register to reply here.
Back
Top