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
java.lang.NullPointerException: Cannot invoke "String.startsWith(String)" because "name" is null
at megamek.server.ServerBoardHelper.getPossibleGameBoard(ServerBoardHelper.java:112)
at megamek.client.ui.swing.lobby.PlayerSettingsDialog.setupStartGrid(PlayerSettingsDialog.java:736)
at megamek.client.ui.swing.lobby.PlayerSettingsDialog.startSection(PlayerSettingsDialog.java:528)
at megamek.client.ui.swing.lobby.PlayerSettingsDialog.createCenterPane(PlayerSettingsDialog.java:318)
at megamek.client.ui.baseComponents.AbstractButtonDialog.initialize(AbstractButtonDialog.java:131)
at megamek.client.ui.swing.lobby.PlayerSettingsDialog.<init>(PlayerSettingsDialog.java:137)
at megamek.client.ui.swing.ClientGUI.customizePlayer(ClientGUI.java:697)
at megamek.client.ui.swing.ClientGUI.actionPerformed(ClientGUI.java:865)
at megamek.client.ui.swing.CommonMenuBar.lambda$actionPerformed$0(CommonMenuBar.java:446)
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 MegaMek 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 *
Critical (Game-breaking/Crash): The game crashes or a core feature (like saving, loading, or network connection) is completely unusable.
Brief Description *
NPE when trying to get to Player Settings in a game that was loaded.
Encountered while investigating #6277
Steps to Reproduce
Operating System *
Windows 11
Java Version *
17.0.13
MegaMek Suite Version *
Free Text (type manually)
Custom MegaMek Version
Latest
Attach Files
4.sav.gz
megamek.log
Final Checklist
The text was updated successfully, but these errors were encountered: