Answer:
The game's working directory must be the /Binaries.

The basic command line is:

aa3game.exe server BaseMapName[Options] [MULTIHOME=x.x.x.x] [–CONFIGSUBDIR=]

BaseMapName

The following maps are shipping with AA3.0 and can be put in the "BaseMapName" portion of the server command line:

• Alley_day_cloudy
  
• Bridge_night_clear
  
• Impact_day_cloudy
  
• Pipeline_dawn_clear
  
• Ranch_day_fog
  

Options -

Options are placed immediately after the "BaseMapName" and will begin with a questions mark option.

System Options/Features – System options and features let you control such things as VOIP, server authorization, game server time and player counts. They include:

• ?EnableTS3=Y/N – Enables/Disables TS3. The default is set to enabled in the INI file.
  
• ?GLOBAL - Enables official/authorized server. This option is mutually exclusive with the ?LAN option.
  
• ?LAN - Starts a Local Area Network(LAN) server that does not authorize with the authentication system. It enables the LAN MBS system. It is mutually exclusive with the ?GLOBAL option
  
• ?MaxSpectators=## - where ## is a number 0 through 6, inclusive. Controls how many spectators may watch the game.
  
• ?MaxPlayers=## - where ## is a number between 2 - 26, inclusive. Controls how many players may join the server.
  
• ?TimeLimit=## - where ## is a number for how long rounds are in minutes.

Mission Options – mission options control the game type and variants that can be played during a mission. They include:

• ?MissionType=[type of mission].
  
• ?MissionVariant=[xxxx] - - Name of the mission variant. Variant of missions are dependent on their appropriate.
  
• ?MissionSize=[size] - Sizes are small, medium and large. For AA 3.0 only large maps are available.
  
• ?MissionTourID=inf - Only infantry missions are available with AA 3.0.

Mission Types describe the manner of game play and include:

• CLASSIC : Classic Objective – Classic game play from AA version 2.x
  
• CO : Carry-able Objective - Each team must retrieve and extract an item (like a suitcase)
  
• TAH : Take and Hold - Each team must take and hold one of more objective areas on the map
  
• VIP : VIP Escort – One team escorts a VIP for extraction while the other team tries to stop them
  
• AO : Activated Objective – Each team must activate an objective
  
• AD : Assualt Defense – One team assaults a position while the other team defends it (NOTE: this can also denote classic game play).

Mission Variants allow for future versions of AA3 to change the layout of a Base Map (NOTE: this is for a future release). Mission types are Base map dependant and Mission Variants are Base map and Mission Type dependent. Available mission type/mission variant combinations are for each base map are:

Base Map	Mission Type, Mission Variant
Alley_day_cloudy	CO, dev TAH, east VIP, dev
Bridge_night_clear	classic, dev1 AO, dev1 CO, dev1
Impact_day_cloudy	AO, dev1 TAH, dev VIP, dev
Pipeline_dawn_clear	classic, AD TAH, dev VIP, dev1
Ranch_day_fog	AO, dev1 CO, dev1 VIP, dev1

Authentication Support for Global Servers

• ?AuthServerPassword=xxxx - where xxxx is the password for your AA3 authorized or official server account.
  
• ?AuthServerUserName=xxxx - where xxxx is the user name for your AA3 authorized or official server account.
  
• ?AuthServerIP=x.x.x.x - where x.x.x.x is the IP address for your AA3 authorized or official server account.
  
• ?AuthServerPort=x - where x is the port used for your AA3 authorized or official server account. The default is 8777 and typically this is not used for standard installations.

Multihome Support (Multiple Server Instances)-

Add "MULTIHOME=x.x.x.x" (where "x.x.x.x" is the IP Address to bind the server to) to the end of the server line (be sure to put a space prior to the "MULTIHOME" after the last server option.

Custom Configuration Files

America's Army 3.0 uses the UnrealEngine 3 standard of completely unique sets of configuration files stored in separate subdirectories for those wishing to specify custom configurations on the command line. Each subdirectory must be created under the AA3Game/Config directory (create a subdirectory of the primary "AA3Game/Config" subdirectory). You do not need (nor should) put the entire path as the value for this option.

Example: To store a customer specific configuration file for the customer "JohnsServer" you would create a subdirectory "[AA3 Installer Directory]/AA3Game/Config/JohnsServerConfig" and then add this to your server's command line:

- CONFIGSUBDIR=JohnsServerConfig

- If the directory does not exist the game will automatically create it and populate it with the default configuration values.

Typically this would be used in conjunction with the MULTIHOME option or to run custom configuration options.