Config recipes

Config recipes

Copy paste, change the host, port and password. Everything not mentioned is left at its default, wich is deliberate: dont change settings you dont have a reason to change.

Standard 50v50, 100 slots

The one most people want. Cap of 50 a side, third faction shut.

{
  "servers": [
    { "name": "50v50", "host": "YOUR.IP", "port": 7779, "token": "YOUR_RCON_PASSWORD" }
  ]
}

Thats genuinely it. Every default is tuned for this.

32v32, 64 slots

{
  "sideCap": 32,
  "servers": [
    { "name": "32v32", "host": "YOUR.IP", "port": 7779, "token": "YOUR_RCON_PASSWORD" }
  ]
}

Small community server, under 40 players

Tighten the tolerance, becuase a gap of 3 matters a lot more at 30 players than at 90.

{
  "sideCap": 20,
  "gapTolerance": 2,
  "servers": [
    { "name": "our box", "host": "YOUR.IP", "port": 7779, "token": "YOUR_RCON_PASSWORD" }
  ]
}

All three factions open

If you dont want the third side shut, say so. It then leaves anybody on it completly alone and only balances the other two.

{
  "closedFaction": null,
  "servers": [
    { "name": "three way", "host": "YOUR.IP", "port": 7779, "token": "YOUR_RCON_PASSWORD" }
  ]
}

Note the rescue feature wont work with this on, and the validator will tell you so. The imbalance maths dosent mean anything across three sides.

Several servers, one balancer

One process handles the lot. Dont run a second copy, they will fight over the same players.

{
  "servers": [
    { "name": "#1", "host": "YOUR.IP", "port": 7779, "token": "PASSWORD_ONE" },
    { "name": "#2", "host": "YOUR.IP", "port": 7789, "token": "PASSWORD_TWO" },
    { "name": "#3 32v32 night", "host": "OTHER.IP", "port": 7779, "token": "PASSWORD_THREE",
      "sideCap": 32 }
  ]
}

Any setting can be overridden per server like sideCap is there.

With your own advert instead of the default

{
  "announce": {
    "everyMinutes": 60,
    "minPlayers": 10,
    "message": "YOURCLAN.COM - come and squad up"
  },
  "servers": [
    { "name": "my server", "host": "YOUR.IP", "port": 7779, "token": "YOUR_RCON_PASSWORD" }
  ]
}

Or shut it up entirely:

{
  "announce": { "message": "" },
  "servers": [
    { "name": "my server", "host": "YOUR.IP", "port": 7779, "token": "YOUR_RCON_PASSWORD" }
  ]
}

With your admins exempt

Steam ids, not names. Names change, ids dont. These people are then never moved, never bounced, and never pulled off the closed faction.

{
  "exempt": ["00000000000000001", "00000000000000002"],
  "servers": [
    { "name": "my server", "host": "YOUR.IP", "port": 7779, "token": "YOUR_RCON_PASSWORD" }
  ]
}

Those are placeholders, swap them for real ones. A steam id is 17 digits and starts 7656. You can get somebodys from their profile url, or from any steam id lookup site.

Keeping the password out of the file

{
  "servers": [
    { "name": "50v50", "host": "YOUR.IP", "port": 7779, "tokenEnv": "WD_RCON_BOX1" }
  ]
}

Then export WD_RCON_BOX1=yourpassword in your service file or shell. Nothing secret ends up anywhere git can see it.

Letting it rescue a ruined match

Off by default. This one restarts rounds, so read the readme section before you switch it on, and run it in --dry-run for a few matches first to see when it would have fired.

{
  "rescue": { "enabled": true },
  "servers": [
    { "name": "my server", "host": "YOUR.IP", "port": 7779, "token": "YOUR_RCON_PASSWORD" }
  ]
}