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

Player Dave & Princess unable to take control of Player Entity Dave (GHOST) #6074

Open
7 tasks done
wolfstormash opened this issue Oct 6, 2024 · 0 comments
Open
7 tasks done
Labels
Severity: Critical Issues described as critical as per the new issue form

Comments

@wolfstormash
Copy link

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 *

Prior to saving my friend Dave changed his VPN IP Address and disconnected, and was unable to reconnect to his slot, After reloading and trying the next day, he is still unable to reconnect to his player slot, When trying to replace him with princess it also puts princess as an observer instead of in control of player entity Dave(ghost)

Steps to Reproduce

Load save, try to replace Dave w/ a princess or connecting as "Dave".

Have not tried reproducing by switching VPN so unsure if it can be recreated and my friends and I personally don't have the time to test it, but was advised to upload it and the save here on the megamek discord.

Operating System *

Windows 10

Java Version *

Eclipse adoptium 17.0.12

MegaMek Suite Version *

v0.50.0

Custom MegaMek Version

No response

Attach Files

weirdsavebug.sav.gz

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
@SJuliez SJuliez added the Severity: Critical Issues described as critical as per the new issue form label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Severity: Critical Issues described as critical as per the new issue form
Projects
None yet
Development

No branches or pull requests

2 participants