Description
When a player leaves a clan party lobby (especially while in a clan-vs-clan lobby or when the leader exits), the remaining party members sometimes see a corrupted player slot. The slot shows an invalid or symbolic name (e.g. Member, ()#(%¤)#%=), while some stats (notably clan contribution) still appear populated.
Reproduce
- Create a clan party
- Enter a clan-vs-clan lobby (two clans facing each other)
- Have one non-leader party member leave the party before the match starts
- Return to the clan party lobby
- Observe that one party member slot is corrupted:
Nickname is invalid or empty
Stats belong to a previous player
Slot cannot be interacted with correctly
This happens more frequently if:
players have joined/left multiple times
he clan leader leaves and the party is reconstructed
Expected behavior
When a party member leaves, the correct party slot should be removed
Remaining players should retain valid nicknames and stats
Party state should remain consistent after clan room teardown
Current Behavior
The wrong party slot is removed client-side
Remaining slot contains corrupted or stale data
Party lobby becomes partially desynchronized
Additional context
This issue originates in handlePartyRoomLeave within ClanRoomLeaveHandler.h.
The server sends a party member removal packet using an index captured before the party list is modified.
The wrong party entry is cleared, Name buffers are not rewritten, Old stats remain attached to the wrong slot, “ghost members”, unreadable nicknames, mismatched clan stats in party lobbies.
Could potentionally fix infinite load bugs.
Description
When a player leaves a clan party lobby (especially while in a clan-vs-clan lobby or when the leader exits), the remaining party members sometimes see a corrupted player slot. The slot shows an invalid or symbolic name (e.g. Member, ()#(%¤)#%=), while some stats (notably clan contribution) still appear populated.
Reproduce
Nickname is invalid or empty
Stats belong to a previous player
Slot cannot be interacted with correctly
This happens more frequently if:
players have joined/left multiple times
he clan leader leaves and the party is reconstructed
Expected behavior
When a party member leaves, the correct party slot should be removed
Remaining players should retain valid nicknames and stats
Party state should remain consistent after clan room teardown
Current Behavior
The wrong party slot is removed client-side
Remaining slot contains corrupted or stale data
Party lobby becomes partially desynchronized
Additional context
This issue originates in handlePartyRoomLeave within ClanRoomLeaveHandler.h.
The server sends a party member removal packet using an index captured before the party list is modified.
The wrong party entry is cleared, Name buffers are not rewritten, Old stats remain attached to the wrong slot, “ghost members”, unreadable nicknames, mismatched clan stats in party lobbies.
Could potentionally fix infinite load bugs.