Nagasawa Fluff Issues
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 fluff
Which entry?
Nagasawa
What's wrong
The Capabilities, Overview, Deployment and History sections of the fluff all state that the Nagasawa was developed by the DCMS and discuss its history.
What it should be
Every single part of the fluff needs to be rewritten, as the Nagasawa is a Clan Sea Fox dropship, not a DCMS one. Additionally, in MegamekLab it has 432 unallocated armor points, which make the design invalid.
Source
Technical Readout: 3145 Mercenaries, pp. 52–53: "Nagasawa"
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 Nagasawa unit entry and compare its Capabilities, Overview, Deployment, and History fluff with Technical Readout: 3145 Mercenaries, pp. 52–53. Correct the Clan Sea Fox attribution and history, resolve the 432 unallocated armor points reported in MegamekLab, and verify that the design is valid.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100