Run DCS Liberation on a multiplayer or dedicated server: create client slots, host each .miz turn, collect debrief results and fix common failures.
Run DCS Liberation on one administrator’s PC, generate the next turn as a DCS .miz mission with client slots, and load that mission on the multiplayer server. After everyone flies, return the mission’s debrief data to the same Liberation campaign and accept the results before planning the next turn.
What actually runs on the multiplayer server?
The server runs an ordinary DCS World mission; it does not run the strategic campaign itself. Liberation remains the campaign controller, handling purchases, planning, frontline changes and generation of the next mission.
Only one person should control the live campaign save. Other pilots need DCS World, the mission’s terrain, their chosen aircraft module and any required mods, but they do not need their own working copy of the campaign. Our full Liberation generation and debrief workflow explains the underlying turn system.
| Arrangement | Where Liberation runs | How the mission is hosted | How results return |
|---|---|---|---|
| Listen server | Host pilot’s PC | The host selects the generated .miz in DCS multiplayer | Usually handled on the same PC |
| Dedicated server | Administrator’s PC, or the server if practical | The generated .miz is copied into the server’s mission list | Through the configured debrief connection or a manual result-file transfer |
How do you host each DCS Liberation turn?
The reliable method is to treat every Liberation turn as a newly generated multiplayer mission.
- Choose one campaign controller. Keep the authoritative Liberation save on one administrator’s PC and make a backup before each mission. Do not merge progress from several copies of the campaign.
- Plan the turn and create human slots. Mark every human-controlled aircraft as a multiplayer client in Liberation’s flight or roster setup. After generation, DCS should see those aircraft as Client slots rather than single-player Player aircraft or AI-only flights.
- Generate the mission. Use the
.mizproduced by the same campaign save and turn. Avoid editing unit names, scripts, triggers or tracked groups after generation; if changes are unavoidable, follow the safe procedure for editing a generated Liberation mission. - Load the exact mission on the server. For a listen server, open DCS multiplayer, create the server and select the generated mission. For a dedicated server, copy it to a mission folder accessible to the server account and add it to the active mission list. Our dedicated-server installation and network guide covers the server software, mission list, firewall and port configuration.
- Check dependencies before launch. Pilots need the terrain and flyable module used by their slot. The server and clients must use compatible DCS builds, while every required user mod must match across the machines that need it. Use our Liberation mod compatibility and installation guidance to avoid missing-unit and integrity problems.
- Start the turn and verify the slot list. Unpause the server if necessary, confirm that each pilot can occupy the assigned aircraft, and make sure the server has loaded the new turn rather than an older mission from its rotation.
- End the mission cleanly. Stop the mission only after the group has finished and DCS has had time to produce the debrief output. Keep the campaign save and server-generated result files until Liberation has accepted the turn successfully.
How do multiplayer results get back into Liberation?
Campaign progress is recorded only when the completed mission’s debrief data is processed by the authoritative Liberation campaign. Landing in DCS or stopping the server does not by itself advance the strategic turn.
With a listen server on the controller’s PC, Liberation can normally collect the result locally. A remote dedicated server writes its output under its own DCS Saved Games profile, so any Liberation-supplied hook or export component must be installed there, not merely on the administrator’s gaming PC.
If automatic reporting is not configured, retrieve the debrief or state output from the server and submit it through the matching Liberation debrief function. Names and locations vary between Liberation releases, so use the path shown by the installed version rather than copying instructions intended for a different build. Review losses, kills and objective changes, then accept the result once.
Why does a Liberation multiplayer campaign fail to progress?
Most failed sessions come from loading the wrong .miz, missing client slots or losing the server’s debrief output.
| Symptom | Likely cause | Fix |
|---|---|---|
| No aircraft are selectable | Flights were generated as AI or single-player aircraft | Return to Liberation, assign human clients and regenerate the turn |
| The campaign does not advance | The result was never returned or accepted | Recover the server’s debrief output and process it in the original campaign save |
| Losses or objectives are missing | The mission was edited, scripts were removed or the wrong turn was flown | Regenerate a clean mission and compare it with the server’s active file |
| Players cannot join or see units | DCS build, terrain, mod or network mismatch | Synchronise dependencies and check the server’s firewall and port configuration |
| The completed turn starts again | The old mission remains in an automatic rotation | Remove the completed mission and load only the newly generated turn |
Can Liberation run as an unattended 24/7 server?
A dedicated server can host a Liberation mission for an extended session, but the campaign is not fully unattended. An administrator must process the debrief, accept the strategic results, plan the next turn and replace the server’s mission.
For an organised group, the safest routine is one campaign controller, one active turn on the server and a backup taken before results are accepted. That prevents an automatic restart, stale mission file or duplicate debrief from corrupting campaign progress.