Wargus Human-User Study Data Archive

The Wargus data was collected from two human-user studies, involving 6 and 8 participants, respectively. The studies followed a round-robin tournament format wherein each participant played a one versus one game against every other participant. For each game played, a Wargus replay file was created from each player's perspective. The replay file lists the actions issued by all units for the duration of the game. The Wargus replay files can be used to recreate the game exactly via the Wargus engine. In addition to the replay files, a full game log was generated that provides the location of all game units at each game cycle. The full logs are not necessary to replay the relevant game, but contain higher resolution data about the game state than the replay files. Lastly, we created a set of strategy labels for each player in every game using data drawn from both the replay and full log files. The strategy labels are provided along with a unit compositional breakdown of each player in 500 game cycle increments.

The replay archive contains 88 replays corresponding to 44 one versus one matchups. The replays, full game logs, and strategy labels are sorted by tournament date (December 5th and December 12th, 2009) and player ID (1 through 8). Player IDs are unique to each tournament date (i.e., Player 1 on December 5th is not the same Player 1 on December 12th). All files listed follow the same naming scheme. The scheme is [player ID#]v[player ID#]_.*. The [player ID#] on either side of the "v" character denotes the two players involved in the match. An underscore immediately following the player ID# indicates that player was the decided winner. Some matches do not have decided winners; this may occur if the game went over the allowed time limit with no clear winner or the game crashed prior to completion. There may also be an additional "r" character at the end of the file name, which designates that this game is a rematch of a previously played game between two players. The following are examples of files names: "1_v2.*", "7v4_.*", and "1v2r.*" The first player listed in a file name indicates the perspective from which the file is derived. For example, the replay file having the name "1_v2.log" will play from the perspective of player 1, giving player 1's visibility of the game state, resource count, etc. Similarly, the strategy label "2v1_.csv" will contain the unit list and pursued strategy of player 2.

The Wargus replay files are used by the Wargus engine to recreate the conditions of the recorded game exactly. For every one versus one matchup, we generated two replay files; one from each player's perspective. Replay files are composed of a list of actions taken by all units in the game. They are unique to each player in that they represent that player's perception of the game state (resource holdings, exploration of the game map, etc.). The format of the replay file is shown below.

A line in the body of the replay file contains the game cycle (current status of the game clock), the unit identification number of the unit performing the action, the unit type (peasant, archer, etc.) of the unit performing the action, and the action itself (attack, move, build, etc.). The remaining components of the line are the arguments relevant to the action taken. For example, a "move" command takes only a target X,Y location on the game map, whereas a "build" command requires an X,Y, and the structure to be built.

In addition to a replay file, our instrumented version of Wargus generates a full log file for each game played. The full log lists the position and ownership of all units at every game cycle. For this reason, even very short games can generate very large log files (100 or more megabytes). The log files can be downloaded separately below or can be reconstructed using a similarly-instrumented version of Wargus and the shorter replay files.

• Rush
• Description: Sending out melee troops early in the game in attempt to destroy the other player.
• Strawman Label Rule: Game cycle is less than 10000, less than 10 peasants/peons, 1 town-hall/great-hall, 2 or more footman/grunt, 1 or more barracks.
• Fast Expand
• Description: Building another town-hall/great-hall early in the game to gain more control and resources on the map.
• Strawman Label Rule: Game cycle is less than 15000, 2 or more town-halls/great-halls, no barracks.
• Strong Economy
• Description: Pumping out peasants or peons early in the game to obtain a large amount of resources.
• Strawman Label Rule: Game cycle is less than 15000, more than 12 peasants/peons, 1 town-hall/great-hall, no barracks.
• Standard
• Description: Using basic land troops as the primary army and main form of combat
• Strawman Label Rule: N/A
• Navy
• Description: Using naval ships as the primary army and main form of combat.
• Strawman Label Rule: 1 or more shipyard and 1 or more oil-platform.
• Air
• Description: Using aerial ships as the primary army and main form of combat.
• Strawman Label Rule: 1 or more gryphon-aviary/dragon-roost.
• Ogres/Knights
• Description: Researching and developing stronger and more advanced land troops.
• Strawman Label Rule: More than 3 ogres/knights.

December 5th Tournament Files

December 12th Tournament Files