[ Question ] Error in fetch-livegame step

[eggtart-365]

Is your question related to a problem? Please describe.
I'm trying to use module-legue-in-game, but an error occurs while making a request to Riot's ACCOUNT-V1 API at the fetch-livegame stage of the plugin-webapi part. As a result of modifying the source code and taking a log, summonerName is included in the e-data used, but tagLine and gameName do not come over.

As a result, the undefined value will be used on request and an HTTP 400 error will be returned as a result.

2025-01-21T14:46:09.381Z [info ] plugin-webapi: Fetching livegame data for summoner=DOS
2025-01-21T14:46:09.982Z [error] plugin-webapi: Failed to get information for summoner=DOS. Maybe this summoner does not exist? error=GenericError: Request failed with status code 400
2025-01-21T14:46:09.997Z [error] module-league-state: Loading livegame failed for summoner=DOS

Describe alternatives you've considered
I'm not sure about the structure of the program, but I'm curious about whether the gameName and tagLine values are properly exceeded in the observer-tool stage and how the module is handling them.

Additional context
prod-toolkit version : 1.11.2
region : KR
regionGroup : ASIA
League of Legends client version : 25.S1.2

---

fetch-livegame Data

{
  "meta":{
    "channelType":"REQUEST",
    "namespace":"plugin-webapi",
    "type":"fetch-livegame",
    "version":1,
    "sender":{
      "name":"module-league-state",
      "version":"4.13.1",
      "mode":"PLUGIN",
      "path":"C:\\Users\\mamai\\Desktop\\prod-toolkit\\modules\\module-league-state"
    },
    "reply":"fetch-livegame-cbxi3uagkm6hsproo"
  },
  "summonerName":"DOS",
  "retries":0
}

[sdomi4]

This is just something that hasn't been updated for the migration from summoner names to Riot IDs; consider it a bug. We don't support most of the toolkit very actively, so absolutely no guarantees if/when it will be fixed.