weyne/dcs-retribution
1
0
Fork 0
mirror of https://github.com/dcs-retribution/dcs-retribution.git synced 2025-11-10 15:41:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Getting started (markdown)

Starfire13
2024-04-13 10:10:00 +10:00
parent 375a690baa
commit 279878a643
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Getting-started.md

@@ -25,6 +25,10 @@ This file will be modified whenever DCS Retribution is opened and the original w
If you don't, DCS will load the file before it is changed and DCS Retribution will not be able to retrieve mission progress.
If DCS performs an update after you have already launched Retribution, you should relaunch Retribution and DCS after the update is complete. This is because the update will have overwritten the MissionScripting.lua file that Retribution had modified.
Permanently modifying this file (e.g. editing it and setting it to read only) is not recommended as connecting to multiplayer servers with an unsanitised MissionScripting.lua is a potential security risk. This is why Retribution replaces the file with the original upon exit.
Experienced users can also disable the automatic modification of the `MissionScripting.lua`. This can be achieved by leaving the `DCS Installation Directory` preference empty.
**Warning**: If you leave the `DCS Installation Directory` empty, you have to manually edit the `MissionScripting.lua`. Otherwise DCS Retribution can not work properly. This is only recommended for expert users. A description on how to manually edit the file can be found in the [Dedicated-Server-Guide](https://github.com/dcs-retribution/dcs-retribution/wiki/Dedicated-Server-Guide#modding-missionscriptinglua).