You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have a tab that shows information about the deaths in the game by each player. It could be selectable by hero (as the "laning" tab currently has) and would display information about each death like
game time (for quick searching in a replay)
damage contributing to that death
gold rewarded to the enemy heroes for the kill
gold lost by hero
respawn time for dead hero
location on the map of the death
It would be useful for the community to have something that allows them to visualize how different deaths contribute to momentum swings and the impact of different kills, as well as make it easier for players to analyze the cause of their death.
Some of these might have to be added on the core end, I haven't look too far into it.
I'd imagine the tab would have a visual appearance similar to the "laning" and "log" tabs. Maybe something like the log except for deaths on the left that are selectable and show the stats/map on the right.
The text was updated successfully, but these errors were encountered:
It would be nice to have a tab that shows information about the deaths in the game by each player. It could be selectable by hero (as the "laning" tab currently has) and would display information about each death like
It would be useful for the community to have something that allows them to visualize how different deaths contribute to momentum swings and the impact of different kills, as well as make it easier for players to analyze the cause of their death.
Some of these might have to be added on the core end, I haven't look too far into it.
I'd imagine the tab would have a visual appearance similar to the "laning" and "log" tabs. Maybe something like the log except for deaths on the left that are selectable and show the stats/map on the right.
The text was updated successfully, but these errors were encountered: