Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue] Fuel-Air insta-kill result display is confusing #6501

Open
4 tasks done
ManoftheSea opened this issue Feb 5, 2025 · 0 comments
Open
4 tasks done

[Issue] Fuel-Air insta-kill result display is confusing #6501

ManoftheSea opened this issue Feb 5, 2025 · 0 comments

Comments

@ManoftheSea
Copy link

Brief Description *

I dropped the bomb on multiple infantry, and saw this in the report:
Fuel-air weapon against infantry may result in automatic destruction. Needs 9-, rolled 6 [4 + 2] (2d6) + 2 (distance from blast center) : destroyed!
Fuel-air weapon against infantry may result in automatic destruction. Needs 9-, rolled 9 [7 + 2] (2d6) + 2 (distance from blast center) : destroyed!

I initially understood this to be that the first roll was a six plus two and the second a nine plus two. Digging into the underlying rolls, it turns out the first actually rolled a [3, 1] and the latter a [2, 5]. This was surprising in two ways:

  • The first roll added 1 to each die, the second roll added 2 to one and 0 to the other.
  • The grouping of the terms looks like "total-rolled [rolls] (dice) modifier", but it's actually "TN, total [modified rolls] (dice) modifiers"

It seems like the use of a "less than or equal" target is already weird. But I would have expected the UI to say "Needs 8; rolled 7 : destroyed", where 8 is underlined and brings up the explanation of 10 (fuel-air save) - 2 (range) and 7 shows range [1-6], result: 7, rolls 2,5.

3. Steps to Reproduce

  1. put infantry on the board
  2. fire fuel-air munitions too close to them (here, 2 hexes away)
  3. read the report

Attach Files

No response

Severity *

Low (Minor/Nuisance): Minor glitches or cosmetic issues that don't affect gameplay and occur rarely.

MegaMek Suite Version *

v0.49.19.1

Operating System *

Linux (NixOS 24.11)

Java Version *

21.0.5

Final Verification

  • I confirm this is a single, unique issue that hasn't been reported before
  • I have included all necessary information and files to help reproduce this issue
  • I have asked on MegaMek Discord about this issue
  • I have confirmed this issue is being opened on the correct repository: MegaMek, MegaMekLab, or MekHQ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant