MegaMek / MegaMek/mm-data

Intercept Engagement needs clarification

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

Nobody has claimed this yet.

Bug
Dominant language
Module Management System
Stars
3
Forks
72
Avg merge
11h 8m
Merged PRs (30d)
36

Description

What kind of data?

Something else

Which entry?

Intecept Engagment

What's wrong

Intercept Engagement needs a scenario note for clarification (Requested by Illiani)

What it should be

It should say pick a direction and go with it

Source

Illiani

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

  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.

Research direction

Locate the “Intecept Engagment” entry in the mm-data repository and review how its scenario note is represented. Clarify the note so it communicates that the user should pick a direction and follow it, then verify the updated entry is consistent with nearby data.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.