# Server configuration and commands

This documentation currently only lists new changes that were introduced in OpenMoHAA.

## Home directory

In original MOH:AA, the game installation directory is used to store mods and data, it's not the case in OpenMoHAA as it uses the home directory by default to write data in here, and the home directory can be used to store mods. This behavior can be changed:
- `set fs_homepath Z:\openmohaa_data` user data will be read and written in the directory located in `Z:\openmohaa_data`
- `set fs_homepath homedata` the subdirectory `homedata` in the game directory will be used to read and store user data
- `+set fs_homepath .` (not recommended) the game directory will be used for storing user data just like the original MOH:AA

The variable defaults to the following value depending on the OS:
- `%APPDATA%\openmohaa` on Windows
- `~/.openmohaa` on Linux

## Networking

### Configure the network components

The network components can be tweaked to use IPv4/IPv6. IPv6 is disabled by default on dedicated servers but that can be changed:
- `set net_enabled 1` enables IPv4 only - the default on the dedicated server executable
- `set net_enabled 2` enables IPv6 only
- `set net_enabled 3` enables both IPv4 and IPv6 - the default on the standalone executable

The master server (gamespy protocol) doesn't support IPv6 servers, which means if IPv4 is disabled and IPv6 is only used, the server won't be visible in the internet game server list.

### Optimization (or Antichams)

There is a new variable, `sv_netoptimize` that helps optimizing network bandwidth, by not telling players about other players they do not see. It is also an useful protection against cheaters. For each client, the server optimizes by only sending them information about other players that they can see. Clients won't see other players they can't see:
- `set sv_netoptimize 0` disables the optimization - the default
- `set sv_netoptimize 1` enables the optimization for entities that are moving
- `set sv_netoptimize 2` enables the optimization always

This option exists since **Medal of Honor: Allied Assault Breakthrough** 2.30, however it was enhanced: sounds like footsteps will be sent so players don't get confused.

### Managing bans

A new feature was introduced to ban IP addresses, thanks to the [ioquake3](https://ioquake3.org/) project. Bans are saved by default in `serverbans.dat` but it can be modified with the `sv_banFile` variable. Here are commands to manage bans:

|Name       |Parameters                             |Description
|-----------|---------------------------------------|-----------
|rehashbans |                                       |Loads saved bans from the banlist file
|listbans   |                                       |Lists all banned IP addresses
|banaddr    |ip[*/subnet*] \| clientnum [*subnet*]  |Bans an IP through its address or through a client number, a subnet can be specified to ban a network range
|exceptaddr |ip[*/subnet*] \| clientnum [*subnet*]  |Adds an IP as an exception, for example IP ranges can be banned but one or more exceptions can be added
|bandel     |ip[*/subnet*] \| num                   |Unbans an IP address or a subnet, the entry number can be specified as an alternative
|exceptdel  |ip[*/subnet*] \| num                   |Removes a ban exception
|flushbans  |                                       |Removes all bans

Examples:
- `banaddr 192.168.5.2` will ban the IP address **192.168.5.2**
- `banaddr 192.168.1.0/24` will ban all **192.168.1.x** IP addresses (in the range **192.168.1.0**-**192.168.1.255**)
- `banaddr 2` will ban the IP address of the client **#2**
- `banaddr 4 24` will ban the subnet of client **#4** - i.e if client **#4** has IP **192.168.8.4**, then it will ban all IPs ranging from **192.168.8.0**-**192.168.8.255**
- `exceptaddr 3` will add the IP of client **#3** as an exception
- `bandel 192.168.8.4` will unban **192.168.8.4**
- `bandel 192.168.1.0/24` will unban the entire **192.168.1.0** subnet (IP ranging from **192.168.1.0**-**192.168.1.255**)

To calculate IP subnets, search for `IP subnet calculator` on Internet.

## Game

### Bots

Bots can be used for testing. They don't move by default, so a mod will be needed, like [eaglear bots](https://www.moddb.com/mods/medal-of-honor-world-war-1/downloads/moh-eaglear-bots):
- `set sv_maxbots x` must be used to configure the maximum number of bots
- `set sv_minPlayers x` is optional and can be used to set the minimum number of players that the server should have. Bots will be spawned based on the minimum number of players.
- `addbot x` where x is the number of bots to add
- `removebot x` where x is the number of bots to remove

### Chat

Chat messages will be logged in the console and in the logfile without requiring to set the `developer` variable.

The in-game chat can be tweaked:
- `set g_instamsg_allowed 0` to disable voice instant messages
- `set g_instamsg_minDelay x` where x is the delay in milliseconds, the minimum delay between each instant messages to avoid spamming
- `set g_textmsg_allowed 0` to disable text messages. All, team and private messages will be disabled
- `set g_textmsg_minDelay x` where x is the delay in milliseconds, the minimum delay between each text message to avoid spamming