Reynald Pader

Still marked as WIP because as of the moment, conditions are very verbose. That is, we have to specify a lot of conditions to make sure that a build order...

@Dentosal , I remember having this problem way back when I was still actively contributing. It's because the API can't register a currently warping in unit as an unavailable cell....

I'm currently testing a build order implementation that can be used as follows: ``` build_order = [ (supply_is(12), train(UnitTypeId.SCV, on_building=UnitTypeId.COMMANDCENTER)), (minerals_at_least(100), build(UnitTypeId.SUPPLYDEPOT)), (supply_is(13), train(UnitTypeId.SCV, on_building=UnitTypeId.COMMANDCENTER)), (supply_is(14), train(UnitTypeId.SCV, on_building=UnitTypeId.COMMANDCENTER)), (minerals_at_least(150), build(UnitTypeId.BARRACKS)),...

Here's a sample usage: https://github.com/reypader/python-sc2/blob/build-order-support/examples/terran_build_order.py and here's the source https://github.com/reypader/python-sc2/blob/build-order-support/sc2/build_order.py It's currently WIP but as of writing, it's working for simple build orders based on resource and supply counts.

I though about referencing previous build orders, actually. Though, the way it is now, it would probably be through counting how many buildings are complete rather than actually referring to...