weyne/MOOSE
1
0
Fork 0
mirror of https://github.com/FlightControl-Master/MOOSE.git synced 2025-08-15 10:47:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix for broken links in documentation

Browse Source
This commit is contained in:
kaltokri 2024-01-02 20:03:18 +01:00
parent 8d45ea00e8
commit d6a0fff993
11 changed files with 28 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Moose Development/Moose/Functional/AICSAR.lua
View File

@ -16,9 +16,9 @@
-- === -- ===
-- --
-- ## Example Missions: -- ## Example Missions:
-- --
-- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/CSR-001%20-%20Basics). -- Demo missions can be found on [GitHub](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/Functional/AICSAR).
-- --
-- === -- ===
-- --
-- ### Author: **Applevangelist** -- ### Author: **Applevangelist**

6
Moose Development/Moose/Functional/AmmoTruck.lua
View File

@ -8,7 +8,7 @@
-- --
-- ## Missions: -- ## Missions:
-- --
-- ### [AmmoTruck](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/AMT%20-%20AmmoTruck/AmmoTruck%20100%20-%20NTTR%20-%20Basic) -- Demo missions can be found on [GitHub](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/Functional/AmmoTruck)
-- --
-- === -- ===
-- --
@ -20,7 +20,7 @@
-- Last update: July 2023 -- Last update: July 2023
------------------------------------------------------------------------- -------------------------------------------------------------------------
--- **AMMOTRUCK** class, extends Core.FSM#FSM --- **AMMOTRUCK** class, extends Core.Fsm#FSM
-- @type AMMOTRUCK -- @type AMMOTRUCK
-- @field #string ClassName Class Name -- @field #string ClassName Class Name
-- @field #string lid Lid for log entries -- @field #string lid Lid for log entries
@ -41,7 +41,7 @@
-- @field #number waitingtime Max waiting time in seconds -- @field #number waitingtime Max waiting time in seconds
-- @field #boolean routeonroad Route truck on road if true (default) -- @field #boolean routeonroad Route truck on road if true (default)
-- @field #number reloads Number of reloads a single truck can do before he must return home -- @field #number reloads Number of reloads a single truck can do before he must return home
-- @extends Core.FSM#FSM -- @extends Core.Fsm#FSM
--- *Amateurs talk about tactics, but professionals study logistics.* - General Robert H Barrow, USMC --- *Amateurs talk about tactics, but professionals study logistics.* - General Robert H Barrow, USMC
-- --

8
Moose Development/Moose/Functional/Autolase.lua
View File

@ -5,11 +5,11 @@
-- **AUOTLASE** - Autolase targets in the field. -- **AUOTLASE** - Autolase targets in the field.
-- --
-- === -- ===
-- --
-- ## Missions: -- ## Missions:
-- --
-- ### [Autolase](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/) -- None yet.
-- --
-- === -- ===
-- --
-- **Main Features:** -- **Main Features:**
@ -443,7 +443,7 @@ end
-- @param #string Gender (Optional) Defaults to "male" -- @param #string Gender (Optional) Defaults to "male"
-- @param #string Culture (Optional) Defaults to "en-US" -- @param #string Culture (Optional) Defaults to "en-US"
-- @param #number Port (Optional) Defaults to 5002 -- @param #number Port (Optional) Defaults to 5002
-- @param #string Voice (Optional) Use a specifc voice with the @{Sound.SRS.SetVoice} function, e.g, `:SetVoice("Microsoft Hedda Desktop")`. -- @param #string Voice (Optional) Use a specifc voice with the @{Sound.SRS#SetVoice} function, e.g, `:SetVoice("Microsoft Hedda Desktop")`.
-- Note that this must be installed on your windows system. Can also be Google voice types, if you are using Google TTS. -- Note that this must be installed on your windows system. Can also be Google voice types, if you are using Google TTS.
-- @param #number Volume (Optional) Volume - between 0.0 (silent) and 1.0 (loudest) -- @param #number Volume (Optional) Volume - between 0.0 (silent) and 1.0 (loudest)
-- @param #string PathToGoogleKey (Optional) Path to your google key if you want to use google TTS -- @param #string PathToGoogleKey (Optional) Path to your google key if you want to use google TTS

8
Moose Development/Moose/Ops/AirWing.lua
View File

@ -10,7 +10,7 @@
-- --
-- ## Example Missions: -- ## Example Missions:
-- --
-- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20Airwing). -- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/Ops/Airwing).
-- --
-- === -- ===
-- --
@ -1398,9 +1398,9 @@ function AIRWING:GetTankerForFlight(flightgroup)
return nil return nil
end end
--- Add the ability to call back an Ops.Awacs#AWACS object with an FSM call "FlightOnMission(FlightGroup, Mission)". --- Add the ability to call back an Ops.AWACS#AWACS object with an FSM call "FlightOnMission(FlightGroup, Mission)".
-- @param #AIRWING self -- @param #AIRWING self
-- @param Ops.Awacs#AWACS ConnectecdAwacs -- @param Ops.AWACS#AWACS ConnectecdAwacs
-- @return #AIRWING self -- @return #AIRWING self
function AIRWING:SetUsingOpsAwacs(ConnectecdAwacs) function AIRWING:SetUsingOpsAwacs(ConnectecdAwacs)
self:I(self.lid .. "Added AWACS Object: "..ConnectecdAwacs:GetName() or "unknown") self:I(self.lid .. "Added AWACS Object: "..ConnectecdAwacs:GetName() or "unknown")
@ -1409,7 +1409,7 @@ function AIRWING:SetUsingOpsAwacs(ConnectecdAwacs)
return self return self
end end
--- Remove the ability to call back an Ops.Awacs#AWACS object with an FSM call "FlightOnMission(FlightGroup, Mission)". --- Remove the ability to call back an Ops.AWACS#AWACS object with an FSM call "FlightOnMission(FlightGroup, Mission)".
-- @param #AIRWING self -- @param #AIRWING self
-- @return #AIRWING self -- @return #AIRWING self
function AIRWING:RemoveUsingOpsAwacs() function AIRWING:RemoveUsingOpsAwacs()

6
Moose Development/Moose/Ops/Awacs.lua
View File

@ -7,9 +7,9 @@
-- === -- ===
-- --
-- ## Example Missions: -- ## Example Missions:
-- --
-- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20Awacs/). -- Demo missions can be found on [GitHub](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/Ops/Awacs/).
-- --
-- ## Videos: -- ## Videos:
-- --
-- Demo videos can be found on [Youtube](https://www.youtube.com/watch?v=ocdy8QzTNN4&list=PLFxp425SeXnq-oS0DSjam1HtddywH8i_k) -- Demo videos can be found on [Youtube](https://www.youtube.com/watch?v=ocdy8QzTNN4&list=PLFxp425SeXnq-oS0DSjam1HtddywH8i_k)

2
Moose Development/Moose/Ops/Brigade.lua
View File

@ -10,7 +10,7 @@
-- --
-- ## Example Missions: -- ## Example Missions:
-- --
-- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20Brigade). -- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/Ops/Brigade).
-- --
-- === -- ===
-- --

4
Moose Development/Moose/Ops/Chief.lua
View File

@ -126,7 +126,7 @@
-- When the chief detects a valid target, he will launch a certain number of selected assets. Only whole groups from SQUADRONs, PLATOONs or FLOTILLAs can be selected. -- When the chief detects a valid target, he will launch a certain number of selected assets. Only whole groups from SQUADRONs, PLATOONs or FLOTILLAs can be selected.
-- In other words, it is not possible to specify the abount of individual *units*. -- In other words, it is not possible to specify the abount of individual *units*.
-- --
-- By default, one group is selected for any detected target. This can, however, be customized with the @{CHIEF.SetResponseOnTarget}() function. The number of min and max -- By default, one group is selected for any detected target. This can, however, be customized with the @{#CHIEF.SetResponseOnTarget}() function. The number of min and max
-- asset groups can be specified depending on threatlevel, category, mission type, number of units, defcon and strategy. -- asset groups can be specified depending on threatlevel, category, mission type, number of units, defcon and strategy.
-- --
-- For example: -- For example:
@ -311,7 +311,7 @@ CHIEF.Strategy = {
--- Resource list. --- Resource list.
-- @type CHIEF.Resources -- @type CHIEF.Resources
-- @field <#CHIEF.Resource> List of resources. -- @field #CHIEF.Resource List of resources.
--- Resource. --- Resource.
-- @type CHIEF.Resource -- @type CHIEF.Resource

2
Moose Development/Moose/Ops/Fleet.lua
View File

@ -9,7 +9,7 @@
-- --
-- ## Example Missions: -- ## Example Missions:
-- --
-- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20Fleet). -- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/Ops/Fleet).
-- --
-- === -- ===
-- --

10
Moose Development/Moose/Ops/FlightControl.lua
View File

@ -12,7 +12,7 @@
-- --
-- ## Example Missions: -- ## Example Missions:
-- --
-- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20FlightControl). -- Demo missions: None
-- --
-- === -- ===
-- --
@ -207,9 +207,9 @@
-- landing is `21L`. -- landing is `21L`.
-- --
-- By default, the runways for landing and takeoff are determined from the wind direction as described above. For cases where this gives wrong results, you can set the active runways manually. This is -- By default, the runways for landing and takeoff are determined from the wind direction as described above. For cases where this gives wrong results, you can set the active runways manually. This is
-- done via @{Wrappper.Airbase#AIRBASE} class. -- done via @{Wrapper.Airbase#AIRBASE} class.
-- --
-- More specifically, you can use the @{Wrappper.Airbase#AIRBASE.SetActiveRunwayLanding} function to set the landing runway and the @{Wrappper.Airbase#AIRBASE.SetActiveRunwayTakeoff} function to set -- More specifically, you can use the @{Wrapper.Airbase#AIRBASE.SetActiveRunwayLanding} function to set the landing runway and the @{Wrapper.Airbase#AIRBASE.SetActiveRunwayTakeoff} function to set
-- the runway for takeoff. -- the runway for takeoff.
-- --
-- ## Example for Nellis AFB -- ## Example for Nellis AFB
@ -223,7 +223,7 @@
-- --
-- # DCS ATC -- # DCS ATC
-- --
-- You can disable the DCS ATC with the @{Wrappper.Airbase#AIRBASE.SetRadioSilentMode}(*true*). This does not remove the DCS ATC airbase from the F10 menu but makes the ATC unresponsive. -- You can disable the DCS ATC with the @{Wrapper.Airbase#AIRBASE.SetRadioSilentMode}(*true*). This does not remove the DCS ATC airbase from the F10 menu but makes the ATC unresponsive.
-- --
-- --
-- # Examples -- # Examples
@ -876,7 +876,7 @@ end
--- Set ATIS. --- Set ATIS.
-- @param #FLIGHTCONTROL self -- @param #FLIGHTCONTROL self
-- @param Ops.Atis#ATIS Atis ATIS. -- @param Ops.ATIS#ATIS ATIS ATIS.
-- @return #FLIGHTCONTROL self -- @return #FLIGHTCONTROL self
function FLIGHTCONTROL:SetATIS(Atis) function FLIGHTCONTROL:SetATIS(Atis)
self.atis=Atis self.atis=Atis

2
Moose Development/Moose/Ops/Operation.lua
View File

@ -11,7 +11,7 @@
-- --
-- ## Example Missions: -- ## Example Missions:
-- --
-- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20Operation). -- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/Ops/Operation).
-- --
-- === -- ===
-- --

2
Moose Development/Moose/Ops/OpsTransport.lua
View File

@ -12,7 +12,7 @@
-- --
-- ## Example Missions: -- ## Example Missions:
-- --
-- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/OPS%20-%20Transport). -- Demo missions can be found on [github](https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/develop/Ops/Transport).
-- --
-- === -- ===
-- --