I had an interesting thought regarding TaskForceRules: I wondered what would happen if expressions or compound values were used in the Mandatory, Recommended, or Maximize columns?
My first attempt was to substitute two comma-separated modifiers in the Maximize column for several ship types. Unfortunately, that seemed to break the parsing completely.
My second attempt had more promising results. I still used two values in Maximize, but delimited with "+" instead of a comma, in effect making an expression out of it. For instance:
The result wasn't striking, but what it didn't do was break the parsing like the first try; the effect on Auto Build appeared about the same as if only the original/first value was present. However, the fact that this didn't break the parsing altogether suggests to me that there might be room for further experimentation with this. I don't want to pursue it right now and get distracted, but if someone else would like to explore it further please keep us all appraised of what you find.
My first attempt was to substitute two comma-separated modifiers in the Maximize column for several ship types. Unfortunately, that seemed to break the parsing completely.
My second attempt had more promising results. I still used two values in Maximize, but delimited with "+" instead of a comma, in effect making an expression out of it. For instance:
Code:
Mandatory Recommended Maximize InfoWeap UniSpace AccDisEn + FarDamag InfoWeap UniSpace NearDamg + FireDlay InfoWeap UniSpace PntDstWp InfoMisl InfoMisl FarDamag InfoFWpn InfoFWpn UniSpace InfoWeap UniSpace FireDlay + MultFire OffTgtRg InfoWeap OffTgtRg + OffSptRg TrpCap UniSpace UniSpace Colony UniSpace UniSpace Outpost UniSpace UniSpace
Comment