v0.17.6
| Format | Description | Import | Export |
|---|---|---|---|
.mtf and .blk |
Unit data from | ||
| • MegaMek Lab: https://megamek.org | |||
| • Solaris SkunkWerks: https://solarisskunkwerks.com | |||
| • Mordel.net | ✅ | ||
.mul |
Force file from MegaMek . Currently only units and pilot import is supported. | ✅ – | |
.txt |
A plain text list of units, one per line. | ✅ | |
.fccm.json |
Flechs Command Console Match | ||
| json containing all match details from units to settings. Used for restoring matches mid-game. | ✅ | ✅ | |
.status.csv |
Unit Status | ||
| csv containing damage details for one or more units. Use for moving data between Command Console and your spreadsheet tool of choice | ✅ | ✅ | |
.status.json |
Same as above but json. | ✅ | ✅ |
.list.csv |
A .csv version of the ComCon match setup screen’s force tables with detailed design stats, skills and BVs. | ✅ |
Unit files can be dragged and dropped into a specific force, or into the match, in which case a new force will be created for them.
Imported units are saved internally, locally, in an ‘Ad-hoc imports’ catalog (see Catalogs) and will show up in search.
Gif of the ad-hoc imports catalog being created when a unit is imported
Image of the (Imp)orted tag for a custom unit that’s showing up in a unit search.
.fccm.json)These files contain everything needed to restore a full match mid-combat, even mid-event-resolution. They include everything from damage with staleness, through declared ranges and proxy targets, to the current event that a unit might be resolving. This data is perfect for manually switching between long running matches, moving a match to a different machine, or creating a manual ‘save point’ generally.
.txt )The simplest way to get a unit list into Command Console — Just a .txt file with the names of the units on different lines. Copying that kind of text and pasting into a match also works.
.status.csv, .status.json ).status files contain information needed for campaign record-keeping: what unit is it, its damage, ammo expenditures and munition types, crew damage and skills, etc. These files do not contain mid-match information like attack declarations, heat, or event logs.
.status files come in two forms: .status.csv for spreadsheet jockeys and .status.json for third party tools or those comfortable with json editors.