Two things the feed can't give us yet:
Team chat and ping events
A new event fired when a teammate sends a team chat message or a quick-communication ping (e.g. "Need healing!", "Ultimate ready", "Enemy spotted").
Suggested data:
{"name":"team_comm","data":"{"uid":"1380486120","name":"yuragi","character_id":"1038","type":"ping","ping_id":"need_healing","text":"Need healing!"}"}
type: "ping" or "chat"
ping_id: a stable id for quick-communication lines, so apps don't have to parse localized text
text: the message as shown in game
Team channel only; no enemy or all-chat messages are needed.
Teammates' health
Add health and max_health to roster_xx for teammates only, the same way ult_charge is teammates-only today:
{"uid":"1380486120", ..., "is_teammate":true, "health":175, "max_health":250}
Why it fits Overwolf's and NetEase's compliance rules:
Teammates only. Nothing about enemies, so no hidden information and no prediction of enemy ultimates.
Everything requested is already visible to the player in game (ally health bars, team chat and pings). It only lets apps show it in a clearer place, e.g. a support player seeing "Need healing" next to that teammate's health on the team card.
Use cases:
Support players: a compact team card with health, ult charge and the latest ping per teammate.
Accessibility: pings repeated in a larger, high-contrast card for players who miss the small chat text in team fights.
Post-match: how often a teammate asked for healing, to help players review their games.
Happy to test a beta build of the events. Thanks!