Implementing this might be as simple as just adding a placeholder tech to the galaxy sizes in mapsizedefs.xml with no effects!!

Right now, just about anything can have a prerequ requirement of something else, but as far as I'm aware the map size cannot be used as a prerequ.  I'm making this request because I made some changes recently based on a couple threads, one of those changes was a "while I'm in here doing this..." that fits well with immense maps, but probably needs a very different version for smaller maps .  without a way to gate it based on mapsize, the options I can see for these sorts of things as a modder are:

• Make a different mod version for each map size (or group of them) & go through the hassle of updating each fork if you later make revisions
• just declare that it's not really for maps under/over/equal to a certain size

In this case, I don't think the ai will use it & players can choose to use/not use it as a result, but I'd almost certainly choose the second & quickly stop bothering with  the first if I went that way

This has the benefit of potentially allowing modders to make tech lines to address certain problems players see in different map sizes globally without needing to mod every relevant component/structure if a global multiplier on an EffectType  could have done it.  Since mapsizedefs.xml seems to only support the ShipRangeeffecttype, it might be a low code work around to opening a locked gateway modders bumped into regularly in GalCiv2.  Since a global modifier doesn't modify any individual components/structures, this might also enhance mod compatibility in some cases