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

Fatigue in list view does not agree with fatigue on pilot UI #4999

Open
7 tasks done
BlueThing00 opened this issue Oct 7, 2024 · 2 comments
Open
7 tasks done

Fatigue in list view does not agree with fatigue on pilot UI #4999

BlueThing00 opened this issue Oct 7, 2024 · 2 comments
Labels
Severity: Medium Issues described as medium severity as per the new issue form

Comments

@BlueThing00
Copy link

Prerequisites and Pre-Issue Checklist

  • I'm reporting the issue to the correct repository:

  • MegaMek

  • MegaMekLab

  • MekHQ

  • I've tested the issue against at least the latest MILESTONE version

  • I've asked on the MegaMek Discord about the error

  • I've reviewed the BattleTech rules and MekHQ documentation, and I've confirmed that something isn't working as intended.

  • I've searched the Github tracker and haven't found the issue listed

Severity *

Medium (Gameplay Limitation): Non-core functionality is impaired, providing a suboptimal but playable experience.

Brief Description *

image

The fatigue in the list view is 5.

The fatigue in the pilot UI is 2.

This appears to be one displaying base fatigue and the other displaying effective fatigue.

Steps to Reproduce

Play a campaign with fatigue enabled.

Look at the UI after one or more Scenarios have been completed.

Operating System *

Windows 11

Java Version *

17

MekHQ Suite Version *

v0.50.0

Custom MekHQ Version

No response

Attach Files

No response

Final Checklist

  • I've checked to make sure that this issue has not already been filed
  • I'm reporting only one issue in this ticket for clarity and focus
@BlueThing00
Copy link
Author

If those are meant to be different, they should have different names (e.g. "Fatigue" and "Effective Fatigue").

Plus, Since the effective fatigue seems to be the one that really matters (if I'm understanding the fatigue rules properly), it should be available in a list view somewhere.

@IllianiCBT
Copy link
Collaborator

Yeah, I must have just called fatigue instead of effective fatigue when writing the code for that part of the table. Easily fixed.

@HammerGS HammerGS added the Severity: Medium Issues described as medium severity as per the new issue form label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Severity: Medium Issues described as medium severity as per the new issue form
Projects
None yet
Development

No branches or pull requests

3 participants