From 4422cf3d4fc5fbef81b0f183713c547358f20daa Mon Sep 17 00:00:00 2001 From: Starfire13 <72491792+Starfire13@users.noreply.github.com> Date: Sat, 19 Jun 2021 07:08:40 +1000 Subject: [PATCH] Updated Dedicated Server Guide (markdown) --- Dedicated-Server-Guide.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/Dedicated-Server-Guide.md b/Dedicated-Server-Guide.md index ffb0eef..968363a 100644 --- a/Dedicated-Server-Guide.md +++ b/Dedicated-Server-Guide.md @@ -81,13 +81,10 @@ After installing dcs-liberation on a computer (let's call it the mission compute At one point, you'll want to *fly* a mission. When you press the *Take off* button in dcs-liberation, it'll generate a mission : `\dcs\missions\liberation_nextturn.miz`. -At the moment, it is mandatory to open the mission in the mission editor (on the mission computer), and save it. - -**If you skip this step, the mission will not be playable on a dedicated DCS server !** - - Now, you can simply copy the mission file to your server and run it. +Note: It was previously the case that multiplayer .miz turns had to be opened and saved in the mission editor prior to use. This is NO longer required. + ## Getting the result of the mission During the mission (at runtime, as we developers like to say), the state of the mission (destroyed units, captured bases) is written in the `state.json` file.