🚀 go-pugleaf

Steve Kaye <nospam giddy-kippers.co.uk> wrote:

> John Doe <jdoe@usenetlove.invalid> wrote: 
>>Steve Kaye <nospam giddy-kippers.co.uk> wrote: 
>>
>>> You can even group different unit types together and use tab
>>> to cycle between them to get to their actions. 
>>
>>That can be used programmatically... Combine barracks with
>>factories. To make siege tanks. 
>>
>>  "siege[<n>]":#produce siege tanks
>>    Key("3/1")+#barracks and factories
>>    (
>>      Key("s/1")
>>    )
>>    *Repeat(extra="n")+
>>    Key("tab/1")+
>>    (
>>      Key("s/1")
>>    )
>>    *Repeat(extra="n")+
>>    PlaySound(r"C:\Program Files\VoiceWorks\boop.wav"),

> It looks like saying "siege four" will press 3 once then S four
> times followed by tab once and S four times. 

That is correct. 
The "/1" just suffixes a very short pause.

> You need to press 3 once, then tab once, then the two key 
> presses required to create a siege tank* four times.  

That is true and it would be less cumbersome if the barracks is 
always listed as the second subgroup, after the factory. If not, 
the listed method works. 

My main concern at the moment is finding an efficient way to
string opening commands together. Given the retarded interface
that requires resources before anything is put in the queue
(regardless of when that object is built or produced), very
tedious timing is necessary. So I'm trying to jump together a
method for recording opening scripts that includes the timing. I
would like to start with a script that beats the AI on Steppes of
War (on various AI difficulty levels). 

Going to be a while before I can handle multiplayer, if ever. 
-- 






> 
> * Don't know the command to make a siege tank as I play protoss and
> use the grid key system - is it S, followed by S?
> 
> steve.kaye
>