# mtf2json
`mtf2json` converts [MegaMek](https://github.com/MegaMek/)'s MTF file format to JSON.
## Project Goals and Features
- Make it easy to parse MTF files in any modern programming language, using a well-known and documented format (JSON).
- Provide a comprehensive JSON structure that includes all necessary data for generating record sheets.
- Handle various issues and inconsistencies in the MTF format.
## Why mtf2json?
MegaMek is a great project, but the MTF format is difficult to work with. It's not a standardized format and there is no official
specification (at least I couldn't find one). Furhermore, an MTF file does not contain all information required to create an actual
record sheet (e.g. the structure pips are missing).
`mtf2json` does not simply create a 1:1 JSON version of the MTF data (that wouldn't be possible anyway) but restructures the data and
adds information that is required for creating record sheets (see examples below).
## Limitations and Supported Versions
### Quad Mechs
Currently, `mtf2json` can only convert MTF files of **biped** mechs.
### Supported MegaMek Version
`0.49.19.1`
### Testing
Testing `mtf2json` is challenging, mostly because the MTF format is so loosely specified. I'm still not sure if I've actually seen all
possible keys and understood all supported value syntaxes. Since there are over 4000 MTF files in MegaMek, I can't test and manually
verify them all. If you have trouble converting an MTF file, create a Github issue and append the file, so I can verify and fix the issue.
## JSON Structure and Examples
Here are some comparisons of sections from an MTF file and their JSON counterpart:
### The Basic Stuff
MTF:
```
chassis:Atlas
model:AS7-K
mul id:144
```
JSON:
```json
"chassis": "Atlas",
"model": "AS7-K",
"mul_id": 144,
```
Most of the "flat" `key:value` pairs are also stored as `key:value` pairs in JSON. However, number values are stored as `int` if appropriate
(they remain strings if they are used as names or model designation).
### Rules Level
MTF:
```
Rules Level:2
```
JSON:
```json
"rules_level": 2,
"rules_level_str": "Standard",
```
A string version of the rules level is automatically added. It's intended to be used in the record sheet and determined using the same algorithm
as [MegaMek](https://github.com/juk0de/megamek/blob/78fb6e4616dd469dcb781c7da37d1bae748c45ce/megamek/src/megamek/common/SimpleTechLevel.java#L92).
### Quirks
MTF:
```
quirk:battle_fists_la
quirk:battle_fists_ra
quirk:command_mech
quirk:distracting
quirk:imp_com
```
JSON:
```json
"quirks": [
"battle_fists_la",
"battle_fists_ra",
"command_mech",
"distracting",
"imp_com"
],
```
No more dealing with multiple identical keys. Just a simple JSON list.
### Heat Sinks
MTF:
```
Heat Sinks:20 Single
```
JSON:
```json
"heat_sinks": {
"quantity": 20,
"type": "Single"
},
```
Type and quantity of heat sinks are separate keys, no need for additional parsing.
### Movement Points
MTF:
```
Walk MP:3
Jump MP:0
```
JSON:
```json
"walk_mp": 3,
"run_mp": 5,
"jump_mp": 0,
```
The movement points for running are calculated automatically, for your convenience.
### Armor
MTF:
```
armor:Standard(Inner Sphere)
LA armor:34
RA armor:34
LT armor:32
RT armor:32
CT armor:47
HD armor:9
LL armor:41
RL armor:41
RTL armor:10
RTR armor:10
RTC armor:14
```
JSON:
```json
"armor": {
"type": "Standard",
"tech_base": "Inner Sphere"
"pips": {
"left_arm": 34,
"right_arm": 34,
"left_torso": {
"front": 32,
"rear": 10
},
"right_torso": {
"front": 32,
"rear": 10
},
"center_torso": {
"front": 47,
"rear": 14
},
"head": 9,
"left_leg": 41,
"right_leg": 41
},
},
```
Armor type, tech base (if available) and pips are stored in the `armor` section.
Note that the tech base is not always available in the MTF file (i.e. sometimes it's "Standard Armor", sometimes "Standard(Inner Sphere))".
Maybe "Standard" always means "Inner Sphere", but I'm not sure, so I leave out the `tech_base` entry in that case.
### Weapons
MTF:
```
Weapons:3
1 ISGaussRifle, Right Torso, Ammo:16
1 ISERLargeLaser, Left Arm
2 ISMediumPulseLaser, Center Torso (R)
```
JSON:
```json
"weapons": {
"1": {
"ISGaussRifle": {
"location": "right_torso",
"facing": "front",
"quantity": 1,
"ammo": 16
}
},
"2": {
"ISERLargeLaser": {
"location": "left_arm",
"facing": "front",
"quantity": 1
}
},
"3": {
"ISMediumPulseLaser": {
"location": "center_torso",
"facing": "rear",
"quantity": 2
}
},
},
```
Location, facing, quantity and ammo are all individual keys of each weapon. Additionally, each weapon has a slot number that represents
the order in the MTF file (and on the record sheet).
### Structure
MTF:
```
structure:IS Standard
```
JSON:
```json
"structure": {
"type": "Standard",
"tech_base": "Inner Sphere",
"pips": {
"head": 3,
"center_torso": 31,
"left_torso": 21,
"right_torso": 21,
"left_arm": 17,
"right_arm": 17,
"left_leg": 21,
"right_leg": 21
}
},
```
Structure type and tech base (if available) are stored in the `structure` section. The pips are added afterwards, based on the mech's tonnage.
"IS" is converted to "Inner Sphere", in order to be consistent to the tech base naming in the `armor` section.
Note that the tech base is not always available in the MTF file (i.e. sometimes it's "IS Standard", sometimes just "Standard"). Maybe "Standard"
always means "Inner Sphere", but I'm not sure, so I leave out the `tech_base` entry in that case.
### Critical Slots
MTF:
```
Left Arm:
Shoulder
Upper Arm Actuator
Lower Arm Actuator
Hand Actuator
Heat Sink
Heat Sink
ISERLargeLaser
ISERLargeLaser
ISAntiMissileSystem
-Empty-
-Empty-
-Empty-
```
JSON:
```json
"critical_slots": {
"left_arm": {
"1": "Shoulder",
"2": "Upper Arm Actuator",
"3": "Lower Arm Actuator",
"4": "Hand Actuator",
"5": "Heat Sink",
"6": "Heat Sink",
"7": "ISERLargeLaser",
"8": "ISERLargeLaser",
"9": "ISAntiMissileSystem",
"10": null,
"11": null,
"12": null
},
}
```
All critical slots data is stored in the `critical_slots` section, with one section per location. Every slot has the slot number as key,
making it very easy to check the content of each slot directly. The `-Empty-` string is replaced by an actual `null` (python `None`).
### Fluff
MTF:
```
overview:The Banshee, introduced in 2445 by the Terran Hegemony, is a 'Mech that was designed specifically for close-assault operations during the early years of BattleMech warfare.
capabilities:A contemporary of the Mackie and Emperor, the Banshee is undeniably fast for one of the heaviest 'Mechs ever produced, and with fifteen tons of armor it is better protected than most other assault 'Mechs. However the use of a massive GM 380 fusion engine left little room for weaponry, and even at the time of its introduction the Banshee was considered undergunned compared to its privately-built competition. As critics noted, what use was impressive armor and mobility if a better-armed enemy could overwhelm and destroy it? The result was a mediocre 'Mech which even the lowly Rifleman could beat as long as it prevented the Banshee's mass from coming into play.
deployment:The two primary weapons on the Banshee, a Magna Hellstar PPC matched up with an Imperator-A Autocannon/5 with one ton of ammo, are mounted in the right and left sides of its torso. The two systems complement each other with similar range profiles and would provide good firepower for a 'Mech weighing at half the tonnage of the Banshee. Perversely for a close-combat 'Mech their minimum ranges means both weapons present targeting difficulties as the Banshee closes in on its enemy, and a Magna Mk I Small Laser mounted in its head appears to have been installed as an afterthought. Sixteen heat sinks help keep the 'Mech cool though, and thanks to its prodigious size the Banshee can turn lighter 'Mechs to scrap in hand-to-hand fighting.
history: The Hegemony soldiered on though, producing five thousand Banshees in a decade before its poor combat performance finally forced them to stop production in 2455 and the 'Mech was relegated to training and militia units for the next few centuries. Even during the Succession Wars the 'Mech's poor reputation meant many commanders saw it as a liability rather than an asset; unless they were fighting on a backwater Periphery world or as part of a poorly-equipped outfit, most Banshees were placed in second-line reserves to provide fire support or fulfill the role of brawlers so that better-armed 'Mechs need not engage in hand-to-hand combat. In this way fully a third of the original Banshee production run remained operational by the dawn of the thirty-first century and could be found throughout the Inner Sphere and Periphery, with the lion's share residing within the Lyran Commonwealth. Though a few attempts had been made over the years to improve the Banshee, Defiance Industries was the first to produce a variant which markedly improved on the original and was suggested by many of its original critics. With help from the Federated Suns and access to blueprints from the original Hesperus II factories, the BNC-3S proved to be such a success the Lyrans began fielding them in front line units, surprising their enemies who ignored them to focus on "real" threats with thoroughly unexpected firepower. Under the Federated Commonwealth improvements would continue to be made, though not at the same priority level as other projects, and the much-improved BNC-5S was active in time to meet the Clan Invasion.
manufacturer:Diplass BattleMechs,Witten Industries,Defiance Industries,Star League Weapons Research
primaryfactory:Apollo,Hesperus II,Hesperus II,New Earth
systemmanufacturer:CHASSIS:Star League
systemmode:CHASSIS:XT
systemmanufacturer:ENGINE:GM
systemmode:ENGINE:380
systemmanufacturer:ARMOR:Starshield
systemmanufacturer:COMMUNICATIONS:Dalban
systemmode:COMMUNICATIONS:Commline
systemmanufacturer:TARGETING:Dalban
systemmode:TARGETING:HiRez-B
```
JSON:
```json
"fluff": {
"overview": "The Banshee, introduced in 2445 by the Terran Hegemony, is a 'Mech that was designed specifically for close-assault operations during the early years of BattleMech warfare.",
"capabilities": "A contemporary of the Mackie and Emperor, the Banshee is undeniably fast for one of the heaviest 'Mechs ever produced, and with fifteen tons of armor it is better protected than most other assault 'Mechs. However the use of a massive GM 380 fusion engine left little room for weaponry, and even at the time of its introduction the Banshee was considered undergunned compared to its privately-built competition. As critics noted, what use was impressive armor and mobility if a better-armed enemy could overwhelm and destroy it? The result was a mediocre 'Mech which even the lowly Rifleman could beat as long as it prevented the Banshee's mass from coming into play.",
"deployment": "The two primary weapons on the Banshee, a Magna Hellstar PPC matched up with an Imperator-A Autocannon/5 with one ton of ammo, are mounted in the right and left sides of its torso. The two systems complement each other with similar range profiles and would provide good firepower for a 'Mech weighing at half the tonnage of the Banshee. Perversely for a close-combat 'Mech their minimum ranges means both weapons present targeting difficulties as the Banshee closes in on its enemy, and a Magna Mk I Small Laser mounted in its head appears to have been installed as an afterthought. Sixteen heat sinks help keep the 'Mech cool though, and thanks to its prodigious size the Banshee can turn lighter 'Mechs to scrap in hand-to-hand fighting.",
"history": "The Hegemony soldiered on though, producing five thousand Banshees in a decade before its poor combat performance finally forced them to stop production in 2455 and the 'Mech was relegated to training and militia units for the next few centuries. Even during the Succession Wars the 'Mech's poor reputation meant many commanders saw it as a liability rather than an asset; unless they were fighting on a backwater Periphery world or as part of a poorly-equipped outfit, most Banshees were placed in second-line reserves to provide fire support or fulfill the role of brawlers so that better-armed 'Mechs need not engage in hand-to-hand combat. In this way fully a third of the original Banshee production run remained operational by the dawn of the thirty-first century and could be found throughout the Inner Sphere and Periphery, with the lion's share residing within the Lyran Commonwealth. Though a few attempts had been made over the years to improve the Banshee, Defiance Industries was the first to produce a variant which markedly improved on the original and was suggested by many of its original critics. With help from the Federated Suns and access to blueprints from the original Hesperus II factories, the BNC-3S proved to be such a success the Lyrans began fielding them in front line units, surprising their enemies who ignored them to focus on \"real\" threats with thoroughly unexpected firepower. Under the Federated Commonwealth improvements would continue to be made, though not at the same priority level as other projects, and the much-improved BNC-5S was active in time to meet the Clan Invasion.",
"manufacturer": [
"Diplass BattleMechs",
"Witten Industries",
"Defiance Industries",
"Star League Weapons Research"
],
"primaryfactory": [
"Apollo",
"Hesperus II",
"Hesperus II",
"New Earth"
],
"systemmanufacturer": {
"chassis": "Star League",
"engine": "GM",
"armor": "Starshield",
"communications": "Dalban",
"targeting": "Dalban"
},
"systemmode": {
"chassis": "XT",
"engine": "380",
"communications": "Commline",
"targeting": "HiRez-B"
}
}
```
I created a new section `fluff` that contains all the additional information that is usually not required for playing or creating record sheets.
As you can see, the MTF keys `systemmanufacturer` and `systemmode` can appear multiple times in an MTF file and contain a "subkey" (i.e. a nested
`key:value` pair within the value). I tried to separate all these "subkeys" into individual `key:value` pairs and organize them neatly. Also, the
`manufacturer` and `primaryfactory` values are always lists, since they often contain multiple values.
## Installation
### PyPi
```sh
pip install mtf2json
```
### Manual
Clone the repository and install the dependencies:
```sh
git clone https://github.com/juk0de/mtf2json.git
cd mtf2json
pip install .
```
## Usage
### CLI
To convert an MTF file to JSON, use the following command:
```sh
mtf2json --mtf-file <path_to_mtf_file> [--convert] [--json-file <path_to_json_file]
```
To query JSON data in the terminal (e.g. armor pips), pipe the output into `jq`:
```sh
mtf2json --mtf-file <path_to_mtf_file> | jq .armor.pips
```
### Library
```python
from mtf2json import read_mtf
from pathlib import Path
json_data = read_mtf(Path('/my/file.mtf'))
```
## Development
* Install [poetry](https://python-poetry.org/docs/)
* Clone repository and `cd` into it
* Execute `poetry install`
* To run tests, execute `poetry run pytest`
* To run `mtf2json`, execute `poetry run mtf2json`
## License
All source code of this project is licensed under the [MIT License](https://opensource.org/license/mit).
The included MTF files (used for testing) are part of the MegaMeklab project und thus are licensed under
the GPLv2 license (see https://github.com/MegaMek/#current-project-status).
Raw data
{
"_id": null,
"home_page": "https://github.com/juk0de/mtf2json",
"name": "mtf2json",
"maintainer": null,
"docs_url": null,
"requires_python": "<4.0,>=3.10",
"maintainer_email": null,
"keywords": "MTF, JSON, MegaMek, BattleTech",
"author": "juk0de",
"author_email": "juk0de@kadidlo.de",
"download_url": "https://files.pythonhosted.org/packages/02/14/7794ba40e0fb6af8064085238c25b2861e03861e68af0309915d49b23053/mtf2json-0.1.1.tar.gz",
"platform": null,
"description": "# mtf2json\n\n`mtf2json` converts [MegaMek](https://github.com/MegaMek/)'s MTF file format to JSON.\n\n## Project Goals and Features\n\n- Make it easy to parse MTF files in any modern programming language, using a well-known and documented format (JSON).\n- Provide a comprehensive JSON structure that includes all necessary data for generating record sheets.\n- Handle various issues and inconsistencies in the MTF format.\n\n## Why mtf2json?\n\nMegaMek is a great project, but the MTF format is difficult to work with. It's not a standardized format and there is no official\nspecification (at least I couldn't find one). Furhermore, an MTF file does not contain all information required to create an actual\nrecord sheet (e.g. the structure pips are missing).\n\n`mtf2json` does not simply create a 1:1 JSON version of the MTF data (that wouldn't be possible anyway) but restructures the data and\nadds information that is required for creating record sheets (see examples below).\n\n## Limitations and Supported Versions\n\n### Quad Mechs\nCurrently, `mtf2json` can only convert MTF files of **biped** mechs.\n\n### Supported MegaMek Version\n`0.49.19.1`\n\n### Testing\nTesting `mtf2json` is challenging, mostly because the MTF format is so loosely specified. I'm still not sure if I've actually seen all\npossible keys and understood all supported value syntaxes. Since there are over 4000 MTF files in MegaMek, I can't test and manually\nverify them all. If you have trouble converting an MTF file, create a Github issue and append the file, so I can verify and fix the issue.\n\n## JSON Structure and Examples\n\nHere are some comparisons of sections from an MTF file and their JSON counterpart:\n\n### The Basic Stuff\n\nMTF:\n```\nchassis:Atlas\nmodel:AS7-K\nmul id:144\n```\n\nJSON:\n```json\n\"chassis\": \"Atlas\",\n\"model\": \"AS7-K\",\n\"mul_id\": 144,\n```\nMost of the \"flat\" `key:value` pairs are also stored as `key:value` pairs in JSON. However, number values are stored as `int` if appropriate\n(they remain strings if they are used as names or model designation).\n\n### Rules Level\nMTF:\n```\nRules Level:2\n```\n\nJSON:\n```json\n\"rules_level\": 2,\n\"rules_level_str\": \"Standard\",\n```\nA string version of the rules level is automatically added. It's intended to be used in the record sheet and determined using the same algorithm\nas [MegaMek](https://github.com/juk0de/megamek/blob/78fb6e4616dd469dcb781c7da37d1bae748c45ce/megamek/src/megamek/common/SimpleTechLevel.java#L92).\n\n### Quirks\nMTF:\n```\nquirk:battle_fists_la\nquirk:battle_fists_ra\nquirk:command_mech\nquirk:distracting\nquirk:imp_com\n```\nJSON:\n```json\n\"quirks\": [\n \"battle_fists_la\",\n \"battle_fists_ra\",\n \"command_mech\",\n \"distracting\",\n \"imp_com\"\n],\n```\nNo more dealing with multiple identical keys. Just a simple JSON list.\n\n### Heat Sinks\nMTF:\n```\nHeat Sinks:20 Single\n```\nJSON:\n```json\n\"heat_sinks\": {\n \"quantity\": 20,\n \"type\": \"Single\"\n},\n```\nType and quantity of heat sinks are separate keys, no need for additional parsing.\n\n### Movement Points\nMTF:\n```\nWalk MP:3\nJump MP:0\n```\nJSON:\n```json\n\"walk_mp\": 3,\n\"run_mp\": 5,\n\"jump_mp\": 0,\n```\nThe movement points for running are calculated automatically, for your convenience.\n\n### Armor\nMTF:\n``` \narmor:Standard(Inner Sphere)\nLA armor:34\nRA armor:34\nLT armor:32\nRT armor:32\nCT armor:47\nHD armor:9\nLL armor:41\nRL armor:41\nRTL armor:10\nRTR armor:10\nRTC armor:14\n```\nJSON:\n```json\n\"armor\": {\n \"type\": \"Standard\",\n \"tech_base\": \"Inner Sphere\"\n \"pips\": {\n \"left_arm\": 34,\n \"right_arm\": 34,\n \"left_torso\": {\n \"front\": 32,\n \"rear\": 10\n },\n \"right_torso\": {\n \"front\": 32,\n \"rear\": 10\n },\n \"center_torso\": {\n \"front\": 47,\n \"rear\": 14\n },\n \"head\": 9,\n \"left_leg\": 41,\n \"right_leg\": 41\n },\n},\n```\nArmor type, tech base (if available) and pips are stored in the `armor` section.\nNote that the tech base is not always available in the MTF file (i.e. sometimes it's \"Standard Armor\", sometimes \"Standard(Inner Sphere))\".\nMaybe \"Standard\" always means \"Inner Sphere\", but I'm not sure, so I leave out the `tech_base` entry in that case.\n\n### Weapons\nMTF:\n```\nWeapons:3\n1 ISGaussRifle, Right Torso, Ammo:16\n1 ISERLargeLaser, Left Arm\n2 ISMediumPulseLaser, Center Torso (R)\n```\nJSON:\n```json\n\"weapons\": {\n \"1\": {\n \"ISGaussRifle\": {\n \"location\": \"right_torso\",\n \"facing\": \"front\",\n \"quantity\": 1,\n \"ammo\": 16\n }\n },\n \"2\": {\n \"ISERLargeLaser\": {\n \"location\": \"left_arm\",\n \"facing\": \"front\",\n \"quantity\": 1\n }\n },\n \"3\": {\n \"ISMediumPulseLaser\": {\n \"location\": \"center_torso\",\n \"facing\": \"rear\",\n \"quantity\": 2\n }\n },\n},\n```\nLocation, facing, quantity and ammo are all individual keys of each weapon. Additionally, each weapon has a slot number that represents\nthe order in the MTF file (and on the record sheet).\n\n### Structure\nMTF:\n```\nstructure:IS Standard\n```\nJSON:\n```json\n\"structure\": {\n \"type\": \"Standard\",\n \"tech_base\": \"Inner Sphere\",\n \"pips\": {\n \"head\": 3,\n \"center_torso\": 31,\n \"left_torso\": 21,\n \"right_torso\": 21,\n \"left_arm\": 17,\n \"right_arm\": 17,\n \"left_leg\": 21,\n \"right_leg\": 21\n }\n},\n```\nStructure type and tech base (if available) are stored in the `structure` section. The pips are added afterwards, based on the mech's tonnage.\n\"IS\" is converted to \"Inner Sphere\", in order to be consistent to the tech base naming in the `armor` section.\nNote that the tech base is not always available in the MTF file (i.e. sometimes it's \"IS Standard\", sometimes just \"Standard\"). Maybe \"Standard\"\nalways means \"Inner Sphere\", but I'm not sure, so I leave out the `tech_base` entry in that case.\n\n### Critical Slots\nMTF:\n```\nLeft Arm:\nShoulder\nUpper Arm Actuator\nLower Arm Actuator\nHand Actuator\nHeat Sink\nHeat Sink\nISERLargeLaser\nISERLargeLaser\nISAntiMissileSystem\n-Empty-\n-Empty-\n-Empty-\n```\nJSON:\n```json\n\"critical_slots\": {\n \"left_arm\": {\n \"1\": \"Shoulder\",\n \"2\": \"Upper Arm Actuator\",\n \"3\": \"Lower Arm Actuator\",\n \"4\": \"Hand Actuator\",\n \"5\": \"Heat Sink\",\n \"6\": \"Heat Sink\",\n \"7\": \"ISERLargeLaser\",\n \"8\": \"ISERLargeLaser\",\n \"9\": \"ISAntiMissileSystem\",\n \"10\": null,\n \"11\": null,\n \"12\": null\n },\n}\n```\nAll critical slots data is stored in the `critical_slots` section, with one section per location. Every slot has the slot number as key,\nmaking it very easy to check the content of each slot directly. The `-Empty-` string is replaced by an actual `null` (python `None`).\n\n### Fluff\nMTF:\n```\noverview:The Banshee, introduced in 2445 by the Terran Hegemony, is a 'Mech that was designed specifically for close-assault operations during the early years of BattleMech warfare.\ncapabilities:A contemporary of the Mackie and Emperor, the Banshee is undeniably fast for one of the heaviest 'Mechs ever produced, and with fifteen tons of armor it is better protected than most other assault 'Mechs. However the use of a massive GM 380 fusion engine left little room for weaponry, and even at the time of its introduction the Banshee was considered undergunned compared to its privately-built competition. As critics noted, what use was impressive armor and mobility if a better-armed enemy could overwhelm and destroy it? The result was a mediocre 'Mech which even the lowly Rifleman could beat as long as it prevented the Banshee's mass from coming into play.\ndeployment:The two primary weapons on the Banshee, a Magna Hellstar PPC matched up with an Imperator-A Autocannon/5 with one ton of ammo, are mounted in the right and left sides of its torso. The two systems complement each other with similar range profiles and would provide good firepower for a 'Mech weighing at half the tonnage of the Banshee. Perversely for a close-combat 'Mech their minimum ranges means both weapons present targeting difficulties as the Banshee closes in on its enemy, and a Magna Mk I Small Laser mounted in its head appears to have been installed as an afterthought. Sixteen heat sinks help keep the 'Mech cool though, and thanks to its prodigious size the Banshee can turn lighter 'Mechs to scrap in hand-to-hand fighting.\nhistory: The Hegemony soldiered on though, producing five thousand Banshees in a decade before its poor combat performance finally forced them to stop production in 2455 and the 'Mech was relegated to training and militia units for the next few centuries. Even during the Succession Wars the 'Mech's poor reputation meant many commanders saw it as a liability rather than an asset; unless they were fighting on a backwater Periphery world or as part of a poorly-equipped outfit, most Banshees were placed in second-line reserves to provide fire support or fulfill the role of brawlers so that better-armed 'Mechs need not engage in hand-to-hand combat. In this way fully a third of the original Banshee production run remained operational by the dawn of the thirty-first century and could be found throughout the Inner Sphere and Periphery, with the lion's share residing within the Lyran Commonwealth. Though a few attempts had been made over the years to improve the Banshee, Defiance Industries was the first to produce a variant which markedly improved on the original and was suggested by many of its original critics. With help from the Federated Suns and access to blueprints from the original Hesperus II factories, the BNC-3S proved to be such a success the Lyrans began fielding them in front line units, surprising their enemies who ignored them to focus on \"real\" threats with thoroughly unexpected firepower. Under the Federated Commonwealth improvements would continue to be made, though not at the same priority level as other projects, and the much-improved BNC-5S was active in time to meet the Clan Invasion.\nmanufacturer:Diplass BattleMechs,Witten Industries,Defiance Industries,Star League Weapons Research\nprimaryfactory:Apollo,Hesperus II,Hesperus II,New Earth\nsystemmanufacturer:CHASSIS:Star League\nsystemmode:CHASSIS:XT\nsystemmanufacturer:ENGINE:GM\nsystemmode:ENGINE:380\nsystemmanufacturer:ARMOR:Starshield\nsystemmanufacturer:COMMUNICATIONS:Dalban\nsystemmode:COMMUNICATIONS:Commline\nsystemmanufacturer:TARGETING:Dalban\nsystemmode:TARGETING:HiRez-B\n```\nJSON:\n```json\n\"fluff\": {\n \"overview\": \"The Banshee, introduced in 2445 by the Terran Hegemony, is a 'Mech that was designed specifically for close-assault operations during the early years of BattleMech warfare.\",\n \"capabilities\": \"A contemporary of the Mackie and Emperor, the Banshee is undeniably fast for one of the heaviest 'Mechs ever produced, and with fifteen tons of armor it is better protected than most other assault 'Mechs. However the use of a massive GM 380 fusion engine left little room for weaponry, and even at the time of its introduction the Banshee was considered undergunned compared to its privately-built competition. As critics noted, what use was impressive armor and mobility if a better-armed enemy could overwhelm and destroy it? The result was a mediocre 'Mech which even the lowly Rifleman could beat as long as it prevented the Banshee's mass from coming into play.\",\n \"deployment\": \"The two primary weapons on the Banshee, a Magna Hellstar PPC matched up with an Imperator-A Autocannon/5 with one ton of ammo, are mounted in the right and left sides of its torso. The two systems complement each other with similar range profiles and would provide good firepower for a 'Mech weighing at half the tonnage of the Banshee. Perversely for a close-combat 'Mech their minimum ranges means both weapons present targeting difficulties as the Banshee closes in on its enemy, and a Magna Mk I Small Laser mounted in its head appears to have been installed as an afterthought. Sixteen heat sinks help keep the 'Mech cool though, and thanks to its prodigious size the Banshee can turn lighter 'Mechs to scrap in hand-to-hand fighting.\",\n \"history\": \"The Hegemony soldiered on though, producing five thousand Banshees in a decade before its poor combat performance finally forced them to stop production in 2455 and the 'Mech was relegated to training and militia units for the next few centuries. Even during the Succession Wars the 'Mech's poor reputation meant many commanders saw it as a liability rather than an asset; unless they were fighting on a backwater Periphery world or as part of a poorly-equipped outfit, most Banshees were placed in second-line reserves to provide fire support or fulfill the role of brawlers so that better-armed 'Mechs need not engage in hand-to-hand combat. In this way fully a third of the original Banshee production run remained operational by the dawn of the thirty-first century and could be found throughout the Inner Sphere and Periphery, with the lion's share residing within the Lyran Commonwealth. Though a few attempts had been made over the years to improve the Banshee, Defiance Industries was the first to produce a variant which markedly improved on the original and was suggested by many of its original critics. With help from the Federated Suns and access to blueprints from the original Hesperus II factories, the BNC-3S proved to be such a success the Lyrans began fielding them in front line units, surprising their enemies who ignored them to focus on \\\"real\\\" threats with thoroughly unexpected firepower. Under the Federated Commonwealth improvements would continue to be made, though not at the same priority level as other projects, and the much-improved BNC-5S was active in time to meet the Clan Invasion.\",\n \"manufacturer\": [\n \"Diplass BattleMechs\",\n \"Witten Industries\",\n \"Defiance Industries\",\n \"Star League Weapons Research\"\n ],\n \"primaryfactory\": [\n \"Apollo\",\n \"Hesperus II\",\n \"Hesperus II\",\n \"New Earth\"\n ],\n \"systemmanufacturer\": {\n \"chassis\": \"Star League\",\n \"engine\": \"GM\",\n \"armor\": \"Starshield\",\n \"communications\": \"Dalban\",\n \"targeting\": \"Dalban\"\n },\n \"systemmode\": {\n \"chassis\": \"XT\",\n \"engine\": \"380\",\n \"communications\": \"Commline\",\n \"targeting\": \"HiRez-B\"\n }\n}\n```\nI created a new section `fluff` that contains all the additional information that is usually not required for playing or creating record sheets.\nAs you can see, the MTF keys `systemmanufacturer` and `systemmode` can appear multiple times in an MTF file and contain a \"subkey\" (i.e. a nested\n`key:value` pair within the value). I tried to separate all these \"subkeys\" into individual `key:value` pairs and organize them neatly. Also, the\n`manufacturer` and `primaryfactory` values are always lists, since they often contain multiple values.\n\n## Installation\n\n### PyPi\n\n```sh\npip install mtf2json\n```\n\n### Manual\nClone the repository and install the dependencies:\n\n```sh\ngit clone https://github.com/juk0de/mtf2json.git\ncd mtf2json\npip install .\n```\n\n## Usage\n\n### CLI\nTo convert an MTF file to JSON, use the following command:\n\n```sh\nmtf2json --mtf-file <path_to_mtf_file> [--convert] [--json-file <path_to_json_file]\n```\n\nTo query JSON data in the terminal (e.g. armor pips), pipe the output into `jq`:\n```sh\nmtf2json --mtf-file <path_to_mtf_file> | jq .armor.pips\n```\n\n### Library\n```python\nfrom mtf2json import read_mtf\nfrom pathlib import Path\njson_data = read_mtf(Path('/my/file.mtf'))\n```\n\n## Development\n* Install [poetry](https://python-poetry.org/docs/)\n* Clone repository and `cd` into it\n* Execute `poetry install`\n* To run tests, execute `poetry run pytest`\n* To run `mtf2json`, execute `poetry run mtf2json`\n\n## License\n\nAll source code of this project is licensed under the [MIT License](https://opensource.org/license/mit).\nThe included MTF files (used for testing) are part of the MegaMeklab project und thus are licensed under\nthe GPLv2 license (see https://github.com/MegaMek/#current-project-status).\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Convert the MegaMek MTF format to JSON.",
"version": "0.1.1",
"project_urls": {
"Homepage": "https://github.com/juk0de/mtf2json",
"Repository": "https://github.com/juk0de/mtf2json"
},
"split_keywords": [
"mtf",
" json",
" megamek",
" battletech"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f273179513b6ea90b1693f478b385e7cb2c95ea11fb7d547fe90acc1f0af0469",
"md5": "52c0aab4df944e1ea59d4f66cd5f67c1",
"sha256": "61c0f968dd60b798bdc1ba0dd49396da2d00b96a85f45c154c3c98849f7f84f9"
},
"downloads": -1,
"filename": "mtf2json-0.1.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "52c0aab4df944e1ea59d4f66cd5f67c1",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4.0,>=3.10",
"size": 14723,
"upload_time": "2024-06-16T07:47:02",
"upload_time_iso_8601": "2024-06-16T07:47:02.125317Z",
"url": "https://files.pythonhosted.org/packages/f2/73/179513b6ea90b1693f478b385e7cb2c95ea11fb7d547fe90acc1f0af0469/mtf2json-0.1.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "02147794ba40e0fb6af8064085238c25b2861e03861e68af0309915d49b23053",
"md5": "bc430a038807c77a19d348990082cc58",
"sha256": "7f9f486fba8ba5f06aed46b8196ccb46cfc4fa00e92998a8c70c293c9a848233"
},
"downloads": -1,
"filename": "mtf2json-0.1.1.tar.gz",
"has_sig": false,
"md5_digest": "bc430a038807c77a19d348990082cc58",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4.0,>=3.10",
"size": 17630,
"upload_time": "2024-06-16T07:47:03",
"upload_time_iso_8601": "2024-06-16T07:47:03.825342Z",
"url": "https://files.pythonhosted.org/packages/02/14/7794ba40e0fb6af8064085238c25b2861e03861e68af0309915d49b23053/mtf2json-0.1.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-06-16 07:47:03",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "juk0de",
"github_project": "mtf2json",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"lcname": "mtf2json"
}
JSON
