We should combine Plugins with Global Extensions

To rebuild HQs, one has to pay a cost. This cost is higher if HQ is not in or adjacent to a port.

I try to compute how much point are spent during the production phase by using a trigger. Each unit as unique costs. Since this costs vary depending on where the unit is (more expensive to build up a unit in Med Front than in East or West Front) and on some other external conditions I cannot put unit basic costs in a property attached to the gamepiece. So I use global properties defined in each zones of the map representing the fronts. As soon as I build up a unit, I add the corresponding zone unit build up costs to a game global property keeping track of this side expenses. If that was that simple all would be ok. (I already have a proto module to experiment this).

But in the case of HQ units, those require heavy logistical support to build up and this is simulated by a higher costs if the HQ is not located in or adjacent to a Major port when operating overseas. When a HQ unit is built up and it is overseas and not in or adjacent to a major port, there is a additionnal costs incurred. That’s what I’d like to be able test.

If I can test the presence of an inivisible “port” or “adj to port” in the same hex the cost would be the normal one if not, the normal cost plus the penalty.

I shall put the proto module on my website and provide you with a link to it as it will speak tons :slight_smile:

Hi Brent,

Didn’t respond to this as I gave it some thought and have slept many times since (forgot) :slight_smile:
I do think a SumCurrent(Locationtype) would be a very useful option be it location,map, zone etc…to include before you release.

Do have a question expanding from the CP’s involving TA’s. As you know the CP runs in realtime and needs no key or command to invoke them.
I was wondering if its possible to extend this realtime ability to TA’s based soley on their property filter to perform their function(s)?

This would kind of be a marriage of the two traits I guess if that makes sense - you wouldn’t necessarily rely on a passive key to invoke a trigger (for hidden TA’s) if the CP or TA prop filter cond is met