You don't need to have Git installed in order to take part, but it might help if you're collaborating with others. However, if you're not familiar with Git, now may not be the best time to learn it.
On Windows, you can download Git for Windows here. This also gives you access to a Linux-style Bash shell terminal called Git Bash.
If you have Git installed, you can clone the repository to your local machine using the clone URL above. Alternatively, there's also a link above to download the repository as a zip or tar archive.
A third option, which may make working with your team mates easier, is to register a username on this git server, then fork the project and clone it from there. That will allow you to share code with your team mates by pushing Git commits back up to your forked project.
There's an installation script in the root folder of this repository. This will download and set up an appropriate Java Development Kit for your machine.
Optionally, if your Scott Logic host tells you that you need to do this, you can add the -r option to configure a
proxy URL for downloading the necessary dependencies.
Open a terminal (command prompt), and run the command below.
Windows command prompt:
install [-r http://<proxy_host>:8081/repository]Mac or Linux shell:
./install.sh [-r http://<proxy_host>:8081/repository]In both of the above, <proxy_host> is the hostname provided to you by the Scott Logic host at your event,
if necessary. As an example, if the hostname given to you is WS01161, then (on Windows):
install -r http://WS01161:8081/repositoryIf you're told that no proxy needs to be set up, then all you need to type is
installIt will probably be easier to do development in a Java IDE - ideally one that supports importing Gradle projects, like
Eclipse or IntelliJ IDEA.
Make sure you've set your IDE's JDK to the one downloaded in the above step.
You can find it in the <project_root_dir>/tools/jdk folder.
Make sure you have the downloaded JDK set as an "installed JRE". Go to Window → Preferences → Java →
Installed JREs → Add → Standard VM → Next → Directory..., and navigate to the
<project_root_dir>/tools/jdk/<jdk_name> folder.
To open the project, go to File → Import... → Gradle → Existing Gradle Project, and follow the prompts in the wizard.
First, ensure you have the downloaded JDK set as one of your SDKs. Hit Ctrl+Alt+Shift+S, then go to
Project Settings → Project → New... → JDK, and navigate to the
<project_root_dir>/tools/jdk/<jdk_name> folder.
If you Open the repostory's root folder as a new project, it should detect Gradle and start the import wizard automatically.
The repository includes a pre-compiled game simulator application. It can be run from either the command line, or your IDE.
After each phase of the game, the application prints an ASCII-art representation of the game's current state to the
console. You can review this before hitting Enter to play the next phase.
Since the printed state takes up quite a few lines in the console,
you may find that your IDE's output console can't be made big enough to properly review it,
in which case you may prefer to build and run the game from a command-line terminal.
There's a void main(...) method in the ExampleBot class. You can use that to run or debug a game simulation from
within your IDE.
Open a command line terminal in the root folder of this project and run one of the following commands.
Windows command prompt:
gradlew run -P mainClass=<your_bot_class_fully_qualified_name>Unix shell:
./gradlew run -P mainClass=<your_bot_class_fully_qualified_name>The turn-by-turn game output is rendered as an ascii-art representation of the board with the following key:
A-D: spawn pointa-d: playerX: out of bounds+: collectable
With the initial Bot you should see a very short game consisting of 7 phases ending due to the LONE_SURVIVOR end
condition. The turn-by-turn replay should show 8 players appearing from one spawn point (don't get your hopes up, these
belong to the default bot), and none appearing from the other spawn point. This is because the initial Bot does not
issue any orders, resulting in each player being eliminated by the next player to emerge from the spawn point.
If you have successfully reached this point then you're all set to start improving on the initial Bot to ensure your players have a longer, and perhaps more prosperous, life.
First things first, rename the Bot class so that there are no namespace clashes when uploading to the server, additionally you might want to change the display name which is shown when testing locally. There are only a few restrictions on the compiled code:
- the jar file must be < 20MB
- the com.contestantbots.team package should only contain classes that extend
com.scottlogic.hackathon.game.Bot - any helper or utility classes should either be
- inner classes of your Bot, or
- not have a public constructor
- your Bot should take no more than 5 seconds to calculate the moves otherwise it will be timed out
- you can include more than one Bot class in the uploaded jar file to allow you to test different strategies, however only one Bot can be active at any given time
When you're ready to move on this tutorial provides a step-by-step guide to adding some basic intelligence to your bot.
Testing I'm on the right upstream