From a4d6ff0140abcd27c02a4151135c674aa1cd4716 Mon Sep 17 00:00:00 2001 From: Rolf Geuenich Date: Tue, 31 Oct 2023 10:56:45 +0100 Subject: [PATCH] Fixed broken links --- Beta_Test_Guide.md | 6 ++++-- Contribution_Guide.md | 4 ++-- Interactive_Debug_Guide.md | 4 ++-- Moose_Core.md | 4 ++-- Moose_Functional.md | 4 ++-- Moose_Setup_Guide.md | 2 +- 6 files changed, 13 insertions(+), 11 deletions(-) diff --git a/Beta_Test_Guide.md b/Beta_Test_Guide.md index c32fca083..c8c716bff 100644 --- a/Beta_Test_Guide.md +++ b/Beta_Test_Guide.md @@ -14,7 +14,9 @@ You are going to learn : This might be a bit daunting at first, but the rewards in term of simplified workflow and direct access to new features is well worth the effort! If you have any problem during the setup or at any other point, don't hesitate to ask the [community](Communities) for help! -This guide assumes that **you already setup your development environment**, like a "normal" mission designer. Which means Lua Development Tools (LDT) is installed on your computer, and you already know how to create a mission using MOOSE. If it is not the case, please follow the instructions [here](http://flightcontrol-master.github.io/MOOSE/Usage_Guide.html) before proceeding. +This guide assumes that **you already setup your development environment**, like a "normal" mission designer. +Which means Lua Development Tools (LDT) is installed on your computer, and you already know how to create a mission using MOOSE. +If it is not the case, please follow the instructions [here](http://flightcontrol-master.github.io/MOOSE/Moose_Setup_Guide.html) before proceeding. # 1) Installation @@ -29,7 +31,7 @@ Since the MOOSE code is evolving very rapidely between Releases, we store the MO Link the MOOSE repository on GITHUB to your freshly installed GITHUB desktop. This is done by browing to the [MOOSE repository at GITHUB](https://github.com/FlightControl-Master/MOOSE), and selecting the green button **Clone or Download** -> **Open in Desktop**. -![](Installation/GitHub_Clone.jpg) +![](Installation/GitHub_Clone.JPG) Specify a local directory on your PC where you want to store the MOOSE repository contents. Sync the MOOSE repository to a defined local MOOSE directory on your PC using GITHUB desktop (press the sync button). diff --git a/Contribution_Guide.md b/Contribution_Guide.md index c66e20aa7..26f5f3194 100644 --- a/Contribution_Guide.md +++ b/Contribution_Guide.md @@ -22,7 +22,7 @@ You are assumed to be familar with at least the basics of GitHub (branches, comm Moose is in fact located on **three repositories** : * [**MOOSE**](https://github.com/FlightControl-Master/MOOSE) contains the Moose's **code**, the **documentation** and the file necessary to the **setup** -* [**MOOSE_MISSIONS**](https://github.com/FlightControl-Master/MOOSE_MISSIONS) contains the **test missions**. Be aware that the [master-release branch](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master-release) contains the statically loaded test missions, while the [master branch](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master) contains their dynamically loaded counterparts. will want to create a local repository for this one and to sync it. +* [**MOOSE_MISSIONS**](https://github.com/FlightControl-Master/MOOSE_MISSIONS) contains the **demo missions** * [**MOOSE_PRESENTATIONS**](https://github.com/FlightControl-Master/MOOSE_PRESENTATIONS) contains bits and bob related to Moose, like Moose's logos and PowerPoint files to present a specific feature of Moose. ## 1.2) Branches @@ -77,7 +77,7 @@ To ensure a good degree of **consistency** in Moose's code, we follow the follow # 4) The Luadoc -The **Luadoc system** is not only **useful for the contributor** to understand the code, but **also the mission designer**, as it used to automatically generate the [HTML documentation](http://flightcontrol-master.github.io/MOOSE/Documentation/index.html). +The **Luadoc system** is not only **useful for the contributor** to understand the code, but **also the mission designer**, as it used to automatically generate the [HTML documentation](http://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/index.html). It thus needs to follow some strict standards. Keep in mind the following informations : diff --git a/Interactive_Debug_Guide.md b/Interactive_Debug_Guide.md index dd6e2270d..29278c625 100644 --- a/Interactive_Debug_Guide.md +++ b/Interactive_Debug_Guide.md @@ -97,7 +97,7 @@ You should have at least on your disk: This is the **debug client**. The source is part of the LDT debug suite, but has been modified to work together with the DCS World scripting engine. You need to copy this file to the root directory of your DCS World installation in Program Files. -![](Debugging/DEBUG_debugger.JPG) +![](Debugging/DEBUG_Debugger.JPG) By example, the location of debugger.lua is here on my DCS World installation PC. @@ -242,7 +242,7 @@ First we setup the Debug as your "favorite", so that it is easy for your to repe Click on the "Bug" icon that you'll find in the task bar. The "Bug" icon is the place where you will start your **debug listener**. However, first, click on Organize Favorites. You need to do this one time only. -![](Debugging/DEBUG_Add Favorites.JPG) +![](Debugging/DEBUG_Add_Favorites.JPG) Just click on the Debug Name that you entered (for me DCS 1.5) in the Debug Configuration window and it will be added ot your favorites. I did already that, so it was already added as an example in the previous picture. diff --git a/Moose_Core.md b/Moose_Core.md index 3b3de9b4e..5ca490aa6 100644 --- a/Moose_Core.md +++ b/Moose_Core.md @@ -168,7 +168,7 @@ Defines an extensive API to manage 3D points in the DCS World 3D simulation spac **The coordinate system classes are essential to understand. Learn this!** -## 9. [**RADIO**](Documentation/Core.Radio.html) +## 9. [**RADIO**](Documentation/Sound.Radio.html) ![RADIO](Images\Core_Radio.JPG) @@ -331,7 +331,7 @@ Manage user flags to interact with the mission editor trigger system and server **User flags are the method to set or retrieve the value of flags as set in the mission editor.** -## 18. [**USERSOUND**](Documentation/Core.UserSound.html) +## 18. [**USERSOUND**](Documentation/Sound.UserSound.html) ![USERSOUND](Images\Core_Usersound.JPG) diff --git a/Moose_Functional.md b/Moose_Functional.md index 4657a9647..3bfaa0ea0 100644 --- a/Moose_Functional.md +++ b/Moose_Functional.md @@ -18,7 +18,7 @@ The ATC_GROUND classes monitor airbase traffic and regulate speed while taxiing. * Kick speeding players during taxi. -## 2. [**ARTY**](Documentation/Functional.Arty.html) +## 2. [**ARTY**](Documentation/Functional.Artillery.html) ![Arty](Images\Artillery.JPG) @@ -154,7 +154,7 @@ The RANGE class enables easy set up of bombing and strafing ranges within DCS Wo * Range information and weather report at the range can be reported via radio menu. -## 9. [**RAT**](Documentation/Functional.Rat.html) +## 9. [**RAT**](Documentation/Functional.RAT.html) ![rat](Images\RAT.JPG) diff --git a/Moose_Setup_Guide.md b/Moose_Setup_Guide.md index 2e8638b87..424475ceb 100644 --- a/Moose_Setup_Guide.md +++ b/Moose_Setup_Guide.md @@ -244,7 +244,7 @@ you'll have to include this **Moose.lua** file into your missions: 2. In the mission editor, create a new trigger. 3. Name the trigger Moose Load and let it execute only at MISSION START. 4. Add an action DO SCRIPT FILE (without a condition, so the middle column must be empty). - 5. In the action, browse to the **[Moose.lua](https://github.com/FlightControl-Master/MOOSE/tree/master/Moose%20Mission%20Setup)** file in the **Moose Mission Setup** directory, and include this file within your mission. + 5. In the action, browse to the **Moose.lua** file and include this file within your mission. 6. Make sure that the "Moose Load" trigger is completely at the top of your mission. Voila, MOOSE is now included in your mission. During the execution of this mission, all MOOSE classes will be loaded, and all MOOSE initializations will be exectuted before any other mission action is executed.