developer-relations
developer-relations copied to clipboard
[BUG] Atakhan type is node provided in match timeline
Problem Description
In match timeline when atakhan is killed we don't get the info of the mob type. For dragon we know wich type or dragon is killed or the soul given, here we don't get any of thoses infos
Expected Result
Get a monsterSubType or something similar in match timeline when Atakhan is killed like this
Actual Result
No information about Atakhan type
Developer Impact
Can't make statistics and give detailed info about the player's game info
Player Impact
Can't get his information, nothing impact the game itself
Preconditions
A game where Atakhan is killed
Repro Steps
- Fetch the endpoint
/lol/match/v5/matches/{matchId}/timelinewith a matchid corresponding to a match where Atakhan is killed
Issue Comments
If you're also experiencing this issue please add any additional context that is useful, the developer impact to yourself, and the player impact to your users. As an example, if spectator-v4 isn't working it might affect a scouting site, but it could also affect a mobile app or site to share replays. Give the context on how this issue affects your project.
I guess they did not forget about not giving the atakhan type. If that info was added onto the game, analysts could reverse engineer the algorithm use to determine the spawn, this would lead on players having third party apps having a huge advantage from players not using them. Drakes are just randomly spawned so it does not matter.
I would love, of course, to know the type of Atakhan that was spawned to have a better application myself, but thinking about the topic, that is the conclusion i made up myself. Hope i am wrong and they add it.
If that info was added onto the game, analysts could reverse engineer the algorithm use to determine the spawn
I could also manually mark matches with top/bot Atakhan and analyze them afterwards, that's not really stopping me except that it takes a bit longer
If that info was added onto the game, analysts could reverse engineer the algorithm use to determine the spawn
I could also manually mark matches with top/bot Atakhan and analyze them afterwards, that's not really stopping me except that it takes a bit longer
It's different, you can find atakhan position, but top/bot does not determine atakhan type