Trying out the github action
This commit is contained in:
@@ -12,10 +12,11 @@ jobs:
|
|||||||
with:
|
with:
|
||||||
fetch-depth: 0
|
fetch-depth: 0
|
||||||
|
|
||||||
- name: Run SpearheadCompile
|
- name: Compile Spearhead
|
||||||
run: |
|
uses: dutchie031/DcsMissionScriptingTools/github-action@feature/github-action
|
||||||
mkdir -p ./output
|
with:
|
||||||
python3 SpearheadCompile.py . ./output/spearhead.lua
|
source-root: ./src
|
||||||
|
output-file: ./output/spearhead.lua
|
||||||
|
|
||||||
- name: Upload spearhead.lua artifact
|
- name: Upload spearhead.lua artifact
|
||||||
uses: actions/upload-artifact@v4
|
uses: actions/upload-artifact@v4
|
||||||
|
|||||||
@@ -90,13 +90,13 @@
|
|||||||
Missions are also defined by trigger zones. <br>
|
Missions are also defined by trigger zones. <br>
|
||||||
They'll be picked up by Spearhead when named according to the naming convention: <br>
|
They'll be picked up by Spearhead when named according to the naming convention: <br>
|
||||||
<code-inline>MISSION_[Type]_[FreeForm]</code-inline> <br>
|
<code-inline>MISSION_[Type]_[FreeForm]</code-inline> <br>
|
||||||
Where <code-inline>[Type]</code-inline> is the type of mission. <br>
|
Where <code-inline>[Type]</code-inline> is the type of mission. <a href="./reference.html#mission-zones">See all</a><br>
|
||||||
|
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h3 id="mission-cas">CAS</h3>
|
<h3 id="mission-cas">CAS</h3>
|
||||||
<p>
|
<p>
|
||||||
Personally CAS is one of our favorite mission types. <br>
|
Personally CAS is one of my favorite mission types. <br>
|
||||||
Mostly because it's easy to set up and creates a truly immersive experience. <br>
|
Mostly because it's easy to set up and creates a truly immersive experience. <br>
|
||||||
|
|
||||||
</p>
|
</p>
|
||||||
|
|||||||
@@ -80,11 +80,22 @@
|
|||||||
<strong>Example:</strong> <code-inline>MISSION_DEAD_BYRON</code-inline>
|
<strong>Example:</strong> <code-inline>MISSION_DEAD_BYRON</code-inline>
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Missions are completable objectives with specific types, such as DEAD, BAI, STRIKE, or SAM. <br />
|
Missions are completable objectives with specific types. <br />
|
||||||
Randomized missions can be defined using the format: <span
|
Randomized missions can be defined using the format: <span
|
||||||
class="inline-lua"><span class="lua-variable">RANDOMMISSION_[Type]_[Name]_[Index]</span></span>.
|
class="inline-lua"><span class="lua-variable">RANDOMMISSION_[Type]_[Name]_[Index]</span></span>.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
Valid Types:
|
||||||
|
<ul>
|
||||||
|
<li>SAM</li>
|
||||||
|
<li>DEAD</li>
|
||||||
|
<li>BAI</li>
|
||||||
|
<li>CAS</li>
|
||||||
|
<li>STRIKE</li>
|
||||||
|
</ul>
|
||||||
|
</p>
|
||||||
|
|
||||||
<h3 id="cap-routes">CAP Routes</h3>
|
<h3 id="cap-routes">CAP Routes</h3>
|
||||||
<p>
|
<p>
|
||||||
<strong>Format:</strong> <code-inline>CAPROUTE_[routeID]_[Name]</code-inline> <br />
|
<strong>Format:</strong> <code-inline>CAPROUTE_[routeID]_[Name]</code-inline> <br />
|
||||||
|
|||||||
Reference in New Issue
Block a user