-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: add Match Start timestamp to telemetry #213
Comments
Hey @BrianGlory interesting.. What's the use case specifically for this one? |
Well, knowing when the match actually starts would be helpful in correlating event time in the telemetry with that shown on the match timer in-game (replays, recordings, broadcasts). Right now, they do not agree. |
The format of this event should be in line with #167 and PlayerFirstSpawn. What about: {
"time": "2017-04-22T15:16:28+0000",
"type": "PlayerPreparing",
"payload": {
"Team": "Right",
"Actor": "*Ozo*"
}
}, |
@genexp UseCase: More accurate timestamps for events. Currently when calculating time diffs b/w events (PlayerFirstSpawn and BuyItem) there is a problem since some players load times are late by 1-10 seconds. If we have this we could use MatchStartTime for diffs instead of PlayerFirstSpawn |
"Match Start Time" Ii assume you mean when the timer in game starts. so the minion spawns should be 35s from the "start time". if that's what you mean, it all makes sense |
That is exactly what I mean @kvahuja :) |
there is currently no way to tell from the telemetry what server time the match actually starts. Although
PlayerFirstSpawn
in the telemetry now, theses times vary depending on the user's device load times and other factors. If there was a timestamp in telemetry for the exact time that a match kicks off+players are able to buy/move off the platform, events from telemetry could be much more accurate in apps.The text was updated successfully, but these errors were encountered: