Howard Chung

currently for the analysis page we just base it off wards placed (>2) and less than 20 last hits at 10 minutes: https://github.com/odota/web/blob/5436c56f491b1d9b759147407f9a48eb7d022570/src/utility/index.jsx#L257 You can compute the same value statically...

It could be added for future matches, but currently isn't saved to the cassandra player_caches table so can't be returned for each player-match

I have not played ranked roles. Is it available in the post-match stats in client?

We calculate support-ness just by the last hit at 10 minutes count and ward placement, see https://github.com/odota/web/blob/master/src/actions/transformMatch.js#L151 and the isSupport function in utility.

The reason that it's in the client side code and not returned in the API/server is that we were aware that it would probably be somewhat inaccurate to guess using...

Yes, this is a long-standing issue with reading data from combat log. Overview gives data from Steam WebAPI. It matches game scoreboard. However most of the parsed data is from...

Ideas welcome, suggested on Reddit: m_lifeState property of CDOTA_Unit_Hero

The problem with this level of specificity is that it's prone to breaking if Valve changes numbers. I want something reliable and consistent.

Yeah I'd prefer not to implement partial fixed since it might cause even more confusion. On Jan 14, 2016 2:10 PM, "Py" [email protected] wrote: > For wraith king, one way...

We count gold loss through separate events. I suppose the event would not be present for aegis and reincarnations, but the problem remains that we're trying to correlate across events...