Trying out the github action

This commit is contained in:
2026-04-07 22:48:15 +02:00
parent a4b87bee31
commit 8da10e4d03
3 changed files with 19 additions and 7 deletions
+2 -2
View File
@@ -90,13 +90,13 @@
Missions are also defined by trigger zones. <br>
They'll be picked up by Spearhead when named according to the naming convention: <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>
<h3 id="mission-cas">CAS</h3>
<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>
</p>
+12 -1
View File
@@ -80,11 +80,22 @@
<strong>Example:</strong> <code-inline>MISSION_DEAD_BYRON</code-inline>
</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
class="inline-lua"><span class="lua-variable">RANDOMMISSION_[Type]_[Name]_[Index]</span></span>.
</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>
<p>
<strong>Format:</strong> <code-inline>CAPROUTE_[routeID]_[Name]</code-inline> <br />