mirror of
https://github.com/FlightControl-Master/MOOSE_DOCS.git
synced 2025-08-15 10:37:49 +00:00
MOOSE generated documentation [skip ci]
This commit is contained in:
@@ -1707,7 +1707,7 @@ And there is NO cargo object actually declared within the script! However, if yo
|
||||
<li>is of type <code>Workmaterials</code></li>
|
||||
<li>will report when a carrier is within 500 meters</li>
|
||||
<li>will board to carriers when the carrier is within 500 meters from the cargo object</li>
|
||||
<li>will dissapear when the cargo is within 25 meters from the carrier during boarding</li>
|
||||
<li>will disappear when the cargo is within 25 meters from the carrier during boarding</li>
|
||||
</ul>
|
||||
|
||||
<p>So the overall syntax of the #CARGO naming tag and arguments are:</p>
|
||||
@@ -1737,7 +1737,7 @@ And there is NO cargo object actually declared within the script! However, if yo
|
||||
<li>is of type <code>Workmaterials</code></li>
|
||||
<li>will report when a carrier is within 500 meters</li>
|
||||
<li>will board to carriers when the carrier is within 500 meters from the cargo object</li>
|
||||
<li>will dissapear when the cargo is within 25 meters from the carrier during boarding</li>
|
||||
<li>will disappear when the cargo is within 25 meters from the carrier during boarding</li>
|
||||
</ul>
|
||||
|
||||
<p>So the overall syntax of the #CARGO naming tag and arguments are:</p>
|
||||
|
||||
Reference in New Issue
Block a user