Black Hawk (Standard) 2 has wrong deployment fluff

Open Beginner friendly
#539 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
content

Research direction

Locate the data entry for Black Hawk (Standard) 2 and read its deployment fluff alongside the issue's replacement text. Update the incorrect description using the TRO: Dark Age, p.70 citation as reference. Done means the entry describes the two ATM 6 launchers replacing the four Streak SRM 4s and no longer contains the imagined loadout.

Written by the indexing model from the issue text.

Description

Bug
What kind of data?

Unit fluff

Which entry?

Black Hawk (Standard) 2

What's wrong

The Black Hawk (Standard) 2 has deployment fluff that describes a completely incorrect/imagined loadout, currently written as follows:

The Black Hawk 2 replaces both the laser and missile armament with a quartet of SRM-6 launchers and a pair of medium pulse lasers, dramatically shifting the design toward close-range brawling. Four tons of SRM ammunition feed the launchers through extended engagements, and the pulse lasers' improved accuracy at short range complements the missile barrage. This variant sacrifices the base model's long-range capability entirely but delivers far greater damage output inside three hundred meters, making it a preferred choice for urban combat and dense terrain operations.

What it should be

In response to market demands, Clan Sea Fox offered two variants of the standard Black Hawk. The Black Hawk 2 replaces the four Streak SRM 4s with two ATM 6 launchers, providing greater range, accuracy and choice of munitions.

Source

TRO: Dark Age, p.70

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
Dominant language
Module Management System
Stars
3
Forks
72
Avg merge
14h 20m
Merged PRs (30d)
38

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MegaMek/mm-data

All issues in MegaMek/mm-data

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.