Taranok wrote:Yeah turrets can be a huge waste with the way that the AI places them.

So you're attempting a big tankless 2 base attack right after ZBwaiP attacks? I really don't know how great that will be. It'll take quite a while for the AI to rebuild units after the attack, and by then ZBwaiP will be on 3 bases for at least 2 minutes. But if you were able to attack without the presence of carriers you could be getting something going.

It wasn't tankless. It was boring. It sucks to make all sorts of fancy upgrade stuff and then some generic 8 fact junk wins.

Taranok, can you make a sample AI script such that Protoss will try a contain in front of the enemy's base, i.e. gather goons, zealots and observers in a safe range from the enemy siege tanks but still killing anything that will try to escape out by land (scvs, vultures, etc)

will try to get any updates/coding worked on this weekend. btw I'm not sure how terrific a contain script will work (I think I read something about attack_prepare will attack without waiting for the attack_do command). Will try though.

Well, I don't mean it to be an otherwise powerful bot. I (and I believe other bot developers) just need an opponent that makes a good contain (gather army in a safe distance in front of the enemy siege tank defense) because passive bots like mine tend to suicide lots of units in such situations. It'll be an extremely useful training partner.Some notes about it to ease the work:1) doesn't need to ever attack, just to continue gathering in a safe distance in front of the enemy natural. Defending that position so to say2) the gathering position should be such that the contained player can't send workers out to build an expansion or sneak out any vultures. I know this is hard on let's say FS, but It should be somehow doable on Python maybe?3) Army composition doesn't need to be too fancy. Goons with range mostly, maybe later - some HTs and reavers, carriers...?4) Could be a UMS map as I know this would be easier.

@ attacking w/o waiting for a commandFrom prior observations, it was discovered that the internal AI engine will send it's army on the offensive without ever instructing it to do anything (i.e. no attack commands in script at all). Ashara I believe confirmed this in his testing as well. Not sure what triggers the AI to decide to attack, but it doesn't appear to just build a passive army. Eventually it seems it will attack whether you instruct it to or not.

Somewhere there is a post/script called EasyZ. Basically I tried to put together a script that wouldn't attack my 10yr old nephew, but rather just build a huge defensive army/base. Eventually tho (usually around 15 minute mark iirc) it would go on the war path. Maybe there was something we needed to leave out that prevented the script from behaving as intended.

The hardcoded build-in script attacks (the ones that are not executed specifically from the script) are one of the many functions that can be disabled by calling start_campaign. After that the AI will just obediently do whatever it is told. Have in mind that if an AI is run in the UMS game move start_campaign is called anyway (or at least the functions it disables do not work in UMS).