-
Notifications
You must be signed in to change notification settings - Fork 0
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
What's left? #2
Comments
This is an incredibly late response, but... I need to take a look at this again. My general recollection is that most of the "basics" are done... the primary events, etc. Beyond that, there needs to be support to parse the lobby archive so that we can extract BattleTags. Beyond that, most of the work would be deriving statistics. This is doing the work like parsing KDAs, damage done, doing something with the events we have. I kind of waffled back and forth on whether we should care about this. Technically a caller could parse the JSON output and do it themselves if we gave them all of the events... but the amount of data is pretty large (although that's largely in part due to it being JSON) |
Do you plan on continuing to work on this? If so I'd be happy to
collaborate!
Arran
…On Wed, 2 May 2018 at 17:47 Toby Lawrence ***@***.***> wrote:
This is an incredibly late response, but... I need to take a look at this
again.
My general recollection was that most of the "basics" are done... the
primary events, etc. Beyond that, there needs to be support to parse the
lobby archive so that we can extract BattleTags.
Beyond that, most of the work would be deriving statistics. This is doing
the work like parsing KDAs, damage done, doing something with the events we
have. I kind of waffled back and forth on whether we should care about
this. Technically a caller could parse the JSON output and do it themselves
if we gave them all of the events... but the amount of data is pretty large
(although that's largely in part due to it being JSON)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AITM9lejpj7egeLm68f41Y9qUyJz-BFWks5tueMZgaJpZM4SEUA4>
.
|
Hey!
I was just about to start writing a parser in Rust then stumbled across yours!
Could you give me a general update on the state of the project and what's left to do to get it to feature parity with other parsers?
Arran
The text was updated successfully, but these errors were encountered: