generated from AresSC2/ares-sc2-bot-template
-
Notifications
You must be signed in to change notification settings - Fork 0
/
zerg_builds.yml
62 lines (54 loc) · 1.55 KB
/
zerg_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
56
57
58
59
60
61
# This file is optional and here as an example of how to activate the build runner
# FEEL FREE TO DELETE!!
# 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:
- BurrowRoachRush
Protoss:
BotName: ProtossRace
Cycle:
- BurrowRoachRush
Random:
BotName: RandomRace
Cycle:
- BurrowRoachRush
Terran:
BotName: TerranRace
Cycle:
- BurrowRoachRush
Zerg:
BotName: ZergRace
Cycle:
- BurrowRoachRush
# Can also use specific opponent ids (overrides race options above)
a_bot_opponent_id_from_aiarena:
BotName: QueenBot
Cycle:
- DummyOpening
Builds:
BurrowRoachRush:
# Build constant workers till x supply
# Turning this off here for a bit more precision in build
ConstantWorkerProductionTill: 0
OpeningBuildOrder:
- 12 drone
- 13 drone
- 14 spawningpool
- 13 gas
- 12 drone
- 13 drone
- 14 overlord
- 14 drone
- 15 roachwarren
- 14 queen
- 14 drone
- 15 drone
- 15 overlord