MegaMek / MegaMek/mm-data

Jumping Jack & Hopping Jack SPA

Open
#361 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

The Hopping Jack SPA, while unofficial, appears to be intended as a stepping stone towards the official Jumping Jack SPA.
This is not reflected in the way the current SPAs are set-up with their prerequisites, which merely makes Hopping Jack incompatible with the latter without properly establishing them as a sequential upgrade path (or with one overwriting the other).

Image

This may be an intended change, in which case this issue can be discarded.

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

Inspect the current Jumping Jack and Hopping Jack SPA definitions and their prerequisite data. Compare how each SPA is intended to establish an upgrade path, then determine whether the prerequisites should allow sequential installation or replacement. Done means the intended relationship is represented consistently, or the issue is confirmed as intentional and can be discarded.

Written by the indexing model from the issue text.

Assessment

Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.