Attached files are Terran custom script, Protoss custom script, scenario maps.
Starcraft Artificial Intelligence
::Introduction::
・Most starcraft players who start exploring the possibilities of writing their own AI scripts are doing so because they think the current AI is too predictable.
・Playing the original starcraft/broodwar AI can be very challenging at times, especially against multiple opponents, but after playing the AI numerous times, perhaps you realised it would be more fun if the AI used a wider variety of build up and attack strategies.
Imagine a Protoss AI rushing into a Terran base with 50 Dark Templars or a Terran AI attacking a Zerg expansion with a group of 24 cloaked Wraiths and 6 Siege Tanks all at once.
Though programming experience is not necessary to be able to construct starcraft AI scripts, it does help. On the other hand, if you haven't got any programming experience yet, this is the perfect opportunity to learn the basics.
How to test the newly created script
1. Compile the script file (i.e. Protoss Expansion Custom Level.asc3 or Terran Expansion Custom Level.asc3) using SCAIEdit III. Make sure there are no errors left.
2. Close the script file and open the "aiscript.bin". You can use WinMPQ to extract the latest aiscript.bin from the latest "Patch_rt.mpq" file (note: if the extracted file is all caps, then rename it to "aiscript.bin" with no caps, otherwise SCAIEdit might have trouble reading it). There is also a "aiscript.bin" included with SCAIEdit III.
3. Look for the "Protoss Expansion Custom Level" or "Terran Expansion Custom Level.asc3". Remove it from the "aiscript.bin" file. Then import your own "Protoss Expansion Custom Level.asc3" or "Terran Expansion Custom Level.asc3" file.
4. Compile the "aiscript.bin" file. The message "Script compilation done!" should appear.
5. Close the "aiscript.bin" file. Then make a backup of the "Patch_rt.mpq" file in your Starcraft directory. Now use WinMPQ to open the file. Then look for the file "scripts\aiscript.bin" or "scripts\AISCRIPT.BIN". Remove it and add your own aiscript.bin (also use "scripts\" as the path). Make sure that while doing this you have (1) a backup of the original "Patch_rt.mpq", (2) no other program open that also makes use of the "Patch_rt.mpq" file (e.g. Starcraft/Broodwar).
6. Close WinMPQ. Start Broodwar and create a game against a Protoss AI.
AIScript commands
::Header commands::
farms_notiming
Build necessary farms only when it hits the maximum supply available.
farms_timing
Build necessary farms with a correct timing, so nothing is paused by a maximum supply limit hit.
start_areatown
Starts the AI Script for area town management. Should only be used in campaign scripts, as it uses the trigger location as its bounds (or area).
start_campaign
Starts the AI Script for Campaign.
Note: This command may have many subtle (but significant in number) changes to AI behaviour which may be desirable in some cases, but not in others.
start_town
Starts the AI Script for town management.
transports_off
Computer will not manage/build transports on its own.
check_transports
Informs computer to build transports on its own. If start_campaign was called, then 2 transports will be built, otherwise 5 will be built.
The first transport is built at priority 80 and subsequent transports are built at priority 50.
Protoss also trains up to 2 observers at priority 80. Used with header transports_off.
- General build order commands: The commands in this category manage the construction of buildings, training of workers, and researching tech and upgrades.
Oddly enough, StarCraft uses the same AI manager for buildings and workers, while normal melee units (AKA military) are controlled by the military manager.
| build [count] [building] [priority] | Adds "Construct [count] number of [building] at [priority]" to the AI's town queue. |
| player_need [count] [building] | Adds "Construct [count] number of [building] at priority 80" to the AI's town queue. |
| wait_build [byte] [building] | Pause script execution until the AI has [byte] of [building] in the current town. Units/buildings in production are not counted. |
| wait_buildstart [byte] [building] | Pause script execution until the AI has [byte] of [building] in the current town, counting units/buildings in production. |
| get_oldpeons [count] | Retrieves [count] number of workers from other towns to the current town. |
| tech [technology] [priority] | Adds "Research [technology] at [priority]" to the AI's town queue. |
| upgrade [byte] [upgrade] [priority] | Adds "Research [upgrade] until [byte] level is reached, at [priority]" to the AI's town queue. |
| train [byte] [military] | Tells the AI to train [military] until it has at least [byte] of them, including those in production. |
