Fix player challenge state persistence on disconnect

- Remove players from playerChallengeMap when they disconnect
- Add removePlayerFromChallenge method to ChallengeManager
- Ensure players start in the lobby when reconnecting without auto-joining their previous challenge

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: finreinhard

CLAUDE.md

@@ -1,3 +1,7 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
 # ChallengePlugin Development Guide
 
 ## Build & Test Commands

src/main/kotlin/li/angu/challengeplugin/listeners/PlayerConnectionListener.kt

@@ -46,8 +46,9 @@ class PlayerConnectionListener(private val plugin: ChallengePluginPlugin) : List
             // Remove the player from the challenge to pause timer if needed
             challenge.removePlayer(player)
 
-            // But keep the player in the challenge map for reconnection
-            // The player data is saved and we'll restore it when they reconnect
+            // Remove the player from the playerChallengeMap
+            // This ensures they'll start in the lobby when reconnecting
+            plugin.challengeManager.removePlayerFromChallenge(player.uniqueId)
         }
     }
 

src/main/kotlin/li/angu/challengeplugin/managers/ChallengeManager.kt

@@ -389,6 +389,14 @@ class ChallengeManager(private val plugin: ChallengePluginPlugin) {
 
         return false
     }
+    
+    /**
+     * Removes a player from the challenge map without affecting the player object.
+     * Used when a player disconnects to ensure they start fresh in the lobby next time.
+     */
+    fun removePlayerFromChallenge(playerId: UUID) {
+        playerChallengeMap.remove(playerId)
+    }
 
     fun completeChallenge(challengeId: UUID) {
         val challenge = activeChallenges[challengeId] ?: return