I recently pulled down and made a dev install of sc2reader, and I'm mostly interested in it to automate personal replay analysis with custom metrics.
I found the SupplyTracker plugin and have already made a couple small changes in my dev install to update from HoTS to LoTV supply values. As you probably know, this plugin is just printing out supply events, which is not that useful for post analysis, so I intend to have it create some sort of supply data structure, and perhaps implement a way to do time polling from a time sorted event list (e.g. what is worker, army, available supply at a time t ). It looks to me like most of the existing plugins (e.g. the APM tracker) are just adding to the data structure that is returned from sc2_reader.load_replay() method, so I thought I would try to follow that pattern.
Are y'all still actively maintaining this, and would you like these changes put into a PR? If so, do you have any other guidelines about structuring the data structures created by plugins? What about adding some data structures and guidelines for time polling as a feature in general, since this seems like a common, if not the most common, use case?
Happy to try to direct my changes so I can contribute back, but equally happy to just keep stuff in my own fork as well. I just thought I'd reach out and see what you all thought, as I explore the codebase.