Merlin MLN-SX is missing Armored Component(Light Engine)
Nobody has claimed this yet.
- Dominant language
- Module Management System
- Stars
- 3
- Forks
- 72
- Avg merge
- 11h 8m
- Merged PRs (30d)
- 36
Description
What kind of data?
Unit stats or equipment
Which entry?
Merlin MLN-SX
What's wrong
The MekLab entry for the Merlin SX is missing the fact that it's Light Engine is Armored(as per the "Armored Component" equipment). This is mentioned in it's Deployment Lore, MUL shows that it's Alpha Strike card has the ARM special and checking XTRO:Boondocks confirms that the Light Engine is armored, both in the write-up's Weaponry section and on the Record Sheet.
The lore entry: "The entire internal structure was replaced with experimental endo-composite construction, and the standard engine was swapped for a lighter model, freeing weight for five tons of armored engine shielding that protects the engine and side torsos."
What it should be
The Light Engine should be Armored, with the sheet having the Armored circles and the Alpha Strike card having the ARM special.
Source
XTRO:Boondocks, MUL 2.0
Screenshots or files
No response
Before you submit
- This report only contains one issue or request, and I haven't already reported it
- This is a data problem, not a program bug - if the program misbehaves with correct data, it belongs in MegaMek
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository for the Merlin MLN-SX MekLab entry and inspect how its Light Engine and equipment data are represented. Compare the entry with XTRO:Boondocks and MUL 2.0; done means the Light Engine is marked Armored, the sheet shows the armored circles, and the Alpha Strike card includes ARM.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100