The game now supports running with docker AND running without docker. See below for the docker instructions.
To play the game without docker:
READ THE WHOLE SECTION FOR YOUR OS. If you don't follow instructions we can't help you.
Download the most recent version of this repository (see the green Download button above?).
Unfortunately, since we don't have docker we'll have to install some other things.
Note that if you are copying over an old player (that used to run in docker), you HAVE to copy the new run.sh and run.bat files for your language from the correct examplefuncsplayer folder. Your code will continue to work inside docker, but will not work outside of it without the new run.sh and run.bat files.
First, install Python 3.6 64 bit. If you have a python 3 install but it isn't 64 bit this won't work.
There's a download link here: https://www.python.org/ftp/python/3.6.4/python-3.6.4-amd64.exe
MAKE SURE you click "Add Python 3.6 to my Path".
Now, start a command prompt (search cmd in the start menu) and run:
py -3 -c "import sys; print(sys.version)"If you get output that looks something like:
3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:54:40) [MSC v.1900 64 bit (AMD64)]
See the 64 bit part? That's important.
Next, copy over the new run.sh and run.bat files from the examplefuncsplayer folders into your player folders. (If your bot is python, copy over the python run.sh and run.bat scripts, and so on.)
Now, go to wherever you downloaded this repo and run the run_nodocker.bat script. It should install a few other things and then quickly start up! Go to the link in the terminal and run a game or two. NOTE: Currently, ONLY PYTHON works outside docker on windows. This will be fixed as soon as we figure out how to get the other languages linking correctly. Just stick with Python for now :)
if you get:
ModuleNotFoundError: No module named cffi_backend
Or:
%1 is not a valid Win32 program
You need to uninstall python 3 32-bit, install 64 bit, and run:
py -3 -m pip uninstall cffi eel greenlet tqdm werkzeug psutil pycparser gevent greenlet bottle bottle-websocket
Before re-running run_nodocker.bat.
If you get Access is denied: ...\\battlecode_manager\\working_dir\\battlecode\\... while running a new game, it means that some of your old players are running. Go to task manager and kill any runaway python processes.
Install Python 3 and homebrew: http://docs.python-guide.org/en/latest/starting/install3/osx/
Once you have python 3 installed, open a terminal (the app is at /Applications/Utilities/Terminal.app).
In the terminal, run the following command:
python3 -c "import sys; print(sys.version)"If you get output that looks something like:
3.6.4 (default, Dec 19 2017, 15:24:51)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2)]
Then you've got working python.
Next, run brew install libffi.
Next, copy over the new run.sh and run.bat files from the examplefuncsplayer folders into your player folders. (If your bot is python, copy over the python run.sh and run.bat scripts, and so on.)
Finally, cd to the directory you downloaded this repository to.
Run: ./run_nodocker.sh
This will download the rest of the python dependencies (just a couple of python libraries) and run the manager. You can now run bots in the same way you did before!
If you're running java bots, you'll need the jdk 8 on your PATH, and if you're running c bots, you'll need gcc.
You need python 3.6, libffi-dev, and linux-headers. Install them via your package manager. Then run run_nodocker.sh.
If you're running java bots, you'll need the jdk 8 on your PATH, and if you're running c bots, you'll need gcc.
You can also run games in Docker, a cross-platform container system. If you followed the previous instructions you DON'T NEED TO DO THIS.
To start, install docker, and make sure it's started.
Install docker for mac: https://www.docker.com/docker-mac
Clone the repo, or click https://github.com/battlecode/bc18-scaffold/archive/master.zip to download
Install docker for your system.
Clone the repo, or click and run sudo sh run.sh in the directory. Wait a while to download our code, then finally it will say:
To play games open http://localhost:6147/run.html in your browser
Follow its instructions, and start runnin them games! (warning, socket.bc18map may be buggy rn)
Windows 10 Professional or Enterprise: install https://www.docker.com/docker-windows
double click run.cmd
wait a while
When you get the message: To play games open http://localhost:6147/run.html in your browser you're good to go!
First, install Docker Toolbox: https://docs.docker.com/toolbox/toolbox_install_windows/
Download the executable and follow the wizard to install it.
Search for 'Docker Quickstart Terminal' and open it. Do not open it twice, because multiple running copies do not work properly.
Wait a few minutes. You will see a picture of a whale when it finishes. Later, you will enter commands in this docker quickstart terminal, so don't close it.
Download the battlecode 2018 scaffold from https://github.com/battlecode/bc18-scaffold. You can use the green button to download the files and then manually unzip them, or you can clone the repository using Github if you're familiar with that.
Check that you have at least 2 GB of space available on your hard drive. You will need this much space for the docker install.
In the quickstart terminal, navigate to the location of the unzipped files that you downloaded. You can navigate using 'cd' and 'ls'. For more information on navigating a file system with a unix terminal, see https://www.digitalocean.com/community/tutorials/basic-linux-navigation-and-file-management.
Once you have navigated to where your bc18-scaffold repository is located, type "bash run.sh" (then press enter) to start the battlecode server. The first time you run this command, it will take a while downloading the docker installation.
The Battlecode server will initialize and you will see the prompt, To play games open http://localhost:6147/run.html in your browser on Mac/Linux/WindowsPro, or http://192.168.99.100:6147/run.html on Windows10Home. . Do not close the docker quickstart window. Go to the second url http://192.168.99.100:6147/run.html and you should see a website. You run Battlecode matches using this website graphical user interface (GUI). The docker quickstart window will not accept commands at this point; it is listening to the GUI.
Run a test match using the GUI. Select "Run Game" at the lower right. Live player logs should appear on screen. When the match ends, the live logs will disappear and a message appears on the website indicating which player won. Also, a match file is produced. The default name of the match file is "replay.bc18". This file appears in the bc18-scaffold directory that has the run.sh file.
To see a visual representation of the match, you can load the match file using the viewer. First, let's download the viewer.
Visit http://battlecode.org/#/materials/releases and select the "Windows" link under the bullet point, "Download the Viewer".
Unzip the file you downloaded.
Before running the viewer, reduce your system volume to a reasonable level. The viewer plays music.
Double-click clientWindows.exe. Select your choice of resolution. Windowed mode is convenient for running next to your code. Once you have configured the player, click "Play!"
Now load the match file by selecting the icon with three bars at the top of the screen. Navigate to the bc18-scaffold directory, where the replay.bc18 file is stored. Then click the file, and at the bottom of the window click "Select". Now the replay file is loaded, so start the replay running using the triangle button in the top left. You can zoom out with the mouse scroll wheel, and pan left/right/up/down with the arrow keys.
To get started with your bot you can modify one of the examplefuncs-players located in the bc18-scaffold directory. You can modify the run.py for python, the main.c for c, and player.java file for java. Then use the web interface to queue a game as before.
Players are named after the directory where they are located. For example, the player "examplesfuncplayer-python" corresponds to the folder where the python code is located.
You can create a new player by copying the examplefuncsplayer and then renaming the folder. The website interface can't see your new folder until you refresh the website. Select the website and press F5 or ctrl+r. Your new bot will then appear in the dropdown menu.
We update the Battlecode game occasionally. Docker should automatically run using the latest version of the Battlecode game. You can manually update to the latest version by entering the following command in the docker quickstart terminal:
docker pull battlecode/battlecode-2018
- How do I play a game?
Ignore the variables for the time being unless you want to specifically test something intensive. Select players from the dropdowns on the right as well as a map, and click "Run Game". A pop-up will display showing the logs of each of the 4 bots (2 bots x 2 maps) while the game runs. When the game ends, the pop-up will disappear and the replay will be in the scaffold folder (the same folder where the bots are located).
- How can I see the replay?
Download the viewer client from http://battlecode.org/#/materials/releases for your operating system. Click on the button with 3 horizontal bars, which will bring up a filesystem that you can select the replay from. Navigate to it, click on the replay, and click "select" in the bottom right of the filesystem window. Then, click the play button in the top right. You can zoom out using the mouse wheel and move your vision using WASD or the arrow keys.
- I ran a game with a broken bot, and now I can't run another game!
Open another Docker Quickstart window (start.sh) and type the following command: docker ps. This will display the information of the currently running container. Take note of the container ID (the first entry) and type docker kill {ID}. You only need to type the first couple characters, e.g. docker kill e06. Go back to the original quickstart window and type bash run.sh again.
- Running
bash run.shkeeps downloading a lot of garbage files!
Again open another Docker Quickstart window (start.sh) and type the following command: docker container ls -a. This will display the information of all containers, including the running one. Type docker container rm {id} for each of the non-running containers. Again you only need to type the first few characters, e.g. docker container rm ff4.
A possibly more robust solution to this problem is via the --rm flag. Running bash run.sh --rm should, in theory, remove the container after termination.
- The Python example bot explodes!
There is currently an API bug tied to building blueprints. If you avoid gc.blueprint() then you should be fine for the time being.
- Docker is taking up too much memory! / I get out of memory errors when running
run.sh!
Docker saves some information between runs called images, containers, and volumes. Unchecked, these can quickly take over many gigs of storage. Occasionally, run the following 4 lines:
docker stop $(docker ps -q)
docker container rm $(docker container ls -aq)
docker volume rm $(docker volume ls -q)$
docker volume prune
which should free up a lot of space.
- I get a 'We dun goof no map found' error!
Ignore it. This should happen when using the test map.
- I don't see any players/maps in the dropdown and/or my console says that
/playercan't be found!
This one is pretty tricky to track down. Try looking at your run.sh file and changing /players to /player if necessary. You can also try running the pwd command in your scaffold directory and replacing $PWD in run.sh with that absolute path. Additionally make sure your filepath doesn't contain any spaces, special characters, etc. that may confuse the parser.
- The Python bot crashes with an error of the form
can't open file run.py!
The issue is most likely that you are using Windows line endings (\r\n) rather than Unix line endings (\n) which confuses the shell script and gives some silly error. To fix this, make sure to convert all your run.sh files to Unix format before running a game. You can accomplish this with an editor like Notepad++ (Edit -> EOL Conversion -> Unix/OSX Format) or the dos2unix command line tool (e.g. dos2unix */run.sh).
- Why is my bot dying with a
Killedmessage?
This means you went over your memory limit. See this gist for some tips on fixing that problem.