Next: Script hooks, Previous: Map style.xml, Up: Reference

### 4.12 Advanced settings

#### 4.12.1 audit

— Command-line option: `--audit`
— Environment variable: `LW6_AUDIT`

> Display all path values, defaults and current settings. This output is very usefull to track down problems such as missing directories, broken installations. If you get an error message that suggests some file is missing, then give this option a try.

#### 4.12.2 bench

— Command-line option: `--bench`
— Environment variable: `LW6_BENCH`

> Runs a benchmarking test which will report an approximative performance estimation of the game on your computer.

#### 4.12.3 bot-iq

— Command-line option: `--bot-iq=<value>`
— Environment variable: `LW6_BOT_IQ`
— XML key: `bot-iq`

> Type: integer.

> The IQ (intelligence quotient) of bots. Typically, a value of 100 will make the bot behave normally, performing at its best. A value of 0 will just make it act the worst way it can. Values over 100 probably won't change anything compared to 100, but this truely depends on which bot backend you're running.

#### 4.12.4 bot-speed

— Command-line option: `--bot-speed=<value>`
— Environment variable: `LW6_BOT_SPEED`
— XML key: `bot-speed`

> Type: float.

> The speed of bots, 1 means normal speed, higher value will speed it up, lower will slow it down. Note that this only has an impact on bot engines, not on the game speed itself.

#### 4.12.5 checkpoint-period

— Command-line option: `--checkpoint-period=<value>`
— Environment variable: `LW6_CHECKPOINT_PERIOD`
— XML key: `checkpoint-period`

> Type: integer.

> Defines with what period (in msec) system values such as frames per sec, network traffic, and others, will be updated. Default value should fit in most cases.

#### 4.12.6 commands-per-sec

— Command-line option: `--commands-per-sec=<value>`
— Environment variable: `LW6_COMMANDS_PER_SEC`
— XML key: `commands-per-sec`

> Type: integer.

> Defines the number of commands per second. When a command is generated, orders are actually sent to the game engine, for instance, 'this cursor moved there'. So this option will affect game responsiveness, setting this to a high value will make the game more responsive but consume bandwidth on network games.

#### 4.12.7 demo

— Command-line option: `--demo`
— Environment variable: `LW6_DEMO`

> Start the game in demo mode. 2 bots play against each other forever.

#### 4.12.8 display-console

— Command-line option: `--display-console=<value>`
— Environment variable: `LW6_DISPLAY_CONSOLE`
— XML key: `display-console`

> Type: boolean.

> Defines wether the interactive system console must be displayed. Note that console support must have been enabled at compilation time. It might not be available on your computer, for instance if you are running a system such as Microsoft Windows.

#### 4.12.9 display-fps

— Command-line option: `--display-fps=<value>`
— Environment variable: `LW6_DISPLAY_FPS`
— XML key: `display-fps`

> Type: boolean.

> Set this to 'true' to display the number of frames per second. When this gets too low... play a smaller map, buy a new computer or contribute and hack Liquid War 6 so that it runs faster!

#### 4.12.10 frames-per-sec

— Command-line option: `--frames-per-sec=<value>`
— Environment variable: `LW6_FRAMES_PER_SEC`
— XML key: `frames-per-sec`

> Type: integer.

> Defines how many frames will be displayed per second. Of course this is a maximum value, if your hardware can't keep up with this value, display will just be slow, no matter what value you define here. Note that you might really wish to have something rather low here, to keep network and 'logic' function responsiveness. Passed 60 frames per second, speed is really only for visual comfort, as Liquid War 6 is now so fast-paced that it requires 200 frames/sec to outperform opponents.

#### 4.12.11 io-per-sec

— Command-line option: `--io-per-sec=<value>`
— Environment variable: `LW6_IO_PER_SEC`
— XML key: `io-per-sec`

> Type: integer.

> Defines the number of calls to input/output functions per second. This can affect speed of menus but also cursors, but won't change the speed of the game itself. It's a cosmectic, comfort option.

#### 4.12.12 loader-sleep

— Command-line option: `--loader-sleep=<value>`
— Environment variable: `LW6_LOADER_SLEEP`
— XML key: `loader-sleep`

> Type: float.

> Defines how long the loader thread should wait between two polls. Default value should fit in most cases.

#### 4.12.13 log-level

— Command-line option: `--log-level=<value>`
— Environment variable: `LW6_LOG_LEVEL`
— XML key: `log-level`

> Type: integer.

> Defines the log level, that is, how verbose the program will be regarding logs and console output. 0 (ERROR) is the minimum, only errors are reported. 1 (WARNING) means errors + warnings. 2 (NOTICE) displays most important messages. 3 (INFO) is the default, the log file will contain all messages but debug stuff. 4 (DEBUG) logs everything, including debug informations.

#### 4.12.14 memory-bazooka-eraser

— Command-line option: `--memory-bazooka-eraser=<value>`
— Environment variable: `LW6_MEMORY_BAZOOKA_ERASER`
— XML key: `memory-bazooka-eraser`

> Type: boolean.

> The memory eraser is a tool which will systematically fill allocated memory with 'M', and overwrite all allocated bytes with 'F' before freeing memory. It will even handle realloc calls. This is usefull to track bugs. Indeed, with this option enabled, freshly allocated memory will never contain zeroes unless one calls calloc, and if you ever free some memory zone before being done with it, it will be filled with junk and therefore not be usable. The memory bazooka must be big enough if you want this feature to actually work.

#### 4.12.15 memory-bazooka-size

— Command-line option: `--memory-bazooka-size=<value>`
— Environment variable: `LW6_MEMORY_BAZOOKA_SIZE`
— XML key: `memory-bazooka-size`

> Type: integer.

> The memory bazooka is a brute-force tool, conceived after a full night spent tracking some memory leak. The idea is to keep a track of all allocated pointers, when the data was allocated (timestamp), where in the code (file, line), and even point out what data there is in that place. A memory bazooka report at the end of the game will just show what's left. There should be nothing. This parameter is here to avoid wasting CPU cycles on a feature which is very debug-oriented and does not really make sense for the casual user. Set it to 0 for best performance, something like 100 might just be helpfull, but 1000000 is the right way to seriously debug code.

#### 4.12.16 modules

— Command-line option: `--modules`
— Environment variable: `LW6_MODULES`

> Tells which modules have been enabled when the game was compiled. It's still possible to add or remove modules afterwards, but this option allows you to know how things were at first.

#### 4.12.17 pilot-lag

— Command-line option: `--pilot-lag=<value>`
— Environment variable: `LW6_PILOT_LAG`
— XML key: `pilot-lag`

> Type: integer.

> Maximum lag, in rounds, until the game engine is slowed down. This will typically be usefull if your computer is too slow for the map resolution and the game speed you set up.

#### 4.12.18 pilot-sleep

— Command-line option: `--pilot-sleep=<value>`
— Environment variable: `LW6_PILOT_SLEEP`
— XML key: `pilot-sleep`

> Type: float.

> Defines how long the pilot thread should wait between two polls. Default value should fit in most cases.

#### 4.12.19 quick-start

— Command-line option: `--quick-start`
— Environment variable: `LW6_QUICK_START`

> Start the game just like if the player had requested a quick start, without showing any menu.

#### 4.12.20 server

— Command-line option: `--server`
— Environment variable: `LW6_SERVER`

> Start the game in server mode, without requiring any graphics backend.

#### 4.12.21 target

— Command-line option: `--target`
— Environment variable: `LW6_TARGET`

> Display all known system target properties, including os and cpu informations.