Game statistics: stats.json

Game File Reference

Overview

• dbmodel.sql - database model
• gameinfos.inc.php - meta-information
• gameoptions.json - game options & user preferences
• img/ - game art
• Game Metadata Manager - tags and metadata media
• material.inc.php - static data
• misc/ - studio-only storage
• modules/ - additional game code
• states.inc.php - state machine
• stats.json - statistics
• X.action.php - player actions
• X.css - interface stylesheet
• Game.php - main logic
• X.js - interface logic
• X.view.php - dynamic game layout
• X_X.tpl - static game layout

---

Useful Components

Official

• Deck: a PHP component to manage cards (deck, hands, picking cards, moving cards, shuffle deck, ...).
• Draggable: a JS component to manage drag'n'drop actions.
• Counter: a JS component to manage a counter that can increase/decrease (ex: player's score).
• ExpandableSection: a JS component to manage a rectangular block of HTML than can be displayed/hidden.
• Scrollmap: a JS component to manage a scrollable game area (useful when the game area can be infinite. Examples: Saboteur or Takenoko games).
• Stock: a JS component to manage and display a set of game elements displayed at a position.
• Zone: a JS component to manage a zone of the board where several game elements can come and leave, but should be well displayed together (See for example: token's places at Can't Stop).

Undocumented component (if somebody knows please help with docs)

• Wrapper: a JS component to wrap a <div> element around its child, even if these elements are absolute positioned.

Unofficial

• BGA Code Sharing - Shared resources, projects on git hub, common code, other links
• BGA Studio Cookbook - Tips and instructions on using API's, libraries and frameworks
• Common board game elements image resources

---

Game Development Process

• First steps with BGA Studio
• Create a game in BGA Studio: Complete Walkthrough
• Tutorial reversi
• Tutorial gomoku
• Tutorial hearts
• BGA Studio Guidelines
• BGA game Lifecycle
• Pre-release checklist
• Post-release phase
• Player Resources - add player help/rules to your game page

---

Guides for Common Topics

• Translations - make your game translatable
• Game Replay
• Mobile Users
• 3D
• Compatibility

---

Miscellaneous Resources

• Studio FAQ
• Tools and tips of BGA Studio - Tips and instructions on setting up development environment
• Studio logs - Instructions for log access
• Practical debugging - Tips focused on debugging
• Troubleshooting - Most common "I am really stuck" situations
• Studio Bugs - Reports against Studio itself (not BGA!)

In this file, you are describing game statistics, that will be displayed at the end of the game.

After modifying this file, you must use "Reload statistics configuration" in BGA Studio Control Panel -> Manage Games ("Game Configuration" section):

https://studio.boardgamearena.com/#!studio

There are 2 types of statistics:

• table statistics, that are not associated to a specific player (i.e.: one value for each game).
• player statistics, that are associated to each players (i.e.: one value for each player in the game).

Statistics types can be "int" for integer, "float" for floating point values, and "bool" for boolean.

Once you defined your statistics there, you can start using "initStat", "setStat" and "incStat" methods in your game logic, using statistics names defined below. See API https://en.doc.boardgamearena.com/Main_game_logic:_yourgamename.game.php#Game_statistics.

If you want to skip some of your statistics according to game variants, do not init it, or call set or inc on it. It will be displayed as "-" (instead of 0 if you init it and don't update it afterwards)

!! It is not a good idea to modify this file when a game is running !!

If your game is already public on BGA, please read the following before any change: https://en.doc.boardgamearena.com/Post-release_phase#Changes_that_breaks_the_games_in_progress

Notes:

• Statistic index is the reference used in setStat/incStat/initStat PHP method
• Statistic index must contains alphanumerical characters and no space. Example: 'turn_played'
• Statistics IDs must be >=10
• Two table statistics can't share the same ID, two player statistics can't share the same ID
• A table statistic can have the same ID as a player statistics, however its not recommended unless it is same conceptually (like turns_number is same statistic in both per table and per player)
• Statistics ID is the reference used by BGA website. If you change the ID, you lost all historical statistic data. Do NOT re-use an ID of a deleted statistic.
• Statistic name is the English description of the statistic as shown to players
• The order in which the stats will appear in the endscreen is determined by the order in the array, NOT by the ID. That is helpful for stats which getting added later but need to be higher up in the list.
• Statistic names and labels are automatically added to the translations system, so there is no need to wrap them in totranslate() calls
• Previously, this was a PHP file (stats.inc.php). You can continue to use this format for old projects. (Note: once a game has been committed with a stats.json file, it is not possible to go back without admin intervention.)

{
  "table": {
    "turns_number": {
      "id": 10,
      "name": "Number of turns",
      "type": "int"
    }
  },
  "player": {
    "turns_number": {
      "id": 10,
      "name": "Number of turns",
      "type": "int"
    },
    "player_teststat1": {
      "id": 11,
      "name": "player test stat 1",
      "type": "int"
    },
    "player_teststat2": {
      "id": 12,
      "name": "player test stat 2",
      "type": "float"
    }
  }
}

Sometimes you may want to display a label instead of a number (for instance if you want to indicate the winning faction as a table statistic, and the faction chosen by each player as a player statistic in a game like Terra Mystica).

You can do this by adding a "value_labels" key following the "table" and "players" keys. Please note that the labels apply to both table and player statistics, so you should pay attention to use the same statistic number for the same type of statistic (or to skip one number if labelling should not be applied for both)

{
  "table": {
    "winning_race": {
      "id": 11,
      "name": "Winning race",
      "type": "int"
    },
  },
  "value_labels": {
    "11": [
      "None (or tied)",
      "Auren",
      "Witches",
      "Fakirs",
      "Nomads",
      "Chaos Magicians",
      "Giants",
      "Swarmlings",
      "Mermaids",
      "Dwarves",
      "Engineers",
      "Halflings",
      "Cultists",
      "Alchemists",
      "Darklings"
    ]
  }
}

If you want to consider some internal game statistics for game developer, publisher or admins's purpose only, simply add the following extra property : "display" => "limited". For instance :

{
  "player_teststat2": {
    "id": 12,
    "name": "player test stat 2",
    "type": "float",
    "display": "limited"
  }
}

Translations

Note that any name or value_labels text in these JSON files are automatically added to the translation system, even though they aren't wrapped in totranslate() calls.