You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
3. Steps to Reproduce
Launch Megamek
Open client settings
On Minimap tab, verify the default SHOWS as "cyberpunk" but has the default tileset in the preview
Make no changes and hit "OK" to save/close Client Settings
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.
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:
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:
3. Steps to Reproduce
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
The text was updated successfully, but these errors were encountered: