If I exit a boss instance using the exit button and try to start the boss fight again, it doesn't start; it only starts if I return to the character screen and restart.

[zealous000]

If I exit a boss instance using the exit button and try to start the boss fight again, it doesn't start; it only starts if I return to the character screen and restart.

[zealous000]

Binary Analysis — Root Cause Identified

Status: Cannot fix via JSON — instance state management in C++

Root Cause

The dungeon/instance state machine does not properly reset when a player leaves via the exit button. The server likely keeps the player's dungeon state as "in-progress" or "completed" instead of resetting to "available."

Binary Evidence

• ContentsDungeonPacket.cpp exists in debug symbols (handles dungeon packets)
• CLIENT_GAME_LEAVE_SECRET_DUNGEON packet IS implemented
• GAME_WORLD_LEAVE_SECRET_DUNGEON and GAME_WORLD_ENTER_SECRET_DUNGEON exist
• Multiple dungeon-related TODOs found: TODO _CLIENT_GAME_DUNGEON_TICKET_INFO, TODO _CLIENT_GAME_DUNGEON_TICKET_CHARGE — ticket system unimplemented

The leave handler likely sends the world server a leave notification but does not properly reset the per-character dungeon entry state. The character selection workaround works because the full login process reinitializes all character states from scratch.

This follows the same pattern as Issues #96 and #101 — entity/state desynchronization that only a full re-login fixes, suggesting a systemic issue with state management.

Fix Required

Fix dungeon state reset in ContentsDungeonPacket.cpp when processing CLIENT_GAME_LEAVE_SECRET_DUNGEON — ensure the character's dungeon state is fully cleared so re-entry is allowed.

Source files (from debug symbols):

• G:\Mir4\...\Contents\Dungeon\ContentsDungeonPacket.cpp
• G:\Mir4\...\Libraries\Common\Resource\_res_dungeon_script.h
• G:\Mir4\...\Libraries\Common\Resource\_res_instance_dungeon_info.h