That upgrade section is really weird. I prefer something like.... --r_evo_carapace-- wait_build(1, Zerg Evolution Chamber) upgrade(1, Zerg Carapace, 70) wait(4500) wait_build(1, Zerg Lair) upgrade(2, Zerg Carapace, 70) wait(5000) upgrade(3, Zerg Carapace, 70) stop() --r_evo_melee-- wait_build(2, Zer...

So everything worked and then everything didn't work! I didn't know what to say this morning when I booted up the 3.1 exe and it wasn't at all like I had it been working. I guess somewhere along the line I "fixed" something and it caused the script to sort of fold in on itself and fail. An...

Whoa, it's 3.1 and it kicks 3.0 in the gut, imo! So I deleted half of the 3.0 scripts and added more junk inside of them instead. I think it's slightly better now, but I can't be sure. I'm still missing the PvT and all three of the mirror matchups. It's just my hardcore laziness when it comes to Pro...

How about just setting the default upgrade at +1/+1 or whatever?

I lied. This can help, but it seemed to cause big gamps in unit training. It's way better to just keep the multiruns going...


I would use this for other loops, however. Like a wraith harass or some detecting loop or whatever could use it well, just not here.

I will post a rep or two soon. I like your coding style and it is always giving new ideas that I can steal for my own one :P Stealing sharing is always great for improvement! I'll get the txts posted so nobody has to go through the trouble of exporting them to check them out... Is it really "M...

Whoa, new version bump!

Here's something useful: If you're running a Zerg script with a bunch of multiruns with training commands in them, as is the norm right now, adding kill_thread() and killable() to your script will help out with transitions to higher tier units. For example: --loopA-- send_suicide(0) multirun(t_lings...

[quote name='Scourge Splitter' post='7382' date='Aug 18 2009, 09:03 AM']I've used it and it works pretty fine, but then I just don't care too much about the desync... :P However, if you want them to expand when they attack, then you can insert wait_train commands, to keep the expansion close to the ...

--dronebuild-- build(1, Zerg Drone, 40) wait(50) goto(dronebuild) That will train 1 Zerg Drone, overall. Given that it looks like you've already got 4 Drones already, that loop doesn't really do anything. You could do something like: --dronebuild-- build(1, Zerg Drone, 40) wait_buildstart(1, Zerg D...