Merge remote-tracking branch 'origin/master' into develop

Moose Development/Moose/Core/Beacon.lua

@@ -8,6 +8,10 @@
 --
 -- ===
 --
+-- ### [Demo Missions](https://github.com/FlightControl-Master/MOOSE_Demos/tree/master/Core/Beacon)
+--
+-- ===
+--
 -- ### Authors: Hugues "Grey_Echo" Bousquet, funkyfranky
 --
 -- @module Core.Beacon
@@ -286,6 +290,7 @@ end
 -- myBeacon:AATACAN(20, "TEXACO", true) -- Activate the beacon
 function BEACON:AATACAN(TACANChannel, Message, Bearing, BeaconDuration)
   self:F({TACANChannel, Message, Bearing, BeaconDuration})
+  self:E("This method is DEPRECATED! Please use ActivateTACAN() instead.")
 
   local IsValid = true
 

Moose Development/Moose/Core/Zone.lua

@@ -46,6 +46,10 @@
 --
 -- ===
 --
+-- ### [Demo Missions](https://github.com/FlightControl-Master/MOOSE_Demos/tree/master/Core/Zone)
+--
+-- ===
+--
 -- ### Author: **FlightControl**
 -- ### Contributions: **Applevangelist**, **FunkyFranky**, **coconutcockpit**
 --

Moose Development/Moose/Sound/Radio.lua

@@ -30,6 +30,10 @@
 --
 -- ===
 --
+-- ### [Demo Missions](https://github.com/FlightControl-Master/MOOSE_Demos/tree/master/Sound/Radio)
+--
+-- ===
+--
 -- ### Authors: Hugues "Grey_Echo" Bousquet, funkyfranky
 --
 -- @module Sound.Radio

docs/beginner/ask-for-help.md

@@ -35,16 +35,24 @@ Please remember when posting a question:
 - Before posting anything follow the [troubleshooting steps].
 - **Read your logs**.
 
+### Formulate a good description
+
 A post should contain the following:
 
-1. A describtion what you expected to happen and what actually happened.
-    - Do not use vague words this stuff is hard to help with! Be specific.
+- A description what you expected to happen and what actually happened.
+  - Do not use vague words this stuff is hard to help with! Be specific.
 
-2. Describe what happens instead.
-    - The less detail you offer, the less chance you can be helped.
-    - Don’t say it doesn’t work. Or is it broken. Say what it actually does.
+- Describe what happens instead.
+  - The less detail you offer, the less chance you can be helped.
+  - Don't say it doesn't work. Or is it broken. Say what it actually does.
 
-3. Post your code in Discord as formatted code:
+### Format your code
+
+The easier your code is to read, the more likely you are to get a helpful answer. If your code is hard to read, some
+people who could help you may not even bother to read your code. Syntax Highlighting makes the code much clearer and
+easier to understand. Therefore:
+
+- Post your code in Discord as formatted code:
 
   - Wrap a single line of code in backticks \` like this:
 
@@ -54,14 +62,31 @@ A post should contain the following:
 
     ![discord-multi-line-code.png](../images/beginner/discord-multi-line-code.png)
 
-- Post your log lines with the error or warning messages. Format them like this:
+### Do not post a screenshot of your code
 
-    ![discord-fomat-logs.png](../images/beginner/discord-fomat-logs.png)
+Your code is easy to read on a screenshot if you are using a good text editor or IDE, but if someone discovers an error
+in your code and wants to post a corrected version, they will have to type out the entire code. This could lead to them
+not helping you because it's too much work for them.
+
+### Post your log
+
+If the error message in the `dcs.log` does not tell you anything, then post it in the Discord.
+
+- Post the important log lines with the error or warning messages. Format them like this:
+
+  ![discord-format-logs.png](../images/beginner/discord-format-logs.png)
+
+### Send your mission when requested
+
+Please don't just send your mission file. You have to manually extract the script from the file.
+It is better to send your script code and log lines beforehand.
+If this does not help, you may be asked to send your mission.
 
 - Some complex problems need the mission (.miz file) also.
 
   - But post your mission only when requested.
   - Try to simplify your mission if it is complex!
+  - Try to avoid or delete MODs, because could prevent people from helping you.
 
 There are people in the Discord and in the forum, who spend their free time to
 help you. <br />

docs/beginner/problems.md

@@ -11,10 +11,14 @@ nav_order: 05
 
 ## Something went wrong
 
-If the mission shows not the expected behaviour do the following steps:
+If the mission shows not the expected behavior do the following steps:
 
 1. Double check if you added the changed mission script to the mission again!
-1. Check if the triggers are configured as requested in the last sections.
+1. Check if the triggers are configured as requested in the last sections:
+  - To load MOOSE: `4 MISSION START`, nothing on `CONDITIONS`, `DO SCRIPT FILE` to load `Moose_.lua`.
+  - To load mission script(s): `1 ONCE`, in `CONDITIONS` add `TIME MORE` = 1, `DO SCRIPT FILE` to load `yourscript.lua`.
+1. Double check if you have the right version of MOOSE (some classes need the develop branch).
+1. Try the newest version of MOOSE.
 
 ## Read the logs
 
@@ -22,8 +26,7 @@ The DCS log is a super important and useful log for the entire of DCS World.
 All scripting and other errors are recorded here. It is the one stop shop for
 things that occurred in your mission. It will tell you if there was a mistake.
 
-1. Open the file `dcs.log` in the `Logs` subfolder in your DCS
-  [Saved Games folder].
+1. Open the file `dcs.log` in the `Logs` subfolder in your DCS [Saved Games folder].
 
 1. Search for the following line: `*** MOOSE INCLUDE END ***`
   - If it is included in the log, Moose was loaded.