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

.github/workflows/gh-pages.yml

@@ -67,3 +67,12 @@ jobs:
       - name: Deploy to GitHub Pages
         id: deployment
         uses: actions/deploy-pages@v1
+
+  check:
+    runs-on: ubuntu-latest
+    needs: deploy
+    steps:
+      - name: Setup Node
+        uses: actions/setup-node@v3
+      - run: npm install linkinator
+      - run: npx linkinator https://flightcontrol-master.github.io/MOOSE/ --recurse

Moose Development/Moose/Wrapper/Unit.lua

@@ -20,8 +20,8 @@
 -- @module Wrapper.Unit
 -- @image Wrapper_Unit.JPG
 
-
---- @type UNIT
+---
+-- @type UNIT
 -- @field #string ClassName Name of the class.
 -- @field #string UnitName Name of the unit.
 -- @field #string GroupName Name of the group the unit belongs to.
@@ -561,7 +561,7 @@ end
 
 --- Check if the unit is a tanker. Also retrieves the refuelling system (boom or probe) if applicable.
 -- @param #UNIT self
--- @return #boolean If true, unit is refuelable (checks for the attribute "Refuelable").
+-- @return #boolean If true, unit is a tanker (checks for the attribute "Tankers").
 -- @return #number Refueling system (if any): 0=boom, 1=probe.
 function UNIT:IsTanker()
   self:F2( self.UnitName )
@@ -582,7 +582,7 @@ function UNIT:IsTanker()
     -- Some hard coded data as this is not in the descriptors...
     if typename=="IL-78M" then
       system=1 --probe
-    elseif typename=="KC130" then
+    elseif typename=="KC130" or typename=="KC130J" then
       system=1 --probe
     elseif typename=="KC135BDA" then
       system=1 --probe
@@ -590,6 +590,10 @@ function UNIT:IsTanker()
       system=1 --probe
     elseif typename=="S-3B Tanker" then
       system=1 --probe
+    elseif typename=="KC_10_Extender" then
+      system=1 --probe
+    elseif typename=="KC_10_Extender_D" then
+      system=0 --boom
     end
     
   end

docs/_config.yml

@@ -1,3 +1,5 @@
+baseurl: ""
+url: "https://flightcontrol-master.github.io"
 repository: FlightControl-Master/MOOSE
 title: MOOSE
 description: MOOSE is a Mission Object Oriented Scripting Environment for mission designers in DCS World

docs/buildsystem/build-docs.md

@@ -56,7 +56,7 @@ Main build steps to create the class documentation are defined in [.github/workf
     - Copy build result to `MOOSE_DOCS` folder.
     - Push results to the target repository.
 
-[tree]: https://www.cyberciti.biz/faq/linux-show-directory-structure-command-line/
+[tree]: https://wiki.ubuntuusers.de/tree/
 [LuaDoc]: https://keplerproject.github.io/luadoc/
 [LuaDocumentor]: https://luarocks.org/modules/luarocks/luadocumentor
 [Applevangelist/luadocumentor]: https://github.com/Applevangelist/luadocumentor/tree/patch-1

docs/buildsystem/build-includes.md

@@ -35,7 +35,7 @@ Main build steps to create the include files are defined in [.github/workflows/b
     - Push results to [MOOSE_INCLUDE] repository
 
 [.github/workflows/build-includes.yml]: https://github.com/FlightControl-Master/MOOSE/blob/master/.github/workflows/build-includes.yml
-[tree]: https://www.cyberciti.biz/faq/linux-show-directory-structure-command-line/
+[tree]: https://wiki.ubuntuusers.de/tree/
 [lua5.3]: https://www.lua.org/manual/5.3/
 [LuaRocks]: https://luarocks.org/
 [LuaCheck]: https://github.com/mpeterv/luacheck

docs/buildsystem/gh-pages.md

@@ -34,7 +34,7 @@ This can be displayed as follows:
 - You need a working installation of [Docker].
 - Go to the `docs` subfolder.
 - Run `docker compose up`.
-- Open a browser with the following URL: <http://127.0.0.1:4000/>.
+- Open a browser with the following URL: `http://127.0.0.1:4000/`.
 - After a change of the [Markdown] files, wait some seconds and press F5 in the browser.
 
 [GitHub Pages]: https://pages.github.com/