v0.2.7

• Unified tech_base strings for all components (and mechs). Available strings are:
  • IS
  • Clan
  • All
  • Mixed
  • Unknown
• Renamed the mech techbase to tech_base
  • this makes it consistent with other components
• The following components now have a tech base entry:
  • Engine
  • Armor
  • Structure
  • Mech
• Added new engine section to the JSON structure. Example:

"engine": {    
    "name": "380 XL Engine",
    "type": "XL",
    "tech_base": "IS" 
}, 

Known issues:

• Some MTF files contain components with two different tech bases
  • e.g. the Turkina U has the following engine: engine:285 XL (Clan) Engine(IS)
  • in this case, mtf2json will either choose the tech base that corresponds to the mech tech base, or the first one (if the mech has Mixed tech base)
• Some MTF files contain conflicting tech bases
  • e.g. the Turkina U has tech base Clan but an IS structure (according to the MTF file)
  • no workaround has been implemented for this (yet)
• Both issues are very likely MegaMek bugs