Master Guide: How To Change Map On An Arma Server Step-by-Step

Changing the active map on an Arma 3 dedicated or hosted server requires deploying the mission file (.pbo format) into the MPMissions directory and updating the mission cycle within the server configuration file. Administrators must align the mission file name with the target terrain's native world class name and mount any mandatory terrain mod dependencies on startup. Properly configuring the mission rotation parameters inside the server config file ensures seamless map switches and automated server boots without administrative intervention.

Pre-Configuration Audit & Server Environment Prerequisites

Before altering the map or mission cycle on your Arma server, you must gather critical server credentials, identify map dependencies, and ensure your local tools are ready. Modifying mission rotations on live servers without verifying file paths and mod keys can cause persistent startup crashes, infinite loading screens, or mission selection loops.

• Essential Administrative Tools: A secure FTP client such as FileZilla or WinSCP, a plain text editor optimized for configuration files such as Notepad++, and full root or control panel access to your server file system.
• Mandatory File Conventions: The target mission file must be compiled in the Arma Packed Bohemia Object (.pbo) file format. The filename must strictly adhere to the standard naming syntax: mission_name.world_name.pbo (for example, op_coit.Altis.pbo or patrol_v2.Tanoa.pbo).
• Required Dependencies: If changing to a custom or modded terrain (such as Chernarus, Takistan, or Anizay), verify that the terrain mod folders are uploaded to the server root, listed in your startup parameters, and that the matching public server key (.bikey) files are placed inside the server keys directory.
• Estimated Execution Time: Initial setup and execution take approximately 10 to 15 minutes. Server restart requires 2 to 3 minutes of planned service downtime.

Tactical Map Deployment & Server Configuration Workflow

Step 1: Acquire and Prepare the Mission File

Every map instance in Arma functions as a mission package bound to a specific island or terrain world name. If you download a mission from the Steam Workshop or create one in the Eden Editor, you must export or save it as a multiplayer mission.

In the Eden Editor, navigate to File, choose Export, and select Export to Multiplayer. This creates a .pbo file inside your Arma 3 profile MPMissions folder located on your local PC directory. If you are using a Workshop mission, locate the downloaded file within your Steam Workshop cache directory, unpack or copy the .pbo file, and confirm that the file suffix correctly indicates the target map's exact world identifier. For example, a mission built on Malden must end with .Malden.pbo.

Warning: Modifying the world suffix of a .pbo file (for example, renaming a file ending in .Stratis.pbo to .Altis.pbo) will not port the mission to a new map. It will cause severe engine errors upon server loading because the terrain object coordinates will mismatch the map boundaries.

Step 2: Upload Mission Files to the Server MPMissions Directory

Connect to your dedicated server or host instance using your FTP client or web control panel file manager.

Navigate directly to the root directory of your Arma server installation. Locate the folder named MPMissions. Drag and drop your newly prepared .pbo mission file into this directory. Ensure the transfer mode in your FTP client is set to Binary to prevent byte corruption during upload.

Pro-Tip: If running your server on a Linux host (such as Ubuntu Server or Debian), file names are strictly case-sensitive. Always convert your mission file names to lowercase letters (e.g., my_mission.altis.pbo) to prevent pathing mismatches between the configuration file and the physical storage.

Step 3: Configure the Server Mission Cycle in server.cfg

To force the server to load your chosen map upon startup, you must define it in the server configuration file, commonly named server.cfg or CONFIG_server.cfg. Locate this file in your server directory or control panel configuration profile and open it with your text editor.

Scroll down to the bottom of the file to find the class Missions section. If this section does not exist, you must create it. Modify or insert the mission definition block using the following structure:

class Missions { class Mission_1 { template = "your_mission_name.your_world_name"; difficulty = "Custom"; }; };

Replace your_mission_name.your_world_name with the exact name of your .pbo file excluding the .pbo extension. For instance, if your file in MPMissions is named insurgency_v1.Tanoa.pbo, the template line must read: template = "insurgency_v1.Tanoa";

To create an automated multi-map rotation, add sequential classes within the class Missions block:

class Missions { class Mission_1 { template = "operation_one.Altis"; difficulty = "Custom"; }; class Mission_2 { template = "operation_two.Enoch"; difficulty = "Custom"; }; };

Set the persistent parameter above the class Missions block to persistent = 1; to ensure the server keeps the mission world loaded continuously even when all players disconnect.

Step 4: Mount Mandatory Terrain Mods and Security Keys

If your new map relies on a third-party terrain mod (such as CUP Terrains, RHS, or terrain mods from the Steam Workshop), the server must mount these mods upon boot.

First, upload the mod folder (e.g., @cup_terrains_core and @cup_terrains_maps) to the main server installation directory. Next, open the mod's internal keys folder, copy the included .bikey files, and paste them directly into the server's primary keys directory. This step is mandatory to allow client signature verification via BattlEye.

Finally, update your server startup command line or launch parameters script to include the newly added mods in the mod launch string, using semicolons to separate directories:

-mod=@CBA_A3;@cup_terrains_core;@cup_terrains_maps;

Step 5: Restart Server and Monitor RPT Boot Logs

Save your changes to server.cfg, re-upload the file if editing locally, and issue a full server restart command through your control panel or terminal.

As the server boots, open the server log directory and monitor the latest real-time parameter log file (.rpt extension). Search the log for the initialization sequence of your selected world. A successful map load will log entries indicating world initialization, object stream loading, and a message stating that the mission read successfully from MPMissions.

Map World Identifiers & Server Configuration Parameters

When configuring custom or official maps, using the precise engine world name is mandatory for server loading. The table below outlines official Arma terrains alongside popular community modded maps, their exact suffix world identifiers, and their core mod requirements.

Server Boot Diagnostics & Mission Cycle Failure Remedies

Issue 1: Server Hangs on Infinite Loading Screen During Boot

• Root Cause: The mission relies on custom map assets or modded script dependencies that are not mounted in the server startup parameters, or mandatory .bikey signature files are missing from the server keys directory.
• Actionable Fix: Open the latest server .rpt log file and scroll to the bottom. Look for lines stating Missing Addon or Warning Message: Cannot load texture/model. Upload the missing mod directory to the server root, verify that its .bikey is inside the keys directory, and add the mod name to the server launch parameter string.

Issue 2: Server Skips Configured Map and Boots to Stratis Selection Screen

• Root Cause: A syntax error exists within the class Missions block inside server.cfg, or the template string does not match the file name located in the MPMissions folder.
• Actionable Fix: Open server.cfg in your text editor. Confirm that every open curly bracket has a corresponding closing bracket followed by a semicolon. Double-check that the string inside template = "filename.world"; matches the .pbo name character-for-character. If running on Linux, confirm that the physical file name in MPMissions is strictly lowercase.

Issue 3: Players Kicked Instantly with Signature Check Verification Error

• Root Cause: The server is running strict public key verification (v2 or v3) but lacks the matching .bikey file for the installed terrain mod, or client mod versions do not match server mod versions.
• Actionable Fix: Download the exact mod version matching the server build, extract the .bikey file located in the mod keys folder, and upload it to the server keys directory. Restart the server to reload key indexes.

Issue 4: Mission Fails to Automatically Load After Player Disconnects

• Root Cause: The persistent flag is either set to 0 or missing entirely from the top section of the server.cfg file.
• Actionable Fix: Open server.cfg, locate the global server settings block, and add or change the line to read persistent = 1;. This forces the engine to preserve mission states and world memory across player sessions without auto-resetting the mission cycle.

Frequently Asked Questions

How do I change the active map on an Arma server without performing a full restart?

You can switch maps dynamically while logged in as an administrator by typing #login YourAdminPassword into the global side-chat channel. Once logged in, type #missions to open the server mission selection menu, select the desired terrain and mission file from the listed MPMissions, and click Reassign or Reframe to load the new map instantly.

Why is my custom Steam Workshop map not appearing on the server?

Steam Workshop maps generally download as client-side mod packages rather than standalone mission files. To play a custom Workshop map on a server, you must install the map mod package on the server itself, add its .bikey file to the keys directory, add its parameter to the startup command, and then upload a .pbo mission file built specifically on that map's world name into MPMissions.

Where can I find the correct native world name for custom modded maps?

You can find the precise world name of a custom map by opening the mission in the Arma 3 Eden Editor on the map you wish to use, clicking File, and choosing Save As. The Eden Editor will automatically append the correct native world suffix (such as .Anizay or .Winthera) to the directory path created inside your local Documents/Arma 3/mpmissions folder.

What is the difference between server.cfg mission configuration and TAD control panel rotation?

TAD (Server Administration Tools) or host web control panels often generate their own server configurations dynamically. If you configure maps manually inside server.cfg while a host panel's mission rotation manager is enabled, the panel will overwrite your server.cfg edits upon boot. You must disable the control panel's automated mission manager or input your class Missions template settings directly through the web dashboard panel interface.

Optimize Your Arma 3 Community Operations Today

Configuring your Arma server with accurate map rotation configs, structured MPMissions deployments, and correct key signatures ensures continuous server uptime and uninterrupted operations for your unit. Apply these mission parameters to your server environment, verify your .rpt logs, and provide your players with seamless tactical transitions across custom terrains.