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

White Space issues on Briefing Screen #4958

Closed
7 tasks done
repligator opened this issue Oct 1, 2024 · 4 comments
Closed
7 tasks done

White Space issues on Briefing Screen #4958

repligator opened this issue Oct 1, 2024 · 4 comments
Labels
Bug Severity: Low Issues described as low severity as per the new issue form

Comments

@repligator
Copy link
Collaborator

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 *

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

Brief Description *

See attached screenshot. I've tried editing the strings without any success, so it looks like the issue is with the formatting. Also, note that this bug is not caused by #4928 , as it predates it.

Screenshot_20241001_093427

Steps to Reproduce

No response

Operating System *

Windows 11

Java Version *

17

MekHQ Suite Version *

v0.50.0

Custom MekHQ Version

#4928

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
@repligator repligator added the Bug label Oct 1, 2024
@IllianiCBT
Copy link
Collaborator

This will be caused by some xml weirdness resulting from the Mech->Mek changes. I think I caught all of them, when working on #4928 so closing this as resolved. Once that PR is merged, though, please keep an eye out for any you think I missed. We can re-open this report if necessary. :)

@repligator
Copy link
Collaborator Author

The screenshot is actually from when I was testing #4928 early today.

@IllianiCBT
Copy link
Collaborator

image

Re-opening

@IllianiCBT IllianiCBT reopened this Oct 1, 2024
@HammerGS HammerGS added the Severity: Low Issues described as low severity as per the new issue form label Oct 7, 2024
@IllianiCBT
Copy link
Collaborator

Closing as resolved…

…again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Severity: Low Issues described as low severity as per the new issue form
Projects
None yet
Development

No branches or pull requests

3 participants