jc4p / lol-mechanics-tracker

helping myself be less bad at video games

6 stars 0 forks source link

0.1 Milestone #1

Open jc4p opened 8 years ago

jc4p commented 8 years ago

Version 0.1

Goal: Functioning prototypes of all vital components, just on my computer. If there's anything I'm planning to do which might not work as planned, or any hidden obstacles I haven't thought of yet, now's the time to go exploring.

[ ] live CS tracking, without noticeable GPU/CPU hit
[ ] Riot API integration to record champ, lane, etc
[ ] Save to CSV
[ ] Investigate if a centralized database would be necessary/helpful

jc4p commented 8 years ago

What about ward tracking? If better picture-in-picture detection comes as part of future plans for #2 pre 0.1 release, ward tracking (and where you/they are placing the wards) would be an easy add i think.

jc4p commented 8 years ago

I think the earlier-on we add a error reporting service the better it'll be, too. There's some code already to save frames OCR couldn't process, adding this logic to a helper class would mean it'd be done more as the code base evolves. Hell, it'd be usable for generating the look-up archives ^ talks about too.

ian-campbell commented 7 years ago

What are the dependencies for this program?

jc4p commented 7 years ago

@ian-campbell it's a bit up in the air (this is both the product I was trying to build and the library I built to use for it combined in one codebase rn). it only runs in side of Visual Studio, and I believe you need to also install the Windows SDK