Network options - Liquid War 6
Description: Liquid War 6

Next: Map parameters, Previous: Sound options, Up: Reference

### 4.9 Network options

#### 4.9.1 bind-ip

— Command-line option: `--bind-ip=<value>`
— Environment variable: `LW6_BIND_IP`
— XML key: `bind-ip`

> Type: string

> Default value: 0.0.0.0

> The IP address to bind on when listening to network messages. You can use this to specifically use a given network interface, the default will listen on any available interface.

#### 4.9.2 bind-port

— Command-line option: `--bind-port=<value>`
— Environment variable: `LW6_BIND_PORT`
— XML key: `bind-port`

> Type: integer

> Default value: 8056 Min value: 1 Max value: 65535

> The IP port to bind on when listening to network messages. The default should work out of the box, and will ease up the discovery process. That is, if you use your own settings, automatic detection of your server by other servers might not work so well.

#### 4.9.3 broadcast

— Command-line option: `--broadcast=<value>`
— Environment variable: `LW6_BROADCAST`
— XML key: `broadcast`

> Type: boolean

> Default value: true

> Allows the program to send broadcast messages on the network. It can be usefull to disable those if you don't use UDP node discovery and/or if there's a sysadmin arround who does not enjoy permanent broadcasts on his LAN.

#### 4.9.4 cli-backends

— Command-line option: `--cli-backends=<value>`
— Environment variable: `LW6_CLI_BACKENDS`
— XML key: `cli-backends`

> Type: string

> Default value: tcp,udp,http

> The client backends to use. Most of the time the default is fine, change it only if you specifically want to disactivate some protocol, or if you want to activate a custom-made client backend. It's a comma separated list.

#### 4.9.5 known-nodes

— Command-line option: `--known-nodes=<value>`
— Environment variable: `LW6_KNOWN_NODES`
— XML key: `known-nodes`

> Type: string

> Default value: http://ufoot.org:8056/,http://ufoot.hd.free.fr:8056/

> List of known nodes, nodes which the program will try to contact first to get the list of other nodes. This is mostly usefull when program is launched for the first time, after this it should keep an up-to-date list of known servers in its internal database and automatically reconnect to them next time it starts. You might want to change this if you really want to connect to a given server which is not publically listed. The list is comma separated.

#### 4.9.6 node-description

— Command-line option: `--node-description=<value>`
— Environment variable: `LW6_NODE_DESCRIPTION`
— XML key: `node-description`

> Type: string

> Default value: No description.

> The description of your node, that is a text that describes your server. This will typically appear when pointing a web client on the public server URL, it is for general information, so if there's something special about your server, say it here.

#### 4.9.7 node-title

— Command-line option: `--node-title=<value>`
— Environment variable: `LW6_NODE_TITLE`
— XML key: `node-title`

> Type: string

> Default value:

> The title of your node, that is the name which will be displayed when listing servers. This is different from player name, for there can be several players on a single computer. By default this will be set to hostname.

#### 4.9.8 password

— Command-line option: `--password=<value>`
— Environment variable: `LW6_PASSWORD`
— XML key: `password`

> Type: string

> Default value:

> The password to use for network games. Do not use a valuable password, as this is stored as clear text on your hard drive. Still, the game will only send a hash/checksum of the password on the network so eavesdropper won't be able to read it. They can see the hash/checksum and use it if clever, but they can't guess the real password. A blank password means anyone can join your games when you act like a server.

#### 4.9.9 public-url

— Command-line option: `--public-url=<value>`
— Environment variable: `LW6_PUBLIC_URL`
— XML key: `public-url`

> Type: string

> Default value:

> The public URL of your server. By default the game will pick up one for you. In fact, the clients discovering your server should guess the public URL, probably http://<your-ip>:<your-port>/ but you might need to use your own settings if you are using NAT or an Apache reverse-proxy to rewrite HTTP requests.

#### 4.9.10 skip-network

— Command-line option: `--skip-network=<value>`
— Environment variable: `LW6_SKIP_NETWORK`
— XML key: `skip-network`

> Type: boolean

> Default value: false

> If set, then game won't do anything network related. No listen, no connect, no nothing. You are playing locally.

#### 4.9.11 srv-backends

— Command-line option: `--srv-backends=<value>`
— Environment variable: `LW6_SRV_BACKENDS`
— XML key: `srv-backends`

> Type: string

> Default value: tcpd,udpd,httpd

> The server backends to use. Most of the time the default is fine, change it only if you specifically want to disactivate some protocol, or if you want to activate a custom-made server backend. It's a comma separated list.