Describe the bug
Lobby events in League of Legends don't show the eventType: PlayerQuitGameEvent anymore. When a player leaves the lobby, it shows GameDissolvedEvent without summonerId, even when he is not the last one leaving the lobby.
Issue Description
If a player leaves the lobby, and he wasn't the last one, we can't know which player left before the game start to forfeit him.
This was working correctly a year ago, maybe before the implementation of encrypted summonerIds.
Also, the documentation of the Tournament API shows that a PlayerGameQuitEvent event should exist.
Expected Result
It should generate an event in the lobby events list containing:
But this issue asks for this event to be added when the client crashes or disconnects. My bug report states that even when the user leaves intentionally, it doesn't show the event.
Describe the bug
Lobby events in League of Legends don't show the eventType: PlayerQuitGameEvent anymore. When a player leaves the lobby, it shows GameDissolvedEvent without summonerId, even when he is not the last one leaving the lobby.
Issue Description
If a player leaves the lobby, and he wasn't the last one, we can't know which player left before the game start to forfeit him.
This was working correctly a year ago, maybe before the implementation of encrypted summonerIds.
Also, the documentation of the Tournament API shows that a PlayerGameQuitEvent event should exist.
Expected Result
It should generate an event in the lobby events list containing:
Actual Result
It doesn't generate any PlayerQuitGameEvent event.
Lobby events output example in a 2vs2, where all players left the lobby by clicking on the cross (x) icon at the bottom of the client:![lobby-events](https://user-images.githubusercontent.com/3618244/70532942-524be900-1b58-11ea-9272-48bf98189d34.png)
Developer Impact
Steps to reproduce
Related issue
I've found this issue related to this bug: https://github.com/RiotGames/developer-relations/issues/114
But this issue asks for this event to be added when the client crashes or disconnects. My bug report states that even when the user leaves intentionally, it doesn't show the event.