MegaMek / MegaMek/mm-data

Recommened adjustment to Diversion engagment

Open Beginner friendly
#563 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?

Diversion engagement

What's wrong

6 turns is very slim unless you have very fast units. Even my units going 5/8 struggled to reach the edge in time. Recommend uping up to 8 turns. (Requested by Illinai on discord)

What it should be

Diversion engagement time limit should be turned up to 8 turns to account for larger maps.

Source

Playtesting

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

Start by locating the Diversion engagement data entry in the mm-data repository and confirm how its turn limit is represented. Update the limit from 6 to 8 turns, then verify that the entry reflects the requested value for larger maps.

Written by the indexing model from the issue text.

Assessment

Domain
game-dev
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.