Skip to content

Missions, Mods, Keys, and Admins

Upload the mission .pbo into mpmissions. Then add its template name to the mission cycle in server.cfg:

class Missions
{
class MainMission
{
template = "MyMission.Altis";
difficulty = "Regular";
};
};

The template excludes the .pbo extension and must match the filename exactly.

The server can download and update a modpack automatically from an Arma 3 Launcher export.

  1. Open the Arma 3 Launcher on your computer.
  2. Open the Mods section and load or select the required mod preset.
  3. Use the launcher’s option to export the mod list as HTML.
  4. Rename the exported file to modlist.html if it has another name.
  5. Stop the server.
  6. Upload modlist.html to the root game folder.
  7. Start the server and watch the console while it downloads the listed mods.

Keep modlist.html in the root game folder. When the server starts, it checks the list and fetches or updates the required Workshop mods automatically.

Players should import the same HTML preset into their Arma 3 Launcher so their loaded mods match the server.

  1. Update the preset in the Arma 3 Launcher.
  2. Export it again as HTML.
  3. Stop the server.
  4. Replace the existing modlist.html in the root game folder.
  5. Start the server and allow the mod update to finish.

Use the separate server-mod launch variable for mods that do not need to be loaded by players. Do not put a client-required mod there merely to hide it from the browser.

When signature checking is enabled, the required .bikey files must be available in the server’s root keys directory. Do not upload private .biprivatekey files.

Common security settings include:

verifySignatures = 2;
kickDuplicate = 1;

Headless clients need separately assigned ports and matching mod access. Contact support before adding ports or startup processes not exposed by your service.