Describe the bug
I start a custom game (without spectator delay) on EUNE and add my friends. Then I trigger lobby synchronization, champ select, and end of game. Next, I enable InGame synchronization in the Observer tool. I start the game from the lobby in the client, and I’m set as a spectator. Champ select starts; the toolkit console correctly reports "Champselect - active," followed by "Champselect - game started." Then the WebAPI attempts to retrieve data about one of the players—even though the player is in the game, it returns an empty string. As a result, the InGame HUD crashes and fails to load.
To Reproduce
- Start the lobby, invite at least 1 summoner, switch yourself as a spectator.
- Sync Lobby, Champselect and InGame in Observer.
- Start the champ select, pick champs and let the game start.
- You will get the error.
Expected behavior
I would expect the game data to be retrieved correctly after collecting data on one of the players and the InGame UI loads.
Screenshots
Console log:
2026-03-28T17:12:02.511Z [info ] module-league-state: Flow: lobby - active
2026-03-28T17:12:09.670Z [info ] module-league-state: Flow: champselect - active
2026-03-28T17:12:24.127Z [info ] module-league-state: Flow: champselect - game started (spectator delay)
2026-03-28T17:12:24.188Z [info ] plugin-webapi: Fetching livegame data for summoner=
2026-03-28T17:12:24.294Z [error] plugin-webapi: Failed to get information for summoner=. Maybe this summoner does not exist? error=GenericError: Request failed with status code 404
2026-03-28T17:12:24.297Z [error] module-league-state: Loading livegame failed for summoner=
2026-03-28T17:12:25.512Z [info ] module-league-state: Flow: champselect - inactive
File: https://127.0.0.1:2999/liveclientdata/allgamedata
{
"activePlayer": {
"error": "Spectator mode doesn't currently support this feature"
},
"allPlayers": [
...
all information are correct about the game - I see correct Riot IDs, correct buys, correct runes etc.
File: https://127.0.0.1:2999/liveclientdata/activeplayername
says "Spectator"
System:
- OS: Windows 11 Pro
- Node: v20.10.0
- Prod Tool Version: v1.13.5
- Observer Tool Version: v6.14.4
- Browser: Edge
Describe the bug
I start a custom game (without spectator delay) on EUNE and add my friends. Then I trigger lobby synchronization, champ select, and end of game. Next, I enable InGame synchronization in the Observer tool. I start the game from the lobby in the client, and I’m set as a spectator. Champ select starts; the toolkit console correctly reports "Champselect - active," followed by "Champselect - game started." Then the WebAPI attempts to retrieve data about one of the players—even though the player is in the game, it returns an empty string. As a result, the InGame HUD crashes and fails to load.
To Reproduce
Expected behavior
I would expect the game data to be retrieved correctly after collecting data on one of the players and the InGame UI loads.
Screenshots
Console log:
2026-03-28T17:12:02.511Z [info ] module-league-state: Flow: lobby - active
2026-03-28T17:12:09.670Z [info ] module-league-state: Flow: champselect - active
2026-03-28T17:12:24.127Z [info ] module-league-state: Flow: champselect - game started (spectator delay)
2026-03-28T17:12:24.188Z [info ] plugin-webapi: Fetching livegame data for summoner=
2026-03-28T17:12:24.294Z [error] plugin-webapi: Failed to get information for summoner=. Maybe this summoner does not exist? error=GenericError: Request failed with status code 404
2026-03-28T17:12:24.297Z [error] module-league-state: Loading livegame failed for summoner=
2026-03-28T17:12:25.512Z [info ] module-league-state: Flow: champselect - inactive
File: https://127.0.0.1:2999/liveclientdata/allgamedata
{
"activePlayer": {
"error": "Spectator mode doesn't currently support this feature"
},
"allPlayers": [
...
all information are correct about the game - I see correct Riot IDs, correct buys, correct runes etc.
File: https://127.0.0.1:2999/liveclientdata/activeplayername
says "Spectator"
System: