Hi all, I have a weird technical issue that is stopping us from playing the game. A player has disconnected partway through the game, upon reconnecting they are unable to reconnect to their old player instance. I can not kick the old player, I can kick the new player. I have access to all the logs across two devices we tried to use.
#Player reconnecting as ghost, unable to kick the human to relinquish control.
1 messages · Page 1 of 1 (latest)
Useful log data:
15:52:45,703 INFO [megamek.MegaMek] {main}
megamek.MegaMek.initializeLogging(MegaMek.java:146) - Starting MegaMek v0.50.0
Build Date: 2024-09-01T14:30:43.590738
Today: 2025-02-26
Origin Project: MegaMek
Java Vendor: Ubuntu
Java Version: 21.0.6
Platform: Linux 6.8.0-54-generic (amd64)
System Locale: en_CA
Total memory available to MegaMek: 4 GB
MM Code Revision: ce95ba3d3c12c0e4e116cb713e47493316831daa
MML Code Revision: 19b12fa9a622458ed00b0dc94ef1d0f2b19bbb66
MHQ Code Revision: eaa1134aa318d26121a879c24651e16e84252b39
...
20:56:19,478 INFO [megamek.server.Server] {Connection 3}
megamek.server.Server.receivePlayerName(Server.java:772) - s: player #3, <player> connected from /<ip>
...
23:59:35,583 INFO [megamek.server.Server] {Connection 7}
megamek.server.Server.receivePlayerName(Server.java:772) - s: player #6, <same player> connected from /<same ip>
Running on: Welcome to Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-54-generic x86_64)
quick check: does it sounds like this issue? https://github.com/MegaMek/megamek/issues/6535
Yes but also no. The most recent save we were using has that problem, however our backup save does not contain two player entries for the same player name. Both saves had the same issue where the player connecting did not gain control of their """player""" but rather was stuck in as an observer
I tried to save data edit to remove the offending bonus player entry, and it is failing to read the file.
When I tried that, the issue was that I had to remove every "Seen by [removed player ID]" reference from units in the save file
Once I excised all of those, it loaded properly. Basically you can't have any references to the removed player or it'll go:
Interesting that you had a similar issue without a duplicate player name, though. That's concerning
It might just be a continued problem with what caused the duplicate connection in the first case. A reconnect likely spawned a second player, and then I saved with that configuration, and then problems occurred on reload.
Their internet connection was not happy that day
I can confirm, a previous save is not infected and functions correctly. We just had a weird save that generated a second player and broke it (I think).
And then the save on server locked it in