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

[0.50.03-SNAPSHOT] Default Minimap theme is set to Cyberpunk #6464

Closed
4 tasks done
PhoenixHeart512 opened this issue Jan 30, 2025 · 1 comment · Fixed by #6467
Closed
4 tasks done

[0.50.03-SNAPSHOT] Default Minimap theme is set to Cyberpunk #6464

PhoenixHeart512 opened this issue Jan 30, 2025 · 1 comment · Fixed by #6467

Comments

@PhoenixHeart512
Copy link

Brief Description *

When opening the Megamek Client Settings for the first time, the Minimap tab shows the default theme as "Cyberpunk" on the dropdown, but the minimap theme preview window shows the "default" theme visually.

If you start a game WITHOUT opening client settings at all, the minimap appears normal. If you open Client Settings for the first time with the game already started, you get this:

Image

If you open Client Settings and then save and close without making any changes whatsoever and then start a game, it saves the minimap theme as Cyberpunk and you get this:

Image

3. Steps to Reproduce

  1. Launch Megamek
  2. Open client settings
  3. On Minimap tab, verify the default SHOWS as "cyberpunk" but has the default tileset in the preview
  4. Make no changes and hit "OK" to save/close Client Settings
  5. Start a game, minimap will now be Cyberpunk tileset

Attach Files

No response

Severity *

High (Major Disruption): A major feature is broken or incorrect, but a workaround exists.

MegaMek Suite Version *

v0.50.03-SNAPSHOT Build Date: 2025-01-30T03:19:43.517489924

Operating System *

Windows 10

Java Version *

Java Version: 17.0.6

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

Successfully merging a pull request may close this issue.

2 participants