Skip to content

Game permissions and default settings

https://environment.hoelle.games/gamespermissions

(Replace environment with dev, staging, or europe-1.)

Version V1.9 of the hinterzimmer back office adds this page. Use it to set game permissions. You need admin rights to use this page.

Use game permissions to allow or deny games for an operator, country, or currency. Enter policies as a valid JSON object. Use jsonlint.com to validate JSON objects.

operator-game-settings figure 6

The image above shows the default policy. This policy allows all operators, countries, and currencies to launch the game.

Record the history of game permission configuration on production in the internal production tracking spreadsheet.


Structure of game permission JSON object

A game permission can contain any of the following lists. Each list is an array of strings. The strings are operator IDs, 2 letter ISO country codes, or 3(4) letter currency codes.

The system evaluates allow lists before deny lists. If an allow list has entries, the system denies all other operators.

The system evaluates operator lists before country code lists. It evaluates country code lists before currency code lists.

{
        "operatorIdAllowList": [],
        "operatorIdDenyList": [],
        "countryCodeAllowList": [],
        "countryCodeDenyList": [],
        "currencyCodeAllowList": [],
        "currencyCodeDenyList": []
}

The following example combines an operator allow list with a currency deny list.

{
  "operatorIdAllowList": [
    "internal_testoperator"
  ],
  "currencyCodeDenyList": [
    "USD",
    "UBTC"
  ]
}

The following example shows an operator allow list with two operator IDs. Both operators can launch the game. The system denies all other operators. Use this method for custom games for one operator.

{
    "operatorIdAllowList":
["31829bfdcc1d40f8ab77a1c2938adf14",
"91fc92e9ea14463d9a3aa8864660de07"]
}

You can also define forced gamesettings. Forced gamesettings override all other settings from operator config or profiles.

globalGameSettings / forced can contain any valid gamesettings.

The following example disables the gamble feature for specific games. It also uses an operator deny list.

{
  "globalGameSettings": {
    "forced": {
      "gambleEnabled": false
    }
  },
  "operatorIdDenyList": [
    "c72f7ccb80614251ad86e1da29aa230b",
    "3b4e392a7c29434c99190a6618b93cc0",
    "93d63d55b45d47939344683d9d522897",
    "b9c1abc13b1447cb9242c2b3e1e0e335"
  ]
}