A better word than "infrastructure"
TripleA (since 1.2.6) has an option called "isInfrastructure", that traditionally applies only to "factory" and "aaGun" units (though from v5 onwards not anymore to aaGun).
Clearly, the term "infrastructure" was taylored for the "factory" case, and well adapts to other things like ports, rails, etc., but it is really not good in general to describe the actual matter. It was not even already good when it was firstly introduced, as an "aaGun" unit is by no means an infrastructure, in reality.
What the infrastructure name captures, as an option, is the case in which a unit cannot be taken as casualty and it is lost after all other units on its same side have been destroyed.
Examples of "infrastructure" units are:
The "factory" of any World War II games.
The "aaGun" of older World War II games.
The "airfield" of World War II Global 1940 2nd Edition
The "Horse" of Feudal Japan.
The "gas" of Domination 1914 No Man's Land.
The "Wild-Mammoth" of Age of Tribes: Primeval
The "fort" of Rome Total War
The "leader" of Greyhawk Wars
The "General" of Napoleonic Empires
The "train" of Red Sun Over China
The "Material" of Total World War: December 1941 2.8
The "zzSword" of War of the Relics
One could say to call them "capturable", as that is how these units are identified in the default tooltips ("Can be Captured"), but that tells only a quarter of the story, not really clarifying that the unit cannot be taken as casualty, unless you have a full knowledge of TripleA, on the matter, and ignoring the fact that you can have a game in which all "infrastructures" are destroyed, instead of captured.
Here I'm not asking to change any TripleA definitions (well, maybe the default tooltips, if we find a good definition), but is there a word that can be used to convey the "infrastructure" concept, that is better than calling them infrastructures?
We may be stuck on this one. Unless we can have the map parsing to know when to expect one name vs another, we cannot update this without updating all existing maps. Even then, it's a major disruption.
I think we'd need a "map parse version" attribute to be able to support this: https://github.com/triplea-game/triplea/issues/5081
This is an example where a 'min' version is not sufficient and forces us to update all maps and upgrade the 'min' version when making such a change. Upgrading all maps is hard to execute on, and it's also difficult to coordinate to keep all engine versions working.
@LaFayette Actually, here I'm not asking to change any TripleA definitions. I'm just asking if anyone has ideas for an alternative name to capture the "infrastructure" behaviour, to be used in tooltips and such, for example.