mirror of
https://github.com/dcs-retribution/dcs-retribution.git
synced 2025-11-10 15:41:24 +00:00
Updated Dedicated Server Guide (markdown)
parent
0319e5b84e
commit
4422cf3d4f
@ -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 : `<saved games>\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.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user