unitReady: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (<pre> to <code> and tidy of note)
m (Text replacement - ">Posted on November ([0-9]{2})[ a-zA-Z]*, ([0-9]{4})" to ">Posted on $2-11-$1")
 
(66 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Command|= Comments
{{RV|type=command
____________________________________________________________________________________________


| ofp |= Game name
|game1= ofp
|version1= 1.00


|1.00|= Game version
|game2= ofpe
____________________________________________________________________________________________
|version2= 1.00


| Check if the unit is ready. Unit is busy when it is given some command like [[move]], until the command is finished. |= Description
|game3= arma1
____________________________________________________________________________________________
|version3= 1.00


| [[Boolean]] <nowiki>=</nowiki> '''unitReady''' unitName|= Syntax
|game4= arma2
|version4= 1.00


|p1= unitName: [[Object]] |= Parameter 1
|game5= arma2oa
|version5= 1.50


| [[Boolean]] |= Return value
|game6= tkoh
____________________________________________________________________________________________
|version6= 1.00
 
|x1= <code>_it = [[unitReady]] _soldierOne;</code> |= Example 1
____________________________________________________________________________________________


| |= See also
|game7= arma3
|version7= 0.50


|gr1= Unit Control
|descr= Check if the unit is ready. Unit is busy when it is given some command like [[move]], until the command is finished.
|s1= [[unitReady]] unitName
|p1= unitName: [[Object]]
|r1= [[Boolean]]
|x1= <sqf>private _it = unitReady _soldierOne;</sqf>
|seealso= [[move]]
}}
}}


<h3 style="display:none">Notes</h3>
<dl class="command_description">
<dl class="command_description">
<!-- Note Section BEGIN -->


<dd class="notedate">Posted on August 26, 2010
<dt><dt>
<dt class="note">'''[[User:Rübe|Rübe]]'''
<dd class="notedate">Posted on 2010-08-26</dd>
<dt class="note">[[User:Rübe|Rübe]]</dt>
<dd class="note">
<dd class="note">
Keep in mind that a) dead units are [[unitReady]] and b) that it takes a while until it get's known to group members that a unit is not [[alive]] anymore, which leads to c) the current [[leader]] of a group might be actually dead (until another group member takes command).<br>
Keep in mind that a) dead units are [[unitReady]] and b) that it takes a while until it get's known to group members that a unit is not [[alive]] anymore, which leads to c) the current [[leader]] of a group might be actually dead (until another group member takes command).<br>
Why this is important? I'll give you an example: if you're using [[unitReady]] as a condition inside one of your fsm to advance whatever the fsm/group is doing, you really might wanna check that this unit is actually still alive. Otherwise you might end up with really fast and nasty loops in your fsm, eventually accompanied by a stream of radio commands that will last until finally a living leader is in command again.. and that could take a while... nasty, I tell you :)
Why this is important? I'll give you an example: if you're using [[unitReady]] as a condition inside one of your fsm to advance whatever the fsm/group is doing, you really might wanna check that this unit is actually still alive. Otherwise you might end up with really fast and nasty loops in your fsm, eventually accompanied by a stream of radio commands that will last until finally a living leader is in command again.. and that could take a while... nasty, I tell you :)
<dt><dt>
<dd class="notedate">Posted on 2011-01-17</dd>
<dt class="note">[[User:Rübe|Rübe]]</dt>
<dd class="note">
Regarding vehicles, there is only one single unit (from the vehicle crew) whose unitReady-status is affected by giving that vehicle (or that unit) commands.
While it is the driver unit for a truck, it is the gunner unit for a mg-jeep or the commander for a tank. Generally it is always the unit "in control" of the vehicle.
(because it is only that unit, that is seen as "full unit" to the "outside world". Only he can be adressed with commands.)<br>


In consequence you can't just send vehicles around and check if they've arrived with something like:
<sqf>waitUntil { unitReady driver _vehicle }; // don't do this!</sqf>


<dt class="note">'''[[User:Rübe|Rübe]]'''
Because it is ''not guaranteed that the driver is in command of the vehicle'' and only that unit will have its unitReady status affected.<br>
So in conclusion, '''if you need to check if a vehicle is ready''', try something like this:
<sqf>
_vehicleReady = {
private ["_veh", "_ready"];
_veh = _this;
_ready = true;
{
if (not isNull _x) then
{
_ready = _ready && (unitReady _x);
};
} forEach [
commander _veh,
gunner _veh,
driver _veh
];
_ready
};
</sqf>
<dt><dt>
<dd class="notedate">Posted on 2015-11-21 - 22:40 (UTC)</dd>
<dt class="note">[[User:Kastenbier|Kastenbier]]</dt>
<dd class="note">
<dd class="note">
Regarding vehicles, there is only one single unit (from the vehicle crew) whose unitReady-status is affected by giving that vehicle (or that unit) commands. While it's the driver unit for a truck, it is the gunner unit for a mg-jeep or the commander for a tank. Generally it's always the unit "in control" of the vehicle. (because it's only that unit, that is seen as "full unit" to the "outside world". Only he can be adressed with commands.)<br>
To check readiness of a vehicle, don't check its crew, driver, gunner, commander, etc., but the vehicle itself, e.g.:
In consequence you can't just send vehicles around and check if they've arrived with something like:
<sqf>unitReady _yourVehicle;</sqf>
 
Only tested 11/21/2015 by me with A2 1.63.131129 and A3 1.52.132676 but possibly true since 1964. :P
  waitUntil{(unitReady (driver _vehicle))}; // don't do this!
</dd>


Because it's ''not guaranteed, that the driver is in command of the vehicle'' and only that unit will have it's unitReady status affected.<br>
So in conclusion, '''if you need to check if a vehicle is ready''', try something like this:<pre>_vehicleReady = {
    private ["_veh", "_ready"];
    _veh = _this;
    _ready = true;
    {
        if (!(isNull _x)) then
        {
            _ready = _ready && (unitReady _x);
        };
    } forEach [
        (commander _veh),
        (gunner _veh),
        (driver _veh)
    ];
    _ready
};</pre>
<!-- Note Section END -->
</dl>
</dl>
<h3 style="display:none">Bottom Section</h3>
[[Category:Scripting Commands|UNITREADY]]
[[Category:Scripting Commands OFP 1.96|UNITREADY]]
[[Category:Scripting Commands OFP 1.46|UNITREADY]]
[[Category:Scripting Commands ArmA|UNITREADY]]
[[Category:Scripting Commands ArmA2|UNITREADY]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]

Latest revision as of 23:13, 13 May 2023

Logo A0.png1.00ofpe logo.png1.00Logo A1 black.png1.00Logo A2.png1.00A2 OA Logo.png1.50tkoh logo small.png1.00Arma 3 logo black.png0.50
Hover & click on the images for description

Description

Description:
Check if the unit is ready. Unit is busy when it is given some command like move, until the command is finished.
Groups:
Unit Control

Syntax

Syntax:
unitReady unitName
Parameters:
unitName: Object
Return Value:
Boolean

Examples

Example 1:
private _it = unitReady _soldierOne;

Additional Information

See also:
move

Notes

Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
Posted on 2010-08-26
Rübe
Keep in mind that a) dead units are unitReady and b) that it takes a while until it get's known to group members that a unit is not alive anymore, which leads to c) the current leader of a group might be actually dead (until another group member takes command).
Why this is important? I'll give you an example: if you're using unitReady as a condition inside one of your fsm to advance whatever the fsm/group is doing, you really might wanna check that this unit is actually still alive. Otherwise you might end up with really fast and nasty loops in your fsm, eventually accompanied by a stream of radio commands that will last until finally a living leader is in command again.. and that could take a while... nasty, I tell you :)
Posted on 2011-01-17
Rübe
Regarding vehicles, there is only one single unit (from the vehicle crew) whose unitReady-status is affected by giving that vehicle (or that unit) commands. While it is the driver unit for a truck, it is the gunner unit for a mg-jeep or the commander for a tank. Generally it is always the unit "in control" of the vehicle. (because it is only that unit, that is seen as "full unit" to the "outside world". Only he can be adressed with commands.)
In consequence you can't just send vehicles around and check if they've arrived with something like:
waitUntil { unitReady driver _vehicle }; // don't do this!
Because it is not guaranteed that the driver is in command of the vehicle and only that unit will have its unitReady status affected.
So in conclusion, if you need to check if a vehicle is ready, try something like this:
_vehicleReady = { private ["_veh", "_ready"]; _veh = _this; _ready = true; { if (not isNull _x) then { _ready = _ready && (unitReady _x); }; } forEach [ commander _veh, gunner _veh, driver _veh ]; _ready };
Posted on 2015-11-21 - 22:40 (UTC)
Kastenbier
To check readiness of a vehicle, don't check its crew, driver, gunner, commander, etc., but the vehicle itself, e.g.:
unitReady _yourVehicle;
Only tested 11/21/2015 by me with A2 1.63.131129 and A3 1.52.132676 but possibly true since 1964. :P
Retrieved from "https://community.bistudio.com/wiki?title=unitReady&oldid=341160"