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

Mass Repairing pod damaged parts throws NPE #4608

Closed
repligator opened this issue Aug 11, 2024 · 1 comment · Fixed by #4682
Closed

Mass Repairing pod damaged parts throws NPE #4608

repligator opened this issue Aug 11, 2024 · 1 comment · Fixed by #4682
Assignees

Comments

@repligator
Copy link
Collaborator

Environment

Java 17
Linux
Master (latest PR a16a4fb)

Description

I noticed one of my mechs was damaged, but wasn't listed in the Repair Bay. I figured it was one of the fixes-itself-when-you-save-and-load issues, so I saved, loaded, and hit mass repair. MHQ through an NPE. I closed MHQ completely, reloaded the save, hit mass repair. Same NPE. Hopefully this may shed some light on the invisible broken parts issue(s).

mekhq.MekHQ.lambda$main$1(MekHQ.java:294) - Uncaught Exception Detected
java.lang.ClassCastException: class mekhq.campaign.parts.PodSpace cannot be cast to class mekhq.campaign.parts.Part (mekhq.campaign.parts.PodSpace and mekhq.campaign.parts.Part are in unnamed module of loader 'app')

Files

mekhq.log
Omega Galaxy31540101.cpnx.gz

@repligator
Copy link
Collaborator Author

Looks like it gets thrown when mass repairing pod-space weapons, and the invisible part was unrelated.

mekhq.log
Autosave-1-Omega Galaxy-31540731.cpnx.gz

@repligator repligator added the Mass Repair/Mass Salvage Any issue around MSRS label Aug 13, 2024
@repligator repligator changed the title Repairing previously invisible damaged parts throws NPE Mass Repairing pod damaged parts throws NPE Aug 13, 2024
@Sleet01 Sleet01 self-assigned this Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants