Hm. Would be complicated. You'd need to edit some code in ASM.

Also, you're fat.
What are we doing this summer?

Hmm, should I use JUMP instead of CALL in the order replacements?

Do you mean the switch case table that lists in order each AIScript command? I didn't think of changing that, but it could be done making things easier, just copying the entire block of code used to make the command work.

That's exactly what should be used in all scripts.
You make more peons than you would normally and then recall a few to expansion.

The max would limit it.

Yeah, I have no idea what type of input they are. That's from scAIEdit III's opcode.dat.

BWScript is an extension of AIScript. If AIScript exceeds its maximum size, you can use BWScript to store your scripts, and SC will read it, however Staredit will not.

Scout_with is unused.

Fixed it up a bit and gave Staredit commands more meaning.

Yeah, I looked at the assembly in ollydbg.

I took some time to get the values for "rush". Sunkens/spores count as 2 units 0 = Barracks OR Spawning Pool OR Gateway (includes incomplete) 1 = At Least 17 Marines + Bunkers, OR at least 16 Sunken Colonies + Hydralisks, OR at least 7 Zealots 2 = At least 25 Marines + Bunkers, OR At least...

I thought the value in "creep" determines the distance towers are placed from each other. I think "prep_down" has to do with Siege Tanks, as both Tank Mode and Siege Mode are compared in memory. "if_towns" doesn't exist. "fatal_error" causes a fatal AI script ...