From 47c5ee67d6ab37bf7df8be5f86c3b66bcd654713 Mon Sep 17 00:00:00 2001
From: Starfire13 <72491792+Starfire13@users.noreply.github.com>
Date: Sat, 13 Apr 2024 10:08:54 +1000
Subject: [PATCH] Updated Getting started (markdown)

---
 Getting-started.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Getting-started.md b/Getting-started.md
index f39bfb3..a7fe133 100644
--- a/Getting-started.md
+++ b/Getting-started.md
@@ -25,6 +25,10 @@ This file will be modified whenever DCS Liberation is opened and the original wi
 
 If you don't, DCS will load the file before it is changed and DCS Liberation will not be able to retrieve mission progress.
 
+If DCS performs an update after you have already launched Liberation, you should relaunch Liberation and DCS after the update is complete. This is because the update will have overwritten the MissionScripting.lua file that Liberation 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 Liberation 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 Liberation 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-liberation/dcs_liberation/wiki/Dedicated-Server-Guide#modding-missionscriptinglua).