-
Notifications
You must be signed in to change notification settings - Fork 0
/
protoss_builds.yml
57 lines (46 loc) · 1.54 KB
/
protoss_builds.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
# This file is optional and here as an example of how to activate the build runner
# FEEL FREE TO DELETE!!
# If playing as a different race, make a file similar to this but change filename:
# `zerg_builds.yml` or `terran_builds.yml`
# Save the game opening and result to disk?
# Setting to `True` allows Ares to select a new opening after defeat
UseData: True
# How should we choose a build? Cycle is the only option for now
BuildSelection: Cycle
# For each Race / Opponent ID choose a build selection
BuildChoices:
# test_123 is active if Debug: True (set via a `config.yml` file)
test_123:
BotName: Test
Cycle:
- DummyOpening
Protoss:
BotName: ProtossRace
Cycle:
- DummyOpening
Random:
BotName: RandomRace
Cycle:
- DummyOpening
Terran:
BotName: TerranRace
Cycle:
- DummyOpening
Zerg:
BotName: ZergRace
Cycle:
- DummyOpening
# Can also use specific opponent ids (overrides race options above)
a_bot_opponent_id_from_aiarena:
BotName: QueenBot
Cycle:
- DummyOpening
Builds:
DummyOpening:
# Build constant workers till x supply
ConstantWorkerProductionTill: 0
OpeningBuildOrder:
# Example: ['12 worker', '13 worker', '14 supply', '14 worker', '15 chrono @ nexus',
# '15 worker', '16 gateway']
# See docs: https://aressc2.github.io/ares-sc2/tutorials.html#build-runner-system
[]