Setting Up Vanilla and Workshop Missions on Your Arma 3 Server

A fresh Arma 3 server is fun for about ten minutes, then everyone starts asking what mission you actually plan to run. Picking and rotating missions, whether they ship with the game or come from the Steam Workshop, is part of every Arma 3 admin's job. The process touches a few config lines and a couple of file uploads, but once you understand the shape of it, swapping missions becomes a routine task.

This guide walks through both vanilla and Workshop missions on a HolyHosting Arma 3 server, plus the errors that usually trip people up.

Adding Vanilla Missions

Vanilla missions are the easiest place to start, especially if you are training newcomers or testing the server before piling on custom content. Bohemia ships a long list of operations, and any of them can be loaded by referencing the file name and a difficulty value in your server config.

Open the panel and find the configuration files area in your panel sidebar.

Click the server configuration entry to expand its contents.

Scroll down to the Missions Cycle block. Inside it, every mission has its own `class MissionX` section with a `template` field for the mission file name and a difficulty value. Enter the mission you want to run.

Fill in the second mission slot the same way and keep the surrounding syntax intact. When the file looks right, hit Save at the top, then Restart Now to reload the server with the new rotation.

Adding a third (or fourth) mission

The default config only ships with two mission slots, but the cycle can hold as many as you want. Copy the entire `class MissionX { ... };` block, paste it underneath, and rename the class to something unique like `class Mission3`. Each block needs its own closing `};`, but do not touch the final brace at the very bottom of the file. That one closes the wider Missions Cycle.

Update the new block's `template` value with the mission you want, save the file, and restart.

Adding Workshop Missions

Custom missions from the Steam Workshop give you a much bigger pool to work with, but they need a small detour through your local Steam install before they reach the server. The short version: subscribe locally, rename the file, upload it through the panel, then point the Missions Cycle at it.

Preparing the file on your PC

Find the mission you want on the Arma 3 Workshop and click Subscribe so Steam downloads it.

Before leaving the page, grab the Workshop ID from the URL (the number after `?id=`). You will need it in a moment.

On your computer, open:

``` ...\Steam\steamapps\workshop\content\107410 ```

Inside that folder, look for the subfolder whose name matches the Workshop ID you saved. The mission lives there as a `.bin` file. Rename it to follow the `[name].[terrain].pbo` pattern. Before renaming, copy the original somewhere safe so you keep a clean backup in case you mistype the new name.

Uploading it to the server

Back on the panel, open your file manager or FTP client.

Enter your FTP password and log in.

Navigate into the `mpmissions` directory.

Click Upload in the top left and drop the renamed `.pbo` file into the window.

Wait for the transfer to finish. Once the file is in `mpmissions`, return to the Missions Cycle in your server configuration and add a new `class MissionX` entry whose `template` matches your new `.pbo` name (without the extension). Save, restart, and your Workshop mission is live.

Enhancing the Experience

Every Arma 3 mission carries its own objectives, and Workshop content stretches that variety further. Layering mods on top of a mission, whether for movement, AI, or new factions, is one of the quickest ways to turn a routine session into something memorable. Many Workshop missions explicitly require certain mods, so always skim the description before loading one onto the server. It saves a lot of guessing later.

Common Problems

Most mission issues come down to syntax. If the server refuses to start or boots into an empty rotation, open the config and check that every `class MissionX` has a unique name and a real mission file in its `template`. Stray semicolons, missing braces, and accidentally deleted spaces will all break the block.

For Workshop missions, double-check the FTP upload. The file has to be a proper `.pbo` inside `mpmissions`. A leftover `.bin` will not register, no matter how correct the config looks.

The other classic warning is the Contains Bad Link to a Static Object message that pops up in-game or in the console. It looks alarming, but most of the time the mission still runs and the warning can be dismissed. When it actually blocks the mission from loading, it usually means a required mod is missing. The Workshop description for the mission is the fastest place to confirm what else needs to be installed. Restarting after fixing the mod list typically clears it up.

If the mission still refuses to cooperate, contact support and they can dig into the logs with you.