mulander / evolutionchamber

Automatically exported from code.google.com/p/evolutionchamber
0 stars 0 forks source link

Set custom starting conditions/units #145

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
People seem to be having issues forcing particular initial build orders for 
longer term BO's - e.g. 12 hatch 13 pool, going into what EC finds - so a way 
to accomplish this is a better fashion could be the ability to set custom 
starting conditions.

For example instead of starting with 1 hatch, 1 OL, 6 drones, you could specify 
2 hatcheries, 12 drones, 1 spawning pool. 

To know the total build time you would of course need to know the time to get 
to your initial starting conditions, however that would be fairly trivial to 
find for most of these.

The time needed to get to your starting conditions from the 0:00 unit could 
also be found using some sort of automatic script, which could run a BO 
optimizer to achieve your starting conditions as well as your build from your 
starting conditions.

This could not only come in handy for testing builds when you have a specific 
opener, but also for testing builds for responding to scouting information.

Original issue reported on code.google.com by kel.bolden@gmail.com on 11 Nov 2010 at 4:32

GoogleCodeExporter commented 8 years ago

Original comment by azzur...@gmail.com on 11 Nov 2010 at 9:37