spawningtool
spawningtool copied to clipboard
StoicLoofah
Tools for analyzing StarCraft 2 Replays
#56 identified many missing buildings and unit types in `lotv_constants.py` that ideally should be added for consistency. Most are properly ignored, but many buildings should appear in the data
I was trying to practice my build order, so I went back to 0:00 in a replay and resumed only to find that the spawning tool timer is significantly faster...
Thank you so much for your support of the community! I noticed that instead of Chronoboosts, spawningtool lists `NexusMassRecall` in `player.abilities`. This problem seems also to affect http://sc2replaystats.com/
The targetunitcommandevent actions didn't have the name or target properly marked, so it wasn't moving
I get this error when I try to load a replay using the CLI. ```Traceback (most recent call last): File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib/python3.6/runpy.py", line...
With co-op support, we have a more detailed structure for `BUILD_DATA` entries https://github.com/StoicLoofah/spawningtool/blob/9a963f6f0be5a299658d05e94d1edec7c0c15f9e/spawningtool/coop_constants.py#L209-L216 Additionally, we also added building entries, which previously weren't necessary because we didn't need to adjust build...
http://spawningtool.com/16875/ So both landing Orbital Commands and morphing them count as UnitTypeChangeEvents, which is unfortunate because we get extra entries for landing buildings. With the data given, I actually don't...
It's still kinda off for replays even after https://github.com/StoicLoofah/spawningtool/commit/7a8e480c488f637fc75c17608ebacb3f8ac15bbb http://wiki.teamliquid.net/starcraft2/Game_Speed
Pretty soon I'll be pulling through the entire sc2reader object. In the meantime, this is tied to a request for measuring some macro and economy metrics alongside the build order
https://github.com/GraylinKim/sc2reader/issues/181