You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+38-4Lines changed: 38 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,9 @@ TODO:
12
12
13
13
# Summary
14
14
15
-
By downloading and running this you are agreeing to the [StarCraft II AI and Machine Learning License](https://github.com/Blizzard/s2client-proto/blob/dca8b6831a84747c2cd6e0c33d6416e14838d886/DATA_LICENSE)
15
+
By downloading and running this you are agreeing to:
16
+
17
+
[StarCraft II AI and Machine Learning License](https://github.com/Blizzard/s2client-proto/blob/dca8b6831a84747c2cd6e0c33d6416e14838d886/DATA_LICENSE)
16
18
17
19
18
20
# Building Containers
@@ -23,32 +25,53 @@ By downloading and running this you are agreeing to the [StarCraft II AI and Mac
23
25
cd game && ./all.sh
24
26
~~~
25
27
28
+
This creates a new container named s2client-api.
29
+
30
+
The entrypoint will be the StarCraft II executable listening for API calls on port 12000.
31
+
32
+
You can run the game now as a container:
33
+
34
+
~~~
35
+
docker run -P -d s2client-game
36
+
~~~
37
+
38
+
TODO: There appears to be an issue connecting on the exposed port
26
39
27
40
3. Building the API build container
28
41
29
42
~~~
30
43
cd build && ./all.sh
31
44
~~~
32
45
46
+
This builds the API and puts binary artifacts into the build-mount volume.
47
+
33
48
4. Test the containers
34
49
35
50
~~~
36
-
TODO
51
+
cd game && ./run-tests.sh
37
52
~~~
38
53
54
+
TODO: This currently crashes
55
+
56
+
39
57
2. Installing replay packs and the Battle.net cache to run hem
40
58
41
59
~~~
42
-
TODO
43
60
~~~
44
61
62
+
TODO: Consider using volumes for this case as well, lots of data to move around.
63
+
45
64
### Running the API build
46
65
66
+
67
+
You can run the build yourself inside the s2client-api container:
68
+
47
69
~~~
48
70
docker run -it s2client-api
49
71
./api-build.sh
50
72
~~~
51
73
74
+
52
75
### Running the Game
53
76
54
77
~~~
@@ -59,5 +82,16 @@ If you want to use the replay container automation you should export
59
82
the container ID in an environment variable.
60
83
61
84
~~~
62
-
export GAME_CONTAINER=docker run -d s2client-game
85
+
export GAME_CONTAINER=`docker run -P -d s2client-game`
63
86
~~~
87
+
88
+
### Developing using the API
89
+
90
+
~~~
91
+
cd dev && ./all.sh
92
+
docker run -it s2client-dev
93
+
~~~
94
+
95
+
The developer image s2client-dev is derived from s2client-game. You will need
96
+
to first build the s2client-game image. Running the developer image you can
97
+
clone the git repo, update your git config and test against the packaged client.
0 commit comments