MOOSE generated documentation [skip ci]

This commit is contained in:
Applevangelist
2022-10-22 09:15:30 +00:00
parent 16abde2bbb
commit ffeb91ddff
140 changed files with 1051 additions and 1233 deletions

View File

@@ -405,7 +405,7 @@
<div class="w3-display-bottommiddle" style="word-break:break-word;"><h2><strong><a href="Actions.Act_Account.html">Actions.Act_Account</a></strong></h2></div>
</div>
<div class="w3-container w3-padding w3-white picturebox" style="word-break:break-word;"><p>
<p><strong>Actions</strong> - ACT_ACCOUNT_ classes <strong>account for</strong> (detect, count &amp; report) various DCS events occuring on <a href="Wrapper.Unit.html">Wrapper.Unit</a>s.</p>
<p><strong>Actions</strong> - ACT_ACCOUNT_ classes <strong>account for</strong> (detect, count &amp; report) various DCS events occurring on <a href="Wrapper.Unit.html">Wrapper.Unit</a>s.</p>
</p></div>
</div>
</div>
@@ -1670,7 +1670,7 @@ The default range of the scores granted is a value between 0 and 10. The default
<p><img src="..\Presentations\SCORING\Dia9.JPG" alt="Banner Image"/></p>
<p>Various <a href="Zone.html">Zone</a>s can be defined for which scores are also granted when objects in that <a href="Zone.html">Zone</a> are destroyed.
<p>Various <a href="Core.Zone.html">Core.Zone</a>s can be defined for which scores are also granted when objects in that <a href="Core.Zone.html">Core.Zone</a> are destroyed.
This is <strong>specifically useful</strong> to designate <strong>scenery targets on the map</strong> that will generate points when destroyed.</p>
<p>With a small change in MissionScripting.lua, the scoring results can also be logged in a <strong>CSV file</strong>.
@@ -1773,11 +1773,11 @@ For example, this can be done as follows:</p>
<h1>Define destruction zones that will give extra scores:</h1>
<p>Define zones of destruction. Any object destroyed within the zone of the given category will give extra points.
Use the method <a href="##(SCORING).AddZoneScore">SCORING.AddZoneScore</a>() to add a <a href="Zone.html">Zone</a> for additional scoring.
Use the method <a href="##(SCORING).RemoveZoneScore">SCORING.RemoveZoneScore</a>() to remove a <a href="Zone.html">Zone</a> for additional scoring.
There are interesting variations that can be achieved with this functionality. For example, if the <a href="Zone.html">Zone</a> is a <a href="Core.Zone.html##(ZONE_UNIT)">Core.Zone#ZONE_UNIT</a>,
then the zone is a moving zone, and anything destroyed within that <a href="Zone.html">Zone</a> will generate points.
The other implementation could be to designate a scenery target (a building) in the mission editor surrounded by a <a href="Zone.html">Zone</a>,
Use the method <a href="##(SCORING).AddZoneScore">SCORING.AddZoneScore</a>() to add a <a href="Core.Zone.html">Core.Zone</a> for additional scoring.
Use the method <a href="##(SCORING).RemoveZoneScore">SCORING.RemoveZoneScore</a>() to remove a <a href="Core.Zone.html">Core.Zone</a> for additional scoring.
There are interesting variations that can be achieved with this functionality. For example, if the <a href="Core.Zone.html">Core.Zone</a> is a <a href="Core.Zone.html##(ZONE_UNIT)">Core.Zone#ZONE_UNIT</a>,
then the zone is a moving zone, and anything destroyed within that <a href="Core.Zone.html">Core.Zone</a> will generate points.
The other implementation could be to designate a scenery target (a building) in the mission editor surrounded by a <a href="Core.Zone.html">Core.Zone</a>,
just large enough around that building.</p>
<h1>Add extra Goal scores upon an event or a condition:</h1>
@@ -1983,7 +1983,7 @@ Various methods exist to configure:</p>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SCORING).AddZoneScore">SCORING:AddZoneScore(ScoreZone, Score)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Add a <a href="Zone.html">Zone</a> to define additional scoring when any object is destroyed in that zone.</p>
<p>Add a <a href="Core.Zone.html">Core.Zone</a> to define additional scoring when any object is destroyed in that zone.</p>
</td>
</tr>
<tr class="w3-border">
@@ -2127,7 +2127,7 @@ Various methods exist to configure:</p>
<tr class="w3-border">
<td class="name w3-half w3-container" style="word-wrap: break-word"><p><a href="##(SCORING).RemoveZoneScore">SCORING:RemoveZoneScore(ScoreZone)</a></p></td>
<td class="summary w3-half w3-container" style="word-wrap: break-word">
<p>Remove a <a href="Zone.html">Zone</a> for additional scoring.</p>
<p>Remove a <a href="Core.Zone.html">Core.Zone</a> for additional scoring.</p>
</td>
</tr>
<tr class="w3-border">
@@ -3094,7 +3094,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(SCORING).penaltyoncoalitionchange" ><strong>SCORING.penaltyoncoalitionchange</strong></a>
@@ -3105,7 +3105,7 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(SCORING).penaltyonfratricide" ><strong>SCORING.penaltyonfratricide</strong></a>
@@ -3457,10 +3457,10 @@ then the old <a href="Wrapper.Unit.html">Wrapper.Unit</a> will be replaced with
<h2><a id="#(SCORING).AddZoneScore" ><strong>SCORING:AddZoneScore(ScoreZone, Score)</strong></a></h2>
</div>
<p>Add a <a href="Zone.html">Zone</a> to define additional scoring when any object is destroyed in that zone.</p>
<p>Add a <a href="Core.Zone.html">Core.Zone</a> to define additional scoring when any object is destroyed in that zone.</p>
<p>Note that if a <a href="Zone.html">Zone</a> with the same name is already within the scoring added, the <a href="Zone.html">Zone</a> (type) and Score will be replaced!
<p>Note that if a <a href="Core.Zone.html">Core.Zone</a> with the same name is already within the scoring added, the <a href="Core.Zone.html">Core.Zone</a> (type) and Score will be replaced!
This allows for a dynamic destruction zone evolution within your mission.</p>
<div id= "#Functions##AddZoneScore" class="w3-show w3-white">
@@ -3479,7 +3479,7 @@ This allows for a dynamic destruction zone evolution within your mission.</p>
</div>
<div class="w3-half">
<p>The <a href="Zone.html">Zone</a> which defines the destruction score perimeters.
<p>The <a href="Core.Zone.html">Core.Zone</a> which defines the destruction score perimeters.
Note that a zone can be a polygon or a moving zone.</p>
</div>
@@ -3965,10 +3965,10 @@ ScoringObject:OpenCSV( "Player Scores" )</code></pre>
<h2><a id="#(SCORING).RemoveZoneScore" ><strong>SCORING:RemoveZoneScore(ScoreZone)</strong></a></h2>
</div>
<p>Remove a <a href="Zone.html">Zone</a> for additional scoring.</p>
<p>Remove a <a href="Core.Zone.html">Core.Zone</a> for additional scoring.</p>
<p>The scoring will search if any <a href="Zone.html">Zone</a> is added with the given name, and will remove that zone from the scoring.
<p>The scoring will search if any <a href="Core.Zone.html">Core.Zone</a> is added with the given name, and will remove that zone from the scoring.
This allows for a dynamic destruction zone evolution within your mission.</p>
<div id= "#Functions##RemoveZoneScore" class="w3-show w3-white">
@@ -3987,7 +3987,7 @@ This allows for a dynamic destruction zone evolution within your mission.</p>
</div>
<div class="w3-half">
<p>The <a href="Zone.html">Zone</a> which defines the destruction score perimeters.
<p>The <a href="Core.Zone.html">Core.Zone</a> which defines the destruction score perimeters.
Note that a zone can be a polygon or a moving zone.</p>
</div>
@@ -5614,7 +5614,7 @@ The scale magnifies the scores given to the players.</p>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(SCORING).penaltyoncoalitionchange" ><strong>SCORING.penaltyoncoalitionchange</strong></a>
@@ -5625,7 +5625,7 @@ The scale magnifies the scores given to the players.</p>
<div>
<div class="w3-card-2 w3-padding-small w3-margin-top">
#boolean
<a id="#(SCORING).penaltyonfratricide" ><strong>SCORING.penaltyonfratricide</strong></a>