In this game each player commands a fleet of starships in the outer space. The goal is to get the highest possible score by collecting point bonuses and killing other players’ starships.
The game is played on a bidimensional cylindric universe. After unfolding, this universe can be seen as the result of setting side by side the same rectangle repeatedly along the vertical edge:
This repeated rectangle is an n × m grid of cells. Thus, any pair (i, j) such that 0 ≤ i < n determines the position of a cell of the universe. Note that two positions (i,j) and (i,j′) such that (j − j′) mod m = 0 actually refer to the same cell. In what follows we will refer to i and j as the row and the column of the position (i, j), respectively.
Each cell of this universe may be empty or may contain:
Players can look up the content of any cell of the universe during the match.
Each player commands a number of starships which is a parameter of the game. Each starship has a unique identifying number. The starships commanded by the same player have consecutive identifiers.
At each round a player can command any of its starships to move in a particular direction or to shoot a missile (but not the two at the same time).
In general, the movement of the elements on the universe follows the next rules:
In the game viewer, the window is the part of the universe that will be shown. Since the window is taken as the system of reference for the visualization, it apparently does not move; similarly, starships moving by default apparently do not move either, etc.
A starship may shoot a missile if it has at least one in its stock (which is then consumed). There is an initial number of missiles in the stock of each starship. This stock can be enlarged by means of missile bonuses. When a starship shoots, the new missile automatically moves forward two columns from the starship position, and then immediately after, the starship also moves with the default direction.
When a starship and a bonus coincide in the same cell, the starship consumes the bonus (increasing the number of available missiles if it is a missile bonus, or getting more score if it is a point bonus). Once a bonus is consumed, if possible it reappears on a random position outside the window. This random position is guaranteed to be previously empty and such that its surrounding square 5 × 5 is free from missiles or starships.
In the other possible cases of collision, when two elements coincide in the same cell both are destroyed. In particular, if one of the colliding elements is a missile shot by a starship of player A and the other element is a starship of a different player B, then A increases its score.
When a starship is killed, it regenerates if possible after a number of rounds, on a random position of the window. This random position is guaranteed to be previously empty and such that its surrounding square 5 × 5 is free from missiles, starships or asteroids. The number of available missiles is the same as before it died.
As a final consideration regarding collisions, when in a round a starship (or a missile) moves from an initial cell to a final cell, in some cases it is considered that it also passes certain intermediate cells. More specifically:
The exact order in which intermediate cells are visited can be looked up in the map dir2all defined in Utils.cc.
After the instructions of all players are collected, the following actions take place:
A game is determined by following set of parameters:
number_players(): number of players in the game.
number_rounds(): number of rounds that will be played.
number_rows(): number of rows of the universe (and of the window).
number_universe_columns(): number of columns of the universe.
number_window_columns(): number of columns of the window.
number_starships_per_player(): number of starships for each player.
number_starships(): total number of starships.
number_rounds_to_regenerate(): number of rounds to wait before a starship can regenerate.
number_missile_bonuses(): number of missile bonuses in the game.
number_point_bonuses(): number of point bonuses in the game.
bonus_missiles(): number of extra missiles obtained when consuming a missile bonus.
bonus_points(): number of extra points obtained when consuming a point bonus.
kill_points(): number of points obtained when killing a starship of another player.
All these parameters can be accessed by the players during the game.
Here we will explain how to run the game under Linux, but a similar procedure should work as well under Windows, Mac, FreeBSD, OpenSolaris... The only requirements on your system are g++, make and a modern browser like Mozilla Firefox or Chromium.
To run your first match, follow the next steps:
./Game Demo Demo Demo Demo < default.cnf > default.res
Here, we are starting a match with 4 instances of the player ”Demo” (included with the source code), with the game configuration defined in ”default.cnf”. The output of this match will be stored in ”default.res”.
A script run.sh for carrying out steps 2-4 automatically is also provided.
Use the --help option of Game to see a list of all options you can use. For instance, the option --list will show a list with all the available player names.
If needed, remember you can run make clean to delete the executable and all object files and start over the build.
To create a player, copy the file AINull.cc (an empty player that is provided as a template) to a new file with the same name format (AIWhatever.cc).
Then, edit the file you just created and change the playername line to your own player name, as follows:
The name you choose for your player must be unique, non-offensive and less than 12 letters long. It will be used to define a new class PLAYER_NAME, which will be referred to below as your player class. The name will be shown as well when viewing the matches and on the website.
Now you can start implementing the method play(). This method will be called every round and is where your player should decide what to do, and do it. Of course, you can define auxiliary methods and variables inside your player class, but the entry point of your code will always be this play() method.
From your player class you can also call functions to access the board state, as defined in the Board class in Board.hh, and to command your units, as defined in the Action class in Action.hh. These functions are made available to your code using multiple inheritance via the class Player in Player.hh . The documentation on the available functions can be found in the aforementioned header files of each class. You can also examine the code of the “Demo” player in AIDemo.cc as an example of how to use these functions. Finally, it may be worth as well to have a look at the file Utils.hh for useful data structures.
Note that you should not modify the factory() method from your player class, nor the last line that adds your player to the list of available players.
To test your strategy against the Dummy player, we provide the AIDummy.o object file. This way you still will not have the source code of our Dummy, but you will be able to add it as a player and compete against it locally.
To add the Dummy player to the list of registered players, you will have to edit the Makefile file and set the variable DUMMY_OBJ to the appropriate value. Remember that object files contain binary instructions targeting a specific machine, so we cannot provide a single, generic file. If you miss an object file for your architecture, contact us and we will try to supply it.
Pro tip: You can ask your friends for the object files of their players and add them to the Makefile too!
Once you think your player is strong enough to enter the competition, you should submit it to the Jutge.org website (https://www.jutge.org). Since it will run in a secure environment to prevent cheating, some restrictions apply to your code: