LiveAPI changes to PlayerKilled and awardedTo
I reviewed the changes to the LiveAPI that released today in Season 20. The change to `PlayerKilled` to remove `awardedTo` causes issues in solutions I have deployed. The comment in the events.proto file is:
"Sent when a player is killed. Details are similar to PlayerDamaged event. The `awardedTo` field has been deprecated for simplicity. Listen for the `PlayerStatChanged` message to determine which player the kill was awarded to."
These changes to remove `awardedTo` create a disconnect between the events and now make me rely on the order of events in an environment where I may get them out of order or at the same time. For example, I may get the following events (reduced for readability):
This shows the ring killing two different players. Then we get `PlayerStatChanged` events for the players that were awarded the kills for the ring deaths. This is not enough information for me to know who Player1 killed.
In my solution that provides leaderboards with custom rules, I can no longer enforce my custom rules for giving points for killing specific legends/players. For example: I may have a rule defined that says you get 5 points for killing a Wraith, but if I don't know who killed the Wraith, that's a problem.
The `awardedTo` field could provide that information. I would like to have this functionality back. I think `awardedTo` on `PlayerKilled` is a great way to do that. Alternatively perhaps you could do some type of `linkedEntity` on the `PlayerStatChanged` to show how you were awarded that change but that seems more complicated.
