You can use TAGX for your own maps. It would be really useful for maps like Large Middle Earth, but setting it up this late in the process would be a pain.
But how does TagX work?
TagX substitutes @tagname@ with a colon delimited list of things having the tag.
Source:
<attachment name="unitAttachment" attachTo="axe_raider" javaClass="games.strategy.triplea.attachments.UnitAttachment" type="unitType">
<option name="transportCost" value="1"/>
<option name="movement" value="2"/>
...
<tag name="foot"/>
</attachment>
<attachment name="unitAttachment" attachTo="berserker" javaClass="games.strategy.triplea.attachments.UnitAttachment" type="unitType">
<option name="transportCost" value="1"/>
<option name="movement" value="2"/>
...
<tag name="foot"/>
</attachment>
<attachment name="unitAttachment" attachTo="boar_rider" javaClass="games.strategy.triplea.attachments.UnitAttachment" type="unitType">
...
<option name="targetsAA" value="@foot@"/>
<option name="typeAA" value="charge"/>
...
<tag name="mounted"/>
</attachment>
Result:
<attachment name="unitAttachment" attachTo="axe_raider" javaClass="games.strategy.triplea.attachments.UnitAttachment" type="unitType">
<option name="transportCost" value="1"/>
<option name="movement" value="2"/>
...
<tag name="foot"/>
</attachment>
<attachment name="unitAttachment" attachTo="berserker" javaClass="games.strategy.triplea.attachments.UnitAttachment" type="unitType">
<option name="transportCost" value="1"/>
<option name="movement" value="2"/>
...
<tag name="foot"/>
</attachment>
<attachment name="unitAttachment" attachTo="boar_rider" javaClass="games.strategy.triplea.attachments.UnitAttachment" type="unitType">
...
<option name="targetsAA" value="axe_raider:berserker"/>
<option name="typeAA" value="charge"/>
...
<tag name="mounted"/>
</attachment>
If later you were to add another unit, and tag it <tag name="foot"/>, they will automatically appear as a valid target for charge, without you having to do anything.
TagX can also do foreach loops:
<attachment foreach="LEADER=@leadership@" name="supportAttachment_$LEADER$_leadership_foot" attachTo="$LEADER$" javaClass="games.strategy.triplea.attachments.UnitSupportAttachment" type="unitType">
<option name="unitType" value="@foot@"/>
<option name="faction" value="allied"/>
<option name="side" value="offence:defence"/>
<option name="dice" value="strength"/>
<option name="bonus" value="1"/>
<option name="number" value="1"/>
<option name="bonusType" value="leadership"/>
<option name="impArtTech" value="false"/>
<option name="players" value="@player@"/>
</attachment>
Tags are substituted first, so @player@ turns into a colon delimited list of players, @leadership@ turns into a colon delimited list of units with the leadership tag. Then the foreach is implemented: the result is a (way too long) list of support attachments, one for each unit with the leadership tag. All instances of $LEADER$ are replaced with the name of the unit to which that particular support attachments belong.
Foreach expansions can be nested. The syntax is foreach="VARIABLE1=value1:value2:value3;VARIABLE2=value4:value5;VARIABLE42=value42:value43" etc., if I recall correctly.
Another example:
<attachment foreach="territory=list:of:territories:you:care:about;player=list:of:players:you:care:about" name="conditionAttachment_$player$_has_battleship_at_$territory$" attachTo="$player$" javaClass="games.strategy.triplea.attachments.RulesAttachment" type="player">
<option name="directPresenceTerritories" value="$territory$" count="1"/>
<option name="unitPresence" value="battleship" count="1"/>
</attachment>
So conditionAttachment_bestplayer_has_battleship_at_bestterritory will be true exactly when bestplayer has a battleship at bestterritory.
