In this guide, we will list a couple of simple, useful practices to follow when building your Halite bot.

Log to a file and not to console

stdout and stdin in are used to communicate with the game environment. As such, you cannot use functions like System.out.println, print(), or std::cout. Instead, print debugging information to a log file.

The starter kits have limited functionality to do this already, and may even print out debugging information about their internals.

Test new vs old before upload

Before submitting a new bot to the online leaderboard, we recommend running some games against the version of your bot that is currently on the leaderboard. If your new bot consistently wins, then put it up!

Check out our tool that makes it easier for you to do regression testing.

Debug timeout issues by disabling timeout locally

When debugging latency issues with your bot, it can be helpful to disable game environment timeouts. To do so, append the -t flag to your environment command, like so:

./halite -d "240 160" "python3" "python3" -t

Reproducible Maps

You can replay games with the exact same map, which is useful when trying to debug or tweak bot behavior. Simply specify a seed and map size when running the game:

./halite -d "30 30" -s 42 "python3" "python3" -t

Debugging with an IDE

There is a community contributed method for running a Halite bot from a custom debugger locally. More on this can be found here on the forums. Warning: this method has not been tested with Halite II. Use at your own risk.