Configure missions & queue Arma 3

Configure missions & queue Arma 3

The multiplayer mission Arma 3 sets the card, game mode, slots players and server scripts. This guide covers the file mpmissions, map rotation, parameters server.cfg and the player experience (MOTD, password, queue).

mpmission files

Missions are files .pbo (or files in dev) placed in mpmissions/. The name without extension is used in the config: class Missions { class Altis { template = "Altis_Life.Altis"; ... }; };

Prerequisite

• Arma 3 server online, start
• Mods required by the installed mission, Workshop

Set Default Mission

1. Upload the mission file in mpmissions/
2. In server.cfgSection class Missions, define template
3. Set maxPlayers according to mission slots and offer
4. Optional: passwordAdmin for #login commands
5. Restart and check console loading

Mission rotation

To alternate several maps (Altis, Tanoa, Chernarus moddé):

• Use a rotation manager (server script, extension)
• Or vote map via mission (integrated framework life)
• Set minimum time per mission to avoid permanent changes

MODD & Presentation

• motd[] in server.cfg, rules, Teamspeak, website
• hostname, short name recognizable
• serverPassword for private sessions or temporary whitelist

Wait File & slots

When the server is full, Arma 3 manages a native tail. Increase slots cautiously: too many players on mission not optimized = lag server. Consider Headless Client to unload AI.

Mission Parameters (.param)

Some missions accept parameter files (duration, weather, respawn). Upload them next to the mission and refer via the interface or config.

Troubleshooting

• Mission not found, typo in template, PBO mispacked
• Black screen at join, mission error script, missing mod
• Slots insufficient, edit mission or maxPlayers

FAQ

Can I use a Zeus-only mission? Yes, configure roles in the mission editor and limit slots players tunedly.