diff --git a/Core/Beacon/010-Beacons/RAD-010-Beacons.miz b/Core/Beacon/010-Beacons/RAD-010-Beacons.miz
index a49533a..9fcc14b 100644
Binary files a/Core/Beacon/010-Beacons/RAD-010-Beacons.miz and b/Core/Beacon/010-Beacons/RAD-010-Beacons.miz differ
diff --git a/Core/Menu/001-Menu-Mission/MEN-001-Menu-Mission.lua b/Core/Menu/001-Menu-Mission/MEN-001-Menu-Mission.lua
index 799b399..9989a3b 100644
--- a/Core/Menu/001-Menu-Mission/MEN-001-Menu-Mission.lua
+++ b/Core/Menu/001-Menu-Mission/MEN-001-Menu-Mission.lua
@@ -1,38 +1,38 @@
----
--- Author: kaltokri
--- Created: 16.03.2024
--- Contributors: -
--- Modified: -
---
--- # Documentation:
--- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
---
--- # Description:
---
--- Very simple example of the MENU_MISSION class.
--- We define a top menu entry, a sub menu entry and to menu commands.
--- Both commands call the same function, but with different arguments.
-
--- # Guide:
---
--- 1. Start the mission and enter as GAME MASTER.
--- 2. Wait for "loaded successfully" message.
--- 3. Open menu by pressing #
--- 4. Choose F10. Other...
--- 5. Select F1. Menu for all players...
--- 6. Select F1. Sub menu 1...
--- 7. Select Cmd1
--- 8. Repeat the same for Cmd2
-
-
--- Example function
-local function execMenuCmd( name )
-  MESSAGE:New( "Menu entry " .. name .. " selected", 25, "INFO" ):ToAll()
-end
-
-local MenuTop = MENU_MISSION:New( "Menu for all players" )
-local MenuSub1 = MENU_MISSION:New( "Sub menu 1", MenuTop )
-MENU_MISSION_COMMAND:New( "Cmd1", MenuSub1, execMenuCmd, "Cmd1" )
-MENU_MISSION_COMMAND:New( "Cmd2", MenuSub1, execMenuCmd, "Cmd2" )
-
-MESSAGE:New( "Moose Framework and Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
+---
+-- Author: kaltokri
+-- Created: 16.03.2024
+-- Contributors: -
+-- Modified: -
+--
+-- # Documentation:
+-- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
+--
+-- # Description:
+--
+-- Very simple example of the MENU_MISSION class.
+-- We define a top menu entry, a sub menu entry and to menu commands.
+-- Both commands call the same function, but with different arguments.
+
+-- # Guide:
+--
+-- 1. Start the mission and enter as GAME MASTER.
+-- 2. Wait for "loaded successfully" message.
+-- 3. Open menu by pressing #
+-- 4. Choose F10. Other...
+-- 5. Select F1. Menu for all players...
+-- 6. Select F1. Sub menu 1...
+-- 7. Select Cmd1
+-- 8. Repeat the same for Cmd2
+
+
+-- Example function
+local function execMenuCmd( name )
+  MESSAGE:New( "Menu entry " .. name .. " selected", 25, "INFO" ):ToAll()
+end
+
+local MenuTop = MENU_MISSION:New( "Menu for all players" )
+local MenuSub1 = MENU_MISSION:New( "Sub menu 1", MenuTop )
+MENU_MISSION_COMMAND:New( "Cmd1", MenuSub1, execMenuCmd, "Cmd1" )
+MENU_MISSION_COMMAND:New( "Cmd2", MenuSub1, execMenuCmd, "Cmd2" )
+
+MESSAGE:New( "Moose Framework and Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
diff --git a/Core/Menu/001-Menu-Mission/MEN-001-Menu-Mission.miz b/Core/Menu/001-Menu-Mission/MEN-001-Menu-Mission.miz
index d65ad88..8c7295e 100644
Binary files a/Core/Menu/001-Menu-Mission/MEN-001-Menu-Mission.miz and b/Core/Menu/001-Menu-Mission/MEN-001-Menu-Mission.miz differ
diff --git a/Core/Menu/002-Menu-Coalition/MEN-002-Menu-Coalition.lua b/Core/Menu/002-Menu-Coalition/MEN-002-Menu-Coalition.lua
index 8b93cbc..4d17204 100644
--- a/Core/Menu/002-Menu-Coalition/MEN-002-Menu-Coalition.lua
+++ b/Core/Menu/002-Menu-Coalition/MEN-002-Menu-Coalition.lua
@@ -1,51 +1,51 @@
----
--- Author: kaltokri
--- Created: 16.03.2024
--- Contributors: -
--- Modified: -
---
--- # Documentation:
--- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
---
--- # Description:
---
--- Very simple example of the MENU_COALITION class.
--- We define two top menu entries with the name "Mission phases". One for each coalition (red & blue).
--- Also we add a COMMAND for each menu, which calls the same function.
--- Note the different names of the menu items.
--- Also we add one entry at the top level for coalition.side.BLUE.
-
--- # Guide:
---
--- 1.  Start the mission and choose coalition Red.
--- 2.  Enter as GAME MASTER.
--- 3.  Wait for "loaded successfully" message.
--- 4.  Open menu by pressing #
--- 5.  Choose F10. Other...
--- 6.  Select F1. Mission phases...
--- 7.  Select F1. Start attack and see message.
--- 8.  Switch to coalition Blue.
--- 9.  Open menu by pressing #
--- 10. Choose F10. Other...
--- 11. Select F1. Mission phases...
--- 12. Select F1. Start counter attack and see message.
--- 13. Open menu by pressing # and select F10. Other...
--- 14. See entry F2. Start attack of Allies and select it.
--- 15. See the message.
-
-
--- Example function
-local function execMenuCmd( side )
-  MESSAGE:New( "The " .. side .. " side will start their attack phase!", 25, "INFO" ):ToAll()
-end
-
-local menuRed = MENU_COALITION:New( coalition.side.RED, "Mission phases" )
-MENU_COALITION_COMMAND:New( coalition.side.RED, "Start attack", menuRed , execMenuCmd, "red" )
-
-local menuBlue = MENU_COALITION:New( coalition.side.BLUE, "Mission phases" )
-MENU_COALITION_COMMAND:New( coalition.side.BLUE, "Start counter attack", menuBlue , execMenuCmd, "blue" )
-
--- This is an example on how to place a COMMAND at top level of the menu. The third parameter must be nil.
-MENU_COALITION_COMMAND:New( coalition.side.BLUE, "Start attack of Allies", nil , execMenuCmd, "purple" )
-
-MESSAGE:New( "Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
+---
+-- Author: kaltokri
+-- Created: 16.03.2024
+-- Contributors: -
+-- Modified: -
+--
+-- # Documentation:
+-- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
+--
+-- # Description:
+--
+-- Very simple example of the MENU_COALITION class.
+-- We define two top menu entries with the name "Mission phases". One for each coalition (red & blue).
+-- Also we add a COMMAND for each menu, which calls the same function.
+-- Note the different names of the menu items.
+-- Also we add one entry at the top level for coalition.side.BLUE.
+
+-- # Guide:
+--
+-- 1.  Start the mission and choose coalition Red.
+-- 2.  Enter as GAME MASTER.
+-- 3.  Wait for "loaded successfully" message.
+-- 4.  Open menu by pressing #
+-- 5.  Choose F10. Other...
+-- 6.  Select F1. Mission phases...
+-- 7.  Select F1. Start attack and see message.
+-- 8.  Switch to coalition Blue.
+-- 9.  Open menu by pressing #
+-- 10. Choose F10. Other...
+-- 11. Select F1. Mission phases...
+-- 12. Select F1. Start counter attack and see message.
+-- 13. Open menu by pressing # and select F10. Other...
+-- 14. See entry F2. Start attack of Allies and select it.
+-- 15. See the message.
+
+
+-- Example function
+local function execMenuCmd( side )
+  MESSAGE:New( "The " .. side .. " side will start their attack phase!", 25, "INFO" ):ToAll()
+end
+
+local menuRed = MENU_COALITION:New( coalition.side.RED, "Mission phases" )
+MENU_COALITION_COMMAND:New( coalition.side.RED, "Start attack", menuRed , execMenuCmd, "red" )
+
+local menuBlue = MENU_COALITION:New( coalition.side.BLUE, "Mission phases" )
+MENU_COALITION_COMMAND:New( coalition.side.BLUE, "Start counter attack", menuBlue , execMenuCmd, "blue" )
+
+-- This is an example on how to place a COMMAND at top level of the menu. The third parameter must be nil.
+MENU_COALITION_COMMAND:New( coalition.side.BLUE, "Start attack of Allies", nil , execMenuCmd, "purple" )
+
+MESSAGE:New( "Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
diff --git a/Core/Menu/002-Menu-Coalition/MEN-002-Menu-Coalition.miz b/Core/Menu/002-Menu-Coalition/MEN-002-Menu-Coalition.miz
index daecf33..2c5a226 100644
Binary files a/Core/Menu/002-Menu-Coalition/MEN-002-Menu-Coalition.miz and b/Core/Menu/002-Menu-Coalition/MEN-002-Menu-Coalition.miz differ
diff --git a/Core/Menu/003-Menu-Group/MEN-003-Menu-Group.lua b/Core/Menu/003-Menu-Group/MEN-003-Menu-Group.lua
index 492c736..849989e 100644
--- a/Core/Menu/003-Menu-Group/MEN-003-Menu-Group.lua
+++ b/Core/Menu/003-Menu-Group/MEN-003-Menu-Group.lua
@@ -1,66 +1,66 @@
----
--- Author: kaltokri
--- Created: 16.03.2024
--- Contributors: -
--- Modified: -
---
--- # Documentation:
--- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
---
--- # Description:
---
--- Very simple example of the MENU_GROUP.
--- We added two planes and give them different menu entries.
--- We need a timer to check regularly if someone entered the plane.
---
--- # Guide:
---
--- 1.  Start the mission.
--- 2.  Enter as Plane-1.
--- 3.  Wait for "loaded successfully" message and then 5 seconds more.
--- 4.  Open menu by pressing #
--- 5.  Choose F11. Parent Menu
--- 6.  Choose F10. Other...
--- 7.  Select F2. Menu for Plane-1...
--- 8.  Select F1. Accept CAS mission and see the message.
--- 9.  Switch to Plane-2 and wait 5 seconds.
--- 10. Open menu by pressing #
--- 11. Choose F11. Parent Menu
--- 12. Choose F10. Other...
--- 13. Select F2. Menu for Plane-2...
--- 12. Select F1. Accept BAI mission and see the message.
-
-
--- Example function
-local function PrintTheTextToBlue( text )
-  MESSAGE:New( text, 25, "INFO" ):ToBlue()
-end
-
--- Start a scheduler after a delay of 5 seconds and repeat it's execution very 5 seconds
-SCHEDULER:New( nil,
-  function()
-    -- Find both groups and save them in an object
-    local PlaneGroup1 = GROUP:FindByName( "Plane-1" )
-    local PlaneGroup2 = GROUP:FindByName( "Plane-2" )
-
-    -- Add menu for the first group
-    if PlaneGroup1 and PlaneGroup1:IsAlive() then
-      local MenuGroup1 = MENU_GROUP:New( PlaneGroup1, "Menu for Plane-1" )
-      MENU_GROUP_COMMAND:New( PlaneGroup1, "Accept CAS mission", MenuGroup1, PrintTheTextToBlue, "Plane-1 accepts the CAS mission" )
-      MESSAGE:New( "Menu added to Group1.", 1, "INFO" ):ToLog()
-    else
-      MESSAGE:New( "Group1 is not available.", 1, "INFO" ):ToLog()
-    end
-
-    -- Add menu for the second group
-    if PlaneGroup2 and PlaneGroup2:IsAlive() then
-      local MenuGroup2 = MENU_GROUP:New( PlaneGroup2, "Menu for Plane-2" )
-      MENU_GROUP_COMMAND:New( PlaneGroup2, "Accept BAI mission", MenuGroup2, PrintTheTextToBlue, "Plane-2 accepts the BAI mission" )
-      MESSAGE:New( "Menu added to Group2.", 1, "INFO" ):ToLog()
-    else
-      MESSAGE:New( "Group2 is not available.", 1, "INFO" ):ToLog()
-    end
-  end, {}, 5, 5 )
-
-MESSAGE:New( "Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
-MESSAGE:New( "The script will check every 5 seconds if group is available and add the menu.", 25, "INFO" ):ToAll():ToLog()
+---
+-- Author: kaltokri
+-- Created: 16.03.2024
+-- Contributors: -
+-- Modified: -
+--
+-- # Documentation:
+-- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
+--
+-- # Description:
+--
+-- Very simple example of the MENU_GROUP.
+-- We added two planes and give them different menu entries.
+-- We need a timer to check regularly if someone entered the plane.
+--
+-- # Guide:
+--
+-- 1.  Start the mission.
+-- 2.  Enter as Plane-1.
+-- 3.  Wait for "loaded successfully" message and then 5 seconds more.
+-- 4.  Open menu by pressing #
+-- 5.  Choose F11. Parent Menu
+-- 6.  Choose F10. Other...
+-- 7.  Select F2. Menu for Plane-1...
+-- 8.  Select F1. Accept CAS mission and see the message.
+-- 9.  Switch to Plane-2 and wait 5 seconds.
+-- 10. Open menu by pressing #
+-- 11. Choose F11. Parent Menu
+-- 12. Choose F10. Other...
+-- 13. Select F2. Menu for Plane-2...
+-- 12. Select F1. Accept BAI mission and see the message.
+
+
+-- Example function
+local function PrintTheTextToBlue( text )
+  MESSAGE:New( text, 25, "INFO" ):ToBlue()
+end
+
+-- Start a scheduler after a delay of 5 seconds and repeat it's execution very 5 seconds
+SCHEDULER:New( nil,
+  function()
+    -- Find both groups and save them in an object
+    local PlaneGroup1 = GROUP:FindByName( "Plane-1" )
+    local PlaneGroup2 = GROUP:FindByName( "Plane-2" )
+
+    -- Add menu for the first group
+    if PlaneGroup1 and PlaneGroup1:IsAlive() then
+      local MenuGroup1 = MENU_GROUP:New( PlaneGroup1, "Menu for Plane-1" )
+      MENU_GROUP_COMMAND:New( PlaneGroup1, "Accept CAS mission", MenuGroup1, PrintTheTextToBlue, "Plane-1 accepts the CAS mission" )
+      MESSAGE:New( "Menu added to Group1.", 1, "INFO" ):ToLog()
+    else
+      MESSAGE:New( "Group1 is not available.", 1, "INFO" ):ToLog()
+    end
+
+    -- Add menu for the second group
+    if PlaneGroup2 and PlaneGroup2:IsAlive() then
+      local MenuGroup2 = MENU_GROUP:New( PlaneGroup2, "Menu for Plane-2" )
+      MENU_GROUP_COMMAND:New( PlaneGroup2, "Accept BAI mission", MenuGroup2, PrintTheTextToBlue, "Plane-2 accepts the BAI mission" )
+      MESSAGE:New( "Menu added to Group2.", 1, "INFO" ):ToLog()
+    else
+      MESSAGE:New( "Group2 is not available.", 1, "INFO" ):ToLog()
+    end
+  end, {}, 5, 5 )
+
+MESSAGE:New( "Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
+MESSAGE:New( "The script will check every 5 seconds if group is available and add the menu.", 25, "INFO" ):ToAll():ToLog()
diff --git a/Core/Menu/003-Menu-Group/MEN-003-Menu-Group.miz b/Core/Menu/003-Menu-Group/MEN-003-Menu-Group.miz
index d3d863d..858b2c8 100644
Binary files a/Core/Menu/003-Menu-Group/MEN-003-Menu-Group.miz and b/Core/Menu/003-Menu-Group/MEN-003-Menu-Group.miz differ
diff --git a/Core/Menu/012-Menu-Coalition-add-and-remove/MEN-012-Menu-Coalition-add-and-remove.lua b/Core/Menu/012-Menu-Coalition-add-and-remove/MEN-012-Menu-Coalition-add-and-remove.lua
index 46efe58..c6430e7 100644
--- a/Core/Menu/012-Menu-Coalition-add-and-remove/MEN-012-Menu-Coalition-add-and-remove.lua
+++ b/Core/Menu/012-Menu-Coalition-add-and-remove/MEN-012-Menu-Coalition-add-and-remove.lua
@@ -1,75 +1,75 @@
----
--- Author: FlightControl
--- Created: 20.10.2018
--- Contributors: kaltokri
--- Modified: 17.03.2024
---
--- # Documentation:
--- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
---
--- # Description:
---
--- This demo creates a menu structure for the planes within the red coalition.
--- This time you can add and remove menu entries dynamic.
--- We use other menu entries to add and remove the menu entry "Show Status".
--- But this is only for simplification. You can change them in your mission code depending on the situation.
---
--- # Guide:
---
--- 1.  Start the mission and choose Plane 1.
--- 2.  Wait for "loaded successfully" message.
--- 3.  Open menu by pressing #
--- 4.  Choose F10. Other...
--- 5.  Select F1. Manage Menus...
--- 6.  Select F1. Add Status Menu.
--- 7.  Open menu by pressing # again.
--- 8.  Choose F10. Other...
--- 9.  Select new entry F3. Status of Planes... and F1. Show Status.
--- 10. See the message.
--- 11. Switxh to Plane 2
--- 12. Open menu by pressing #
--- 13. Choose F10. Other...
--- 14. The menu entry F2. Status of Planes... is available
---     NOTE: The order of the menu entries may vary!
--- 15. Select F2. Status of Planes... and F1. Show Status.
--- 16. See the message again.
--- 17. Open menu by pressing #
--- 18. Choose F10. Other...
--- 19. Select F1. Manage Menus...
--- 20. Choose F2. Remove Status Menu
--- 21. Open the menu and check the menu entry Status of Planes is gone.
--- 22. Switch back to Planre 1 and check that the menu entry is also removed.
-
--- Find and save client object
-local Plane1 = CLIENT:FindByName( "Plane 1" )
-local Plane2 = CLIENT:FindByName( "Plane 2" )
-
--- This would create a menu for the red coalition under the main DCS "Others" menu.
-local MenuCoalitionRed = MENU_COALITION:New( coalition.side.RED, "Manage Menus" )
-
--- We define the variable here, so we can use them in the functions, but the status is saved on mission script level.
-local MenuStatus -- Menu#MENU_COALITION
-
--- A simple function to show a status text.
-local function ShowStatus( StatusText, TextToCoalition )
-  MESSAGE:New( TextToCoalition, 15 ):ToRed()
-  Plane1:Message( StatusText, 15 )
-  Plane2:Message( StatusText, 15 )
-end
-
--- This function creates a menu entry for the red coalition to show a status message.
-local function AddStatusMenu()
-  MenuStatus = MENU_COALITION:New( coalition.side.RED, "Status of Planes" )
-  local MenuStatusShow = MENU_COALITION_COMMAND:New( coalition.side.RED, "Show Status", MenuStatus, ShowStatus, "Status of planes is ok!", "Message to Red Coalition" )
-end
-
--- This function removes the menu entry for the red coalition to show a status message.
-local function RemoveStatusMenu()
-  MenuStatus:Remove()
-end
-
--- Add two entries to add and remove another
-local MenuAdd    = MENU_COALITION_COMMAND:New( coalition.side.RED, "Add Status Menu", MenuCoalitionRed, AddStatusMenu )
-local MenuRemove = MENU_COALITION_COMMAND:New( coalition.side.RED, "Remove Status Menu", MenuCoalitionRed, RemoveStatusMenu )
-
-MESSAGE:New( "Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
+---
+-- Author: FlightControl
+-- Created: 20.10.2018
+-- Contributors: kaltokri
+-- Modified: 17.03.2024
+--
+-- # Documentation:
+-- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
+--
+-- # Description:
+--
+-- This demo creates a menu structure for the planes within the red coalition.
+-- This time you can add and remove menu entries dynamic.
+-- We use other menu entries to add and remove the menu entry "Show Status".
+-- But this is only for simplification. You can change them in your mission code depending on the situation.
+--
+-- # Guide:
+--
+-- 1.  Start the mission and choose Plane 1.
+-- 2.  Wait for "loaded successfully" message.
+-- 3.  Open menu by pressing #
+-- 4.  Choose F10. Other...
+-- 5.  Select F1. Manage Menus...
+-- 6.  Select F1. Add Status Menu.
+-- 7.  Open menu by pressing # again.
+-- 8.  Choose F10. Other...
+-- 9.  Select new entry F3. Status of Planes... and F1. Show Status.
+-- 10. See the message.
+-- 11. Switxh to Plane 2
+-- 12. Open menu by pressing #
+-- 13. Choose F10. Other...
+-- 14. The menu entry F2. Status of Planes... is available
+--     NOTE: The order of the menu entries may vary!
+-- 15. Select F2. Status of Planes... and F1. Show Status.
+-- 16. See the message again.
+-- 17. Open menu by pressing #
+-- 18. Choose F10. Other...
+-- 19. Select F1. Manage Menus...
+-- 20. Choose F2. Remove Status Menu
+-- 21. Open the menu and check the menu entry Status of Planes is gone.
+-- 22. Switch back to Planre 1 and check that the menu entry is also removed.
+
+-- Find and save client object
+local Plane1 = CLIENT:FindByName( "Plane 1" )
+local Plane2 = CLIENT:FindByName( "Plane 2" )
+
+-- This would create a menu for the red coalition under the main DCS "Others" menu.
+local MenuCoalitionRed = MENU_COALITION:New( coalition.side.RED, "Manage Menus" )
+
+-- We define the variable here, so we can use them in the functions, but the status is saved on mission script level.
+local MenuStatus -- Menu#MENU_COALITION
+
+-- A simple function to show a status text.
+local function ShowStatus( StatusText, TextToCoalition )
+  MESSAGE:New( TextToCoalition, 15 ):ToRed()
+  Plane1:Message( StatusText, 15 )
+  Plane2:Message( StatusText, 15 )
+end
+
+-- This function creates a menu entry for the red coalition to show a status message.
+local function AddStatusMenu()
+  MenuStatus = MENU_COALITION:New( coalition.side.RED, "Status of Planes" )
+  local MenuStatusShow = MENU_COALITION_COMMAND:New( coalition.side.RED, "Show Status", MenuStatus, ShowStatus, "Status of planes is ok!", "Message to Red Coalition" )
+end
+
+-- This function removes the menu entry for the red coalition to show a status message.
+local function RemoveStatusMenu()
+  MenuStatus:Remove()
+end
+
+-- Add two entries to add and remove another
+local MenuAdd    = MENU_COALITION_COMMAND:New( coalition.side.RED, "Add Status Menu", MenuCoalitionRed, AddStatusMenu )
+local MenuRemove = MENU_COALITION_COMMAND:New( coalition.side.RED, "Remove Status Menu", MenuCoalitionRed, RemoveStatusMenu )
+
+MESSAGE:New( "Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
diff --git a/Core/Menu/012-Menu-Coalition-add-and-remove/MEN-012-Menu-Coalition-add-and-remove.miz b/Core/Menu/012-Menu-Coalition-add-and-remove/MEN-012-Menu-Coalition-add-and-remove.miz
index f8e63c6..c8d678d 100644
Binary files a/Core/Menu/012-Menu-Coalition-add-and-remove/MEN-012-Menu-Coalition-add-and-remove.miz and b/Core/Menu/012-Menu-Coalition-add-and-remove/MEN-012-Menu-Coalition-add-and-remove.miz differ
diff --git a/Core/Menu/013-Menu-Group-add-and-remove/MEN-013-Menu-Group-add-and-remove.lua b/Core/Menu/013-Menu-Group-add-and-remove/MEN-013-Menu-Group-add-and-remove.lua
index 7f5343b..5d147ef 100644
--- a/Core/Menu/013-Menu-Group-add-and-remove/MEN-013-Menu-Group-add-and-remove.lua
+++ b/Core/Menu/013-Menu-Group-add-and-remove/MEN-013-Menu-Group-add-and-remove.lua
@@ -1,71 +1,71 @@
----
--- Author: FlightControl
--- Created: 20.10.2018
--- Contributors: kaltokri
--- Modified: 18.03.2024
---
--- # Documentation:
--- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
--- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Scheduler.html
---
--- # Description:
---
--- This demo creates a menu structure for the two groups of planes.
--- Each group will receive a different menu structure.
---
--- # Guide:
---
--- To test this mission join the planes, look at the radio menus (option F10).
--- Then switch planes and check if the menu is still there.
--- And play with the Add and Remove menu options.
--- NOTE: That will only work on multiplayer after the DCS groups bug is solved.
-
-
--- We define the variable here, so we can use it in the functions, but the status is saved on mission script level.
-local MenuStatus = {}
-
--- A simple function to show a status text.
-local function ShowStatus( PlaneGroup, StatusText, TextToCoalition )
-  MESSAGE:New( TextToCoalition, 15 ):ToRed()
-  PlaneGroup:Message( StatusText, 15 )
-end
-
---- This function creates a menu entry for the red coalition to show a status message.
--- @param Wrapper.Group#GROUP MenuGroup
-local function AddStatusMenu( MenuGroup )
-  local MenuGroupName = MenuGroup:GetName()
-  -- This would create a menu for the red coalition under the MenuCoalitionRed menu object.
-  MenuStatus[MenuGroupName] = MENU_GROUP:New( MenuGroup, "Status for Planes" )
-  MENU_GROUP_COMMAND:New( MenuGroup, "Show Status", MenuStatus[MenuGroupName], ShowStatus, MenuGroup, "Status of planes is ok!", "Message to Red Coalition" )
-end
-
--- This function removes the menu entry for the red coalition to show a status message.
-local function RemoveStatusMenu( MenuGroup )
-  local MenuGroupName = MenuGroup:GetName()
-  MenuStatus[MenuGroupName]:Remove()
-end
-
--- Start a scheduler after a delay of 5 seconds and repeat it's execution very 5 seconds
-SCHEDULER:New( nil,
-  function()
-    -- Find both groups and save them in an object.
-    local PlaneGroup1 = GROUP:FindByName( "Plane 1" )
-    local PlaneGroup2 = GROUP:FindByName( "Plane 2" )
-
-    -- Add menu for the first group
-    if PlaneGroup1 and PlaneGroup1:IsAlive() then
-      local MenuGroup1 = MENU_GROUP:New( PlaneGroup1, "Manage Menus" )
-      MENU_GROUP_COMMAND:New( PlaneGroup1, "Add Status Menu Plane 1", MenuGroup1, AddStatusMenu, PlaneGroup1 )
-      MENU_GROUP_COMMAND:New( PlaneGroup1, "Remove Status Menu Plane 1", MenuGroup1, RemoveStatusMenu, PlaneGroup1 )
-    end
-
-    -- Add menu for the second group
-    if PlaneGroup2 and PlaneGroup2:IsAlive() then
-      local MenuGroup2 = MENU_GROUP:New( PlaneGroup2, "Manage Menus" )
-      MENU_GROUP_COMMAND:New( PlaneGroup2, "Add Status Menu Plane 2", MenuGroup2, AddStatusMenu, PlaneGroup2 )
-      MENU_GROUP_COMMAND:New( PlaneGroup2, "Remove Status Menu Plane 2", MenuGroup2, RemoveStatusMenu, PlaneGroup2 )
-    end
-  end, {}, 5, 5 )
-
-MESSAGE:New( "Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
-MESSAGE:New( "The script will check every 5 seconds if group is available and add the menu.", 25, "INFO" ):ToAll():ToLog()
+---
+-- Author: FlightControl
+-- Created: 20.10.2018
+-- Contributors: kaltokri
+-- Modified: 18.03.2024
+--
+-- # Documentation:
+-- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Menu.html
+-- https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Scheduler.html
+--
+-- # Description:
+--
+-- This demo creates a menu structure for the two groups of planes.
+-- Each group will receive a different menu structure.
+--
+-- # Guide:
+--
+-- To test this mission join the planes, look at the radio menus (option F10).
+-- Then switch planes and check if the menu is still there.
+-- And play with the Add and Remove menu options.
+-- NOTE: That will only work on multiplayer after the DCS groups bug is solved.
+
+
+-- We define the variable here, so we can use it in the functions, but the status is saved on mission script level.
+local MenuStatus = {}
+
+-- A simple function to show a status text.
+local function ShowStatus( PlaneGroup, StatusText, TextToCoalition )
+  MESSAGE:New( TextToCoalition, 15 ):ToRed()
+  PlaneGroup:Message( StatusText, 15 )
+end
+
+--- This function creates a menu entry for the red coalition to show a status message.
+-- @param Wrapper.Group#GROUP MenuGroup
+local function AddStatusMenu( MenuGroup )
+  local MenuGroupName = MenuGroup:GetName()
+  -- This would create a menu for the red coalition under the MenuCoalitionRed menu object.
+  MenuStatus[MenuGroupName] = MENU_GROUP:New( MenuGroup, "Status for Planes" )
+  MENU_GROUP_COMMAND:New( MenuGroup, "Show Status", MenuStatus[MenuGroupName], ShowStatus, MenuGroup, "Status of planes is ok!", "Message to Red Coalition" )
+end
+
+-- This function removes the menu entry for the red coalition to show a status message.
+local function RemoveStatusMenu( MenuGroup )
+  local MenuGroupName = MenuGroup:GetName()
+  MenuStatus[MenuGroupName]:Remove()
+end
+
+-- Start a scheduler after a delay of 5 seconds and repeat it's execution very 5 seconds
+SCHEDULER:New( nil,
+  function()
+    -- Find both groups and save them in an object.
+    local PlaneGroup1 = GROUP:FindByName( "Plane 1" )
+    local PlaneGroup2 = GROUP:FindByName( "Plane 2" )
+
+    -- Add menu for the first group
+    if PlaneGroup1 and PlaneGroup1:IsAlive() then
+      local MenuGroup1 = MENU_GROUP:New( PlaneGroup1, "Manage Menus" )
+      MENU_GROUP_COMMAND:New( PlaneGroup1, "Add Status Menu Plane 1", MenuGroup1, AddStatusMenu, PlaneGroup1 )
+      MENU_GROUP_COMMAND:New( PlaneGroup1, "Remove Status Menu Plane 1", MenuGroup1, RemoveStatusMenu, PlaneGroup1 )
+    end
+
+    -- Add menu for the second group
+    if PlaneGroup2 and PlaneGroup2:IsAlive() then
+      local MenuGroup2 = MENU_GROUP:New( PlaneGroup2, "Manage Menus" )
+      MENU_GROUP_COMMAND:New( PlaneGroup2, "Add Status Menu Plane 2", MenuGroup2, AddStatusMenu, PlaneGroup2 )
+      MENU_GROUP_COMMAND:New( PlaneGroup2, "Remove Status Menu Plane 2", MenuGroup2, RemoveStatusMenu, PlaneGroup2 )
+    end
+  end, {}, 5, 5 )
+
+MESSAGE:New( "Mission script loaded successfully", 25, "INFO" ):ToAll():ToLog()
+MESSAGE:New( "The script will check every 5 seconds if group is available and add the menu.", 25, "INFO" ):ToAll():ToLog()
diff --git a/Core/Menu/013-Menu-Group-add-and-remove/MEN-013-Menu-Group-add-and-remove.miz b/Core/Menu/013-Menu-Group-add-and-remove/MEN-013-Menu-Group-add-and-remove.miz
index 0668964..a9486d2 100644
Binary files a/Core/Menu/013-Menu-Group-add-and-remove/MEN-013-Menu-Group-add-and-remove.miz and b/Core/Menu/013-Menu-Group-add-and-remove/MEN-013-Menu-Group-add-and-remove.miz differ
diff --git a/Core/SpawnStatic/010-Simple-Spawning/SPS-010-Simple-Spawning.miz b/Core/SpawnStatic/010-Simple-Spawning/SPS-010-Simple-Spawning.miz
index fdf64a5..fa182f8 100644
Binary files a/Core/SpawnStatic/010-Simple-Spawning/SPS-010-Simple-Spawning.miz and b/Core/SpawnStatic/010-Simple-Spawning/SPS-010-Simple-Spawning.miz differ
diff --git a/Core/SpawnStatic/020-Mark-target-with-containers/SPS-020-Mark-target-with-containers.miz b/Core/SpawnStatic/020-Mark-target-with-containers/SPS-020-Mark-target-with-containers.miz
index bcb91a1..26f2c3d 100644
Binary files a/Core/SpawnStatic/020-Mark-target-with-containers/SPS-020-Mark-target-with-containers.miz and b/Core/SpawnStatic/020-Mark-target-with-containers/SPS-020-Mark-target-with-containers.miz differ
diff --git a/Core/SpawnStatic/050-Spawn-FARPs/SPS-050-Spawn-FARPs.miz b/Core/SpawnStatic/050-Spawn-FARPs/SPS-050-Spawn-FARPs.miz
index 5e44bff..4cce245 100644
Binary files a/Core/SpawnStatic/050-Spawn-FARPs/SPS-050-Spawn-FARPs.miz and b/Core/SpawnStatic/050-Spawn-FARPs/SPS-050-Spawn-FARPs.miz differ
diff --git a/Core/Zone/100-Normal-Zone/ZON-100-Normal-Zone.miz b/Core/Zone/100-Normal-Zone/ZON-100-Normal-Zone.miz
index 836a32d..5dc80a9 100644
Binary files a/Core/Zone/100-Normal-Zone/ZON-100-Normal-Zone.miz and b/Core/Zone/100-Normal-Zone/ZON-100-Normal-Zone.miz differ
diff --git a/Core/Zone/101-Normal-Zone-Random-Point/ZON-101-Normal-Zone-Random-Point.miz b/Core/Zone/101-Normal-Zone-Random-Point/ZON-101-Normal-Zone-Random-Point.miz
index 69a1651..84732b8 100644
Binary files a/Core/Zone/101-Normal-Zone-Random-Point/ZON-101-Normal-Zone-Random-Point.miz and b/Core/Zone/101-Normal-Zone-Random-Point/ZON-101-Normal-Zone-Random-Point.miz differ
diff --git a/Core/Zone/102-Normal-Zone-Boundary/ZON-102-Normal-Zone-Boundary.miz b/Core/Zone/102-Normal-Zone-Boundary/ZON-102-Normal-Zone-Boundary.miz
index d7484b1..859e1c2 100644
Binary files a/Core/Zone/102-Normal-Zone-Boundary/ZON-102-Normal-Zone-Boundary.miz and b/Core/Zone/102-Normal-Zone-Boundary/ZON-102-Normal-Zone-Boundary.miz differ
diff --git a/Core/Zone/103-Test-if-GROUP-object-is-in-ZONE/ZON-103-Test-if-GROUP-object-is-in-ZONE.miz b/Core/Zone/103-Test-if-GROUP-object-is-in-ZONE/ZON-103-Test-if-GROUP-object-is-in-ZONE.miz
index d45141d..a853d06 100644
Binary files a/Core/Zone/103-Test-if-GROUP-object-is-in-ZONE/ZON-103-Test-if-GROUP-object-is-in-ZONE.miz and b/Core/Zone/103-Test-if-GROUP-object-is-in-ZONE/ZON-103-Test-if-GROUP-object-is-in-ZONE.miz differ
diff --git a/Core/Zone/104-Test-if-GROUP-SET-is-in-ZONE/ZON-104-Test-if-GROUP-SET-is-in-ZONE.miz b/Core/Zone/104-Test-if-GROUP-SET-is-in-ZONE/ZON-104-Test-if-GROUP-SET-is-in-ZONE.miz
index 5c7f791..0137ad7 100644
Binary files a/Core/Zone/104-Test-if-GROUP-SET-is-in-ZONE/ZON-104-Test-if-GROUP-SET-is-in-ZONE.miz and b/Core/Zone/104-Test-if-GROUP-SET-is-in-ZONE/ZON-104-Test-if-GROUP-SET-is-in-ZONE.miz differ
diff --git a/Core/Zone/110-ZONE-declared-in-ME/ZON-110-ZONE-declared-in-ME.miz b/Core/Zone/110-ZONE-declared-in-ME/ZON-110-ZONE-declared-in-ME.miz
index d4fe99c..1e9e8fc 100644
Binary files a/Core/Zone/110-ZONE-declared-in-ME/ZON-110-ZONE-declared-in-ME.miz and b/Core/Zone/110-ZONE-declared-in-ME/ZON-110-ZONE-declared-in-ME.miz differ
diff --git a/Core/Zone/190-Return-SCENERY-objects-in-Zone/ZON-190-Return-SCENERY-objects-in-Zone.miz b/Core/Zone/190-Return-SCENERY-objects-in-Zone/ZON-190-Return-SCENERY-objects-in-Zone.miz
index 2484c0a..3b772d5 100644
Binary files a/Core/Zone/190-Return-SCENERY-objects-in-Zone/ZON-190-Return-SCENERY-objects-in-Zone.miz and b/Core/Zone/190-Return-SCENERY-objects-in-Zone/ZON-190-Return-SCENERY-objects-in-Zone.miz differ
diff --git a/Core/Zone/200-Group-Zone/ZON-200-Group-Zone.miz b/Core/Zone/200-Group-Zone/ZON-200-Group-Zone.miz
index 95791fb..03984a5 100644
Binary files a/Core/Zone/200-Group-Zone/ZON-200-Group-Zone.miz and b/Core/Zone/200-Group-Zone/ZON-200-Group-Zone.miz differ
diff --git a/Core/Zone/201-Group-Zone-Random-Point/ZON-201-Group-Zone-Random-Point.miz b/Core/Zone/201-Group-Zone-Random-Point/ZON-201-Group-Zone-Random-Point.miz
index 6349117..fc28a1b 100644
Binary files a/Core/Zone/201-Group-Zone-Random-Point/ZON-201-Group-Zone-Random-Point.miz and b/Core/Zone/201-Group-Zone-Random-Point/ZON-201-Group-Zone-Random-Point.miz differ
diff --git a/Core/Zone/300-Unit-Zone/ZON-300-Unit-Zone.miz b/Core/Zone/300-Unit-Zone/ZON-300-Unit-Zone.miz
index 89c28f7..e1072ca 100644
Binary files a/Core/Zone/300-Unit-Zone/ZON-300-Unit-Zone.miz and b/Core/Zone/300-Unit-Zone/ZON-300-Unit-Zone.miz differ
diff --git a/Core/Zone/301-Unit-Zone-Random-Point/ZON-301-Unit-Zone-Random-Point.miz b/Core/Zone/301-Unit-Zone-Random-Point/ZON-301-Unit-Zone-Random-Point.miz
index 4b3a31d..0ec8be0 100644
Binary files a/Core/Zone/301-Unit-Zone-Random-Point/ZON-301-Unit-Zone-Random-Point.miz and b/Core/Zone/301-Unit-Zone-Random-Point/ZON-301-Unit-Zone-Random-Point.miz differ
diff --git a/Core/Zone/400-Radius-Zone/ZON-400-Radius-Zone.miz b/Core/Zone/400-Radius-Zone/ZON-400-Radius-Zone.miz
index 51484a8..d9446dd 100644
Binary files a/Core/Zone/400-Radius-Zone/ZON-400-Radius-Zone.miz and b/Core/Zone/400-Radius-Zone/ZON-400-Radius-Zone.miz differ
diff --git a/Core/Zone/401-Radius-Zone-Random-Point/ZON-401-Radius-Zone-Random-Point.miz b/Core/Zone/401-Radius-Zone-Random-Point/ZON-401-Radius-Zone-Random-Point.miz
index d1ed5a6..f3cc0aa 100644
Binary files a/Core/Zone/401-Radius-Zone-Random-Point/ZON-401-Radius-Zone-Random-Point.miz and b/Core/Zone/401-Radius-Zone-Random-Point/ZON-401-Radius-Zone-Random-Point.miz differ
diff --git a/Core/Zone/500-Polygon-Zone/ZON-500-Polygon-Zone.miz b/Core/Zone/500-Polygon-Zone/ZON-500-Polygon-Zone.miz
index 6cc5605..6d0b37d 100644
Binary files a/Core/Zone/500-Polygon-Zone/ZON-500-Polygon-Zone.miz and b/Core/Zone/500-Polygon-Zone/ZON-500-Polygon-Zone.miz differ
diff --git a/Core/Zone/501-Polygon-Zone-Random-Point/ZON-501-Polygon-Zone-Random-Point.miz b/Core/Zone/501-Polygon-Zone-Random-Point/ZON-501-Polygon-Zone-Random-Point.miz
index 5cf0114..bc130fe 100644
Binary files a/Core/Zone/501-Polygon-Zone-Random-Point/ZON-501-Polygon-Zone-Random-Point.miz and b/Core/Zone/501-Polygon-Zone-Random-Point/ZON-501-Polygon-Zone-Random-Point.miz differ
diff --git a/Core/Zone/502-Polygon-Zone-Boundary/ZON-502-Polygon-Zone-Boundary.miz b/Core/Zone/502-Polygon-Zone-Boundary/ZON-502-Polygon-Zone-Boundary.miz
index b5e0a9f..65dc0c8 100644
Binary files a/Core/Zone/502-Polygon-Zone-Boundary/ZON-502-Polygon-Zone-Boundary.miz and b/Core/Zone/502-Polygon-Zone-Boundary/ZON-502-Polygon-Zone-Boundary.miz differ
diff --git a/Core/Zone/510-ZONE_POLYGON-declared-in-ME/ZON-510-ZONE_POLYGON-declared-in-ME.miz b/Core/Zone/510-ZONE_POLYGON-declared-in-ME/ZON-510-ZONE_POLYGON-declared-in-ME.miz
index f3ed5f5..3456bae 100644
Binary files a/Core/Zone/510-ZONE_POLYGON-declared-in-ME/ZON-510-ZONE_POLYGON-declared-in-ME.miz and b/Core/Zone/510-ZONE_POLYGON-declared-in-ME/ZON-510-ZONE_POLYGON-declared-in-ME.miz differ
diff --git a/Core/Zone/520-Draw-Zones-and-Shapes/ZON-520-Draw-Zones-and-Shapes.miz b/Core/Zone/520-Draw-Zones-and-Shapes/ZON-520-Draw-Zones-and-Shapes.miz
index b6770ff..676d986 100644
Binary files a/Core/Zone/520-Draw-Zones-and-Shapes/ZON-520-Draw-Zones-and-Shapes.miz and b/Core/Zone/520-Draw-Zones-and-Shapes/ZON-520-Draw-Zones-and-Shapes.miz differ
diff --git a/Functional/FOX/100-Simple/FOX-100-Simple.miz b/Functional/FOX/100-Simple/FOX-100-Simple.miz
index 39d11c9..9baab81 100644
Binary files a/Functional/FOX/100-Simple/FOX-100-Simple.miz and b/Functional/FOX/100-Simple/FOX-100-Simple.miz differ
diff --git a/Functional/FOX/101-LaunchZone/FOX-101-LaunchZone.miz b/Functional/FOX/101-LaunchZone/FOX-101-LaunchZone.miz
index 9f4c60c..1a712cc 100644
Binary files a/Functional/FOX/101-LaunchZone/FOX-101-LaunchZone.miz and b/Functional/FOX/101-LaunchZone/FOX-101-LaunchZone.miz differ
diff --git a/Functional/FOX/102-ProtectedGroup/FOX-102-ProtectedGroup.miz b/Functional/FOX/102-ProtectedGroup/FOX-102-ProtectedGroup.miz
index 23281ca..88ae36a 100644
Binary files a/Functional/FOX/102-ProtectedGroup/FOX-102-ProtectedGroup.miz and b/Functional/FOX/102-ProtectedGroup/FOX-102-ProtectedGroup.miz differ
diff --git a/Functional/FOX/103-SafeZone/ZON-103-SafeZone.miz b/Functional/FOX/103-SafeZone/ZON-103-SafeZone.miz
index c1e603c..6588da6 100644
Binary files a/Functional/FOX/103-SafeZone/ZON-103-SafeZone.miz and b/Functional/FOX/103-SafeZone/ZON-103-SafeZone.miz differ
diff --git a/Other/000-Template/000-Template.miz b/Other/000-Template/000-Template.miz
index cdca2ba..3b2fe47 100644
Binary files a/Other/000-Template/000-Template.miz and b/Other/000-Template/000-Template.miz differ
diff --git a/Sound/MSRS/001-Play-internal-Sound-file/MSRS-001-Play-internal-Sound-file.miz b/Sound/MSRS/001-Play-internal-Sound-file/MSRS-001-Play-internal-Sound-file.miz
index 16d9550..968a4b8 100644
Binary files a/Sound/MSRS/001-Play-internal-Sound-file/MSRS-001-Play-internal-Sound-file.miz and b/Sound/MSRS/001-Play-internal-Sound-file/MSRS-001-Play-internal-Sound-file.miz differ
diff --git a/Sound/MSRS/002-Play-external-Sound-file/MSRS-002-Play-external-Sound-file.miz b/Sound/MSRS/002-Play-external-Sound-file/MSRS-002-Play-external-Sound-file.miz
index 452a669..5146ac6 100644
Binary files a/Sound/MSRS/002-Play-external-Sound-file/MSRS-002-Play-external-Sound-file.miz and b/Sound/MSRS/002-Play-external-Sound-file/MSRS-002-Play-external-Sound-file.miz differ
diff --git a/Sound/MSRS/003-PlayTextFile/MSRS-003-PlayTextFile.miz b/Sound/MSRS/003-PlayTextFile/MSRS-003-PlayTextFile.miz
index d6673dc..06d5ba1 100644
Binary files a/Sound/MSRS/003-PlayTextFile/MSRS-003-PlayTextFile.miz and b/Sound/MSRS/003-PlayTextFile/MSRS-003-PlayTextFile.miz differ
diff --git a/Sound/MSRS/010-Windows-TTS-via-config-file/MSRS-010-Windows-TTS-via-config-file.miz b/Sound/MSRS/010-Windows-TTS-via-config-file/MSRS-010-Windows-TTS-via-config-file.miz
index 0dca605..bf7b849 100644
Binary files a/Sound/MSRS/010-Windows-TTS-via-config-file/MSRS-010-Windows-TTS-via-config-file.miz and b/Sound/MSRS/010-Windows-TTS-via-config-file/MSRS-010-Windows-TTS-via-config-file.miz differ
diff --git a/Sound/Radio/000-Transmission-from-Static/RAD-000-Transmission-from-Static.miz b/Sound/Radio/000-Transmission-from-Static/RAD-000-Transmission-from-Static.miz
index 741e75f..168627f 100644
Binary files a/Sound/Radio/000-Transmission-from-Static/RAD-000-Transmission-from-Static.miz and b/Sound/Radio/000-Transmission-from-Static/RAD-000-Transmission-from-Static.miz differ
diff --git a/Sound/Radio/001-Transmission-from-UNIT-or-GROUP/RAD-001-Transmission-from-UNIT-or-GROUP.miz b/Sound/Radio/001-Transmission-from-UNIT-or-GROUP/RAD-001-Transmission-from-UNIT-or-GROUP.miz
index c797a68..0dc640e 100644
Binary files a/Sound/Radio/001-Transmission-from-UNIT-or-GROUP/RAD-001-Transmission-from-UNIT-or-GROUP.miz and b/Sound/Radio/001-Transmission-from-UNIT-or-GROUP/RAD-001-Transmission-from-UNIT-or-GROUP.miz differ
diff --git a/Sound/Radio/002-Transmission-Tips-and-Tricks/RAD-002-Transmission-Tips-and-Tricks.miz b/Sound/Radio/002-Transmission-Tips-and-Tricks/RAD-002-Transmission-Tips-and-Tricks.miz
index dae27fb..d6d76ab 100644
Binary files a/Sound/Radio/002-Transmission-Tips-and-Tricks/RAD-002-Transmission-Tips-and-Tricks.miz and b/Sound/Radio/002-Transmission-Tips-and-Tricks/RAD-002-Transmission-Tips-and-Tricks.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Caucasus.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Caucasus.miz
index cab91ed..bbe93d9 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Caucasus.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Caucasus.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Falklands.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Falklands.miz
index 9625d14..c20340f 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Falklands.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Falklands.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-MarianaIslands.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-MarianaIslands.miz
index d7b62ae..ecfd0c1 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-MarianaIslands.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-MarianaIslands.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Nevada.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Nevada.miz
index 39c7bbd..c9678fb 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Nevada.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Nevada.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Normandy.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Normandy.miz
index 0ef767b..f13dba5 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Normandy.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Normandy.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-PersianGulf.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-PersianGulf.miz
index 05cc1be..0ca9f48 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-PersianGulf.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-PersianGulf.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Sinai.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Sinai.miz
index bc42e49..f2dd110 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Sinai.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Sinai.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Syria.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Syria.miz
index a490086..97c4bf0 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Syria.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-Syria.miz differ
diff --git a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-TheChannel.miz b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-TheChannel.miz
index 5464175..f521641 100644
Binary files a/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-TheChannel.miz and b/Wrapper/Airbase/900-Airbase-data/AFB-900-Airbase-data-TheChannel.miz differ
diff --git a/Wrapper/Group/100-IsAlive/GRP-100-IsAlive.miz b/Wrapper/Group/100-IsAlive/GRP-100-IsAlive.miz
index 6fcfbc6..558a48a 100644
Binary files a/Wrapper/Group/100-IsAlive/GRP-100-IsAlive.miz and b/Wrapper/Group/100-IsAlive/GRP-100-IsAlive.miz differ
diff --git a/Wrapper/Group/101-TaskAttackUnit/GRP-101-TaskAttackUnit.miz b/Wrapper/Group/101-TaskAttackUnit/GRP-101-TaskAttackUnit.miz
index fdf7690..d8f63ee 100644
Binary files a/Wrapper/Group/101-TaskAttackUnit/GRP-101-TaskAttackUnit.miz and b/Wrapper/Group/101-TaskAttackUnit/GRP-101-TaskAttackUnit.miz differ
diff --git a/Wrapper/Group/200-Follow-Group/GRP-200-Follow-Group.miz b/Wrapper/Group/200-Follow-Group/GRP-200-Follow-Group.miz
index 07d6bbb..496ef88 100644
Binary files a/Wrapper/Group/200-Follow-Group/GRP-200-Follow-Group.miz and b/Wrapper/Group/200-Follow-Group/GRP-200-Follow-Group.miz differ
diff --git a/Wrapper/Group/300-Switch-WayPoints/GRP-300-Switch-WayPoints.miz b/Wrapper/Group/300-Switch-WayPoints/GRP-300-Switch-WayPoints.miz
index fd3cd2c..8dadbdd 100644
Binary files a/Wrapper/Group/300-Switch-WayPoints/GRP-300-Switch-WayPoints.miz and b/Wrapper/Group/300-Switch-WayPoints/GRP-300-Switch-WayPoints.miz differ
diff --git a/Wrapper/Group/310-Command-StopRoute/GRP-310-Command-StopRoute.miz b/Wrapper/Group/310-Command-StopRoute/GRP-310-Command-StopRoute.miz
index 5225943..4c21149 100644
Binary files a/Wrapper/Group/310-Command-StopRoute/GRP-310-Command-StopRoute.miz and b/Wrapper/Group/310-Command-StopRoute/GRP-310-Command-StopRoute.miz differ
diff --git a/Wrapper/Group/400-RouteReturnToAirbase/GRP-400-RouteReturnToAirbase.miz b/Wrapper/Group/400-RouteReturnToAirbase/GRP-400-RouteReturnToAirbase.miz
index 7458aeb..f147777 100644
Binary files a/Wrapper/Group/400-RouteReturnToAirbase/GRP-400-RouteReturnToAirbase.miz and b/Wrapper/Group/400-RouteReturnToAirbase/GRP-400-RouteReturnToAirbase.miz differ
diff --git a/Wrapper/Group/500-Ground-TaskRoute/GRP-500-Ground-TaskRoute.miz b/Wrapper/Group/500-Ground-TaskRoute/GRP-500-Ground-TaskRoute.miz
index 9bc52dc..7c6393f 100644
Binary files a/Wrapper/Group/500-Ground-TaskRoute/GRP-500-Ground-TaskRoute.miz and b/Wrapper/Group/500-Ground-TaskRoute/GRP-500-Ground-TaskRoute.miz differ
diff --git a/Wrapper/Group/501-Ground-TaskRouteToVec2/GRP-501-Ground-TaskRouteToVec2.miz b/Wrapper/Group/501-Ground-TaskRouteToVec2/GRP-501-Ground-TaskRouteToVec2.miz
index 897b5e1..632a252 100644
Binary files a/Wrapper/Group/501-Ground-TaskRouteToVec2/GRP-501-Ground-TaskRouteToVec2.miz and b/Wrapper/Group/501-Ground-TaskRouteToVec2/GRP-501-Ground-TaskRouteToVec2.miz differ
diff --git a/Wrapper/Group/502-Route-at-waypoint-to-random-point/GRP-502-Route-at-waypoint-to-random-point.miz b/Wrapper/Group/502-Route-at-waypoint-to-random-point/GRP-502-Route-at-waypoint-to-random-point.miz
index c3decbf..c978e4b 100644
Binary files a/Wrapper/Group/502-Route-at-waypoint-to-random-point/GRP-502-Route-at-waypoint-to-random-point.miz and b/Wrapper/Group/502-Route-at-waypoint-to-random-point/GRP-502-Route-at-waypoint-to-random-point.miz differ
diff --git a/Wrapper/Group/503-NTTR-Route-at-waypoint-to-random-point/GRP-503-NTTR-Route-at-waypoint-to-random-point.miz b/Wrapper/Group/503-NTTR-Route-at-waypoint-to-random-point/GRP-503-NTTR-Route-at-waypoint-to-random-point.miz
index 99926aa..da0a367 100644
Binary files a/Wrapper/Group/503-NTTR-Route-at-waypoint-to-random-point/GRP-503-NTTR-Route-at-waypoint-to-random-point.miz and b/Wrapper/Group/503-NTTR-Route-at-waypoint-to-random-point/GRP-503-NTTR-Route-at-waypoint-to-random-point.miz differ
diff --git a/Wrapper/Group/504-Pinpoint-Strike-Waypooints-and-Tasking/GRP-504-Pinpoint-Strike-Waypooints-and-Tasking.miz b/Wrapper/Group/504-Pinpoint-Strike-Waypooints-and-Tasking/GRP-504-Pinpoint-Strike-Waypooints-and-Tasking.miz
index 49c639e..836ee88 100644
Binary files a/Wrapper/Group/504-Pinpoint-Strike-Waypooints-and-Tasking/GRP-504-Pinpoint-Strike-Waypooints-and-Tasking.miz and b/Wrapper/Group/504-Pinpoint-Strike-Waypooints-and-Tasking/GRP-504-Pinpoint-Strike-Waypooints-and-Tasking.miz differ
diff --git a/Wrapper/Group/510-Task-Follow/GRP-510-Task-Follow.miz b/Wrapper/Group/510-Task-Follow/GRP-510-Task-Follow.miz
index 7ae6f96..b65578f 100644
Binary files a/Wrapper/Group/510-Task-Follow/GRP-510-Task-Follow.miz and b/Wrapper/Group/510-Task-Follow/GRP-510-Task-Follow.miz differ
diff --git a/Wrapper/Group/550-Patrol-a-route/GRP-550-Patrol-a-route.miz b/Wrapper/Group/550-Patrol-a-route/GRP-550-Patrol-a-route.miz
index 29376cd..958e8db 100644
Binary files a/Wrapper/Group/550-Patrol-a-route/GRP-550-Patrol-a-route.miz and b/Wrapper/Group/550-Patrol-a-route/GRP-550-Patrol-a-route.miz differ
diff --git a/Wrapper/Group/551-Patrol-to-random-points-of-a-route/GRP-551-Patrol-to-random-points-of-a-route.miz b/Wrapper/Group/551-Patrol-to-random-points-of-a-route/GRP-551-Patrol-to-random-points-of-a-route.miz
index 49a1e74..35e650d 100644
Binary files a/Wrapper/Group/551-Patrol-to-random-points-of-a-route/GRP-551-Patrol-to-random-points-of-a-route.miz and b/Wrapper/Group/551-Patrol-to-random-points-of-a-route/GRP-551-Patrol-to-random-points-of-a-route.miz differ
diff --git a/Wrapper/Group/552-Patrol-in-a-zone/GRP-552-Patrol-in-a-zone.miz b/Wrapper/Group/552-Patrol-in-a-zone/GRP-552-Patrol-in-a-zone.miz
index dff26a4..ba08c19 100644
Binary files a/Wrapper/Group/552-Patrol-in-a-zone/GRP-552-Patrol-in-a-zone.miz and b/Wrapper/Group/552-Patrol-in-a-zone/GRP-552-Patrol-in-a-zone.miz differ
diff --git a/Wrapper/Group/553-Patrol-in-a-list-of-zones/GRP-553-Patrol-in-a-list-of-zones.miz b/Wrapper/Group/553-Patrol-in-a-list-of-zones/GRP-553-Patrol-in-a-list-of-zones.miz
index 45989c8..e0007a4 100644
Binary files a/Wrapper/Group/553-Patrol-in-a-list-of-zones/GRP-553-Patrol-in-a-list-of-zones.miz and b/Wrapper/Group/553-Patrol-in-a-list-of-zones/GRP-553-Patrol-in-a-list-of-zones.miz differ
diff --git a/Wrapper/Group/600-Respawn/GRP-600-Respawn.miz b/Wrapper/Group/600-Respawn/GRP-600-Respawn.miz
index 185e88d..602446b 100644
Binary files a/Wrapper/Group/600-Respawn/GRP-600-Respawn.miz and b/Wrapper/Group/600-Respawn/GRP-600-Respawn.miz differ
diff --git a/Wrapper/Group/601-Respawn-hidden/GRP-601-Respawn-hidden.miz b/Wrapper/Group/601-Respawn-hidden/GRP-601-Respawn-hidden.miz
index 9b496b8..35b9aa1 100644
Binary files a/Wrapper/Group/601-Respawn-hidden/GRP-601-Respawn-hidden.miz and b/Wrapper/Group/601-Respawn-hidden/GRP-601-Respawn-hidden.miz differ
diff --git a/Wrapper/Group/610-Respawn-in-Zone/GRP-610-Respawn-in-Zone.miz b/Wrapper/Group/610-Respawn-in-Zone/GRP-610-Respawn-in-Zone.miz
index 87eef05..a946150 100644
Binary files a/Wrapper/Group/610-Respawn-in-Zone/GRP-610-Respawn-in-Zone.miz and b/Wrapper/Group/610-Respawn-in-Zone/GRP-610-Respawn-in-Zone.miz differ
diff --git a/Wrapper/Group/611-Respawn-multiple-units-in-Zone/GRP-611-Respawn-multiple-units-in-Zone.miz b/Wrapper/Group/611-Respawn-multiple-units-in-Zone/GRP-611-Respawn-multiple-units-in-Zone.miz
index 4c933c9..16c8aed 100644
Binary files a/Wrapper/Group/611-Respawn-multiple-units-in-Zone/GRP-611-Respawn-multiple-units-in-Zone.miz and b/Wrapper/Group/611-Respawn-multiple-units-in-Zone/GRP-611-Respawn-multiple-units-in-Zone.miz differ
diff --git a/Wrapper/Group/612-Respawn-multiple-units-in-Zone-randomized/GRP-612-Respawn-multiple-units-in-Zone-randomized.miz b/Wrapper/Group/612-Respawn-multiple-units-in-Zone-randomized/GRP-612-Respawn-multiple-units-in-Zone-randomized.miz
index d550394..c2f5f0e 100644
Binary files a/Wrapper/Group/612-Respawn-multiple-units-in-Zone-randomized/GRP-612-Respawn-multiple-units-in-Zone-randomized.miz and b/Wrapper/Group/612-Respawn-multiple-units-in-Zone-randomized/GRP-612-Respawn-multiple-units-in-Zone-randomized.miz differ
diff --git a/Wrapper/Group/615-Respawn-in-Zone-hidden/GRP-615-Respawn-in-Zone-hidden.miz b/Wrapper/Group/615-Respawn-in-Zone-hidden/GRP-615-Respawn-in-Zone-hidden.miz
index 6727295..f47bf33 100644
Binary files a/Wrapper/Group/615-Respawn-in-Zone-hidden/GRP-615-Respawn-in-Zone-hidden.miz and b/Wrapper/Group/615-Respawn-in-Zone-hidden/GRP-615-Respawn-in-Zone-hidden.miz differ
diff --git a/Wrapper/Group/616-Respawn-multiple-units-in-Zone-hidden/GRP-616-Respawn-multiple-units-in-Zone-hidden.miz b/Wrapper/Group/616-Respawn-multiple-units-in-Zone-hidden/GRP-616-Respawn-multiple-units-in-Zone-hidden.miz
index 07230d5..d93ac0c 100644
Binary files a/Wrapper/Group/616-Respawn-multiple-units-in-Zone-hidden/GRP-616-Respawn-multiple-units-in-Zone-hidden.miz and b/Wrapper/Group/616-Respawn-multiple-units-in-Zone-hidden/GRP-616-Respawn-multiple-units-in-Zone-hidden.miz differ
diff --git a/Wrapper/Group/617-Respawn-multiple-units-in-Zone-randomized-hidden/GRP-617-Respawn-multiple-units-in-Zone-randomized-hidden.miz b/Wrapper/Group/617-Respawn-multiple-units-in-Zone-randomized-hidden/GRP-617-Respawn-multiple-units-in-Zone-randomized-hidden.miz
index b91f75b..94487ca 100644
Binary files a/Wrapper/Group/617-Respawn-multiple-units-in-Zone-randomized-hidden/GRP-617-Respawn-multiple-units-in-Zone-randomized-hidden.miz and b/Wrapper/Group/617-Respawn-multiple-units-in-Zone-randomized-hidden/GRP-617-Respawn-multiple-units-in-Zone-randomized-hidden.miz differ
diff --git a/Wrapper/Group/900-Option-Green-and-Red-State/GRP-900-Option-Green-and-Red-State.miz b/Wrapper/Group/900-Option-Green-and-Red-State/GRP-900-Option-Green-and-Red-State.miz
index 698bfd1..0cd500a 100644
Binary files a/Wrapper/Group/900-Option-Green-and-Red-State/GRP-900-Option-Green-and-Red-State.miz and b/Wrapper/Group/900-Option-Green-and-Red-State/GRP-900-Option-Green-and-Red-State.miz differ
diff --git a/Wrapper/Weapon/010-Track-Bomb/WPN-010-Track-Bomb.miz b/Wrapper/Weapon/010-Track-Bomb/WPN-010-Track-Bomb.miz
index 3b5c1e3..da669b5 100644
Binary files a/Wrapper/Weapon/010-Track-Bomb/WPN-010-Track-Bomb.miz and b/Wrapper/Weapon/010-Track-Bomb/WPN-010-Track-Bomb.miz differ
diff --git a/Wrapper/Weapon/020-Track-AA-Missile/WPN-020-Track-AA-Missile.miz b/Wrapper/Weapon/020-Track-AA-Missile/WPN-020-Track-AA-Missile.miz
index beeecf2..8a50880 100644
Binary files a/Wrapper/Weapon/020-Track-AA-Missile/WPN-020-Track-AA-Missile.miz and b/Wrapper/Weapon/020-Track-AA-Missile/WPN-020-Track-AA-Missile.miz differ
diff --git a/Wrapper/Weapon/030-Track-SA-Missile/WPN-030-Track-SA-Missile.miz b/Wrapper/Weapon/030-Track-SA-Missile/WPN-030-Track-SA-Missile.miz
index d64cb14..8e2143f 100644
Binary files a/Wrapper/Weapon/030-Track-SA-Missile/WPN-030-Track-SA-Missile.miz and b/Wrapper/Weapon/030-Track-SA-Missile/WPN-030-Track-SA-Missile.miz differ
diff --git a/Wrapper/Weapon/040-Track-Shell/WPN-040-Track-Shell.miz b/Wrapper/Weapon/040-Track-Shell/WPN-040-Track-Shell.miz
index b90d79a..eb63f05 100644
Binary files a/Wrapper/Weapon/040-Track-Shell/WPN-040-Track-Shell.miz and b/Wrapper/Weapon/040-Track-Shell/WPN-040-Track-Shell.miz differ