setGroupOwner: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " +" to " ") |
Lou Montana (talk | contribs) m (Text replacement - "</dd> <dt><dt>" to "</dd> <dt><dt>") |
||
| Line 31: | Line 31: | ||
In {{arma3}} 1.48, setGroupOwner does NOT work if group has no units | In {{arma3}} 1.48, setGroupOwner does NOT work if group has no units | ||
</dd> | </dd> | ||
<dt><dt> | <dt><dt> | ||
<dd class="notedate">Posted on April 28, 2020 - 22:58 (UTC)</dd> | <dd class="notedate">Posted on April 28, 2020 - 22:58 (UTC)</dd> | ||
| Line 38: | Line 39: | ||
[[lock|Locking]] the vehicle during transfer can counter this behavior. | [[lock|Locking]] the vehicle during transfer can counter this behavior. | ||
</dd> | </dd> | ||
<dt><dt> | <dt><dt> | ||
<dd class="notedate">Posted on April 30, 2020 - 21:15 (UTC)</dd> | <dd class="notedate">Posted on April 30, 2020 - 21:15 (UTC)</dd> | ||
| Line 44: | Line 46: | ||
Using '''setGroupOwner''' may cause AI to have their loadout removed. This typically occurs when transferring multiple groups in sequence without delay. This occurs on seemingly random AI in groups. The simple but finicky solution to this is to add a sufficient delay between the transfer of groups. Alternatively, one could have the units' loadouts saved and then reloaded if the unit is shown as naked. Both of these methods may be combined as well. | Using '''setGroupOwner''' may cause AI to have their loadout removed. This typically occurs when transferring multiple groups in sequence without delay. This occurs on seemingly random AI in groups. The simple but finicky solution to this is to add a sufficient delay between the transfer of groups. Alternatively, one could have the units' loadouts saved and then reloaded if the unit is shown as naked. Both of these methods may be combined as well. | ||
</dd> | </dd> | ||
<dt><dt> | <dt><dt> | ||
<dd class="notedate">Posted on April 30, 2020 - 21:58 (UTC)</dd> | <dd class="notedate">Posted on April 30, 2020 - 21:58 (UTC)</dd> | ||
Revision as of 10:00, 11 June 2021
Description
- Description:
- Description needed
- Groups:
- Multiplayer
Syntax
- Syntax:
- Syntax needed
- Parameters:
- group: Group -
- clientID: Number - the machine network ID of the new owner.
- Return Value:
- Boolean
Examples
- Example 1:
_localityChanged = _someGroup setGroupOwner (owner _playerObject);
Additional Information
- See also:
- ownersetOwnergroupOwner
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 July 30, 2015 - 12:49 (UTC)
- IT07
- In Arma 3 1.48, setGroupOwner does NOT work if group has no units
- Posted on April 28, 2020 - 22:58 (UTC)
- TMZulu
-
The setGroupOwner command will dismount the unit leader of a vehicle if the vehicle is stationary, likely due to the dummy waypoint used in the transfer.
Locking the vehicle during transfer can counter this behavior. - Posted on April 30, 2020 - 21:15 (UTC)
- TMZulu
- Using setGroupOwner may cause AI to have their loadout removed. This typically occurs when transferring multiple groups in sequence without delay. This occurs on seemingly random AI in groups. The simple but finicky solution to this is to add a sufficient delay between the transfer of groups. Alternatively, one could have the units' loadouts saved and then reloaded if the unit is shown as naked. Both of these methods may be combined as well.
- Posted on April 30, 2020 - 21:58 (UTC)
- TMZulu
- Locality dependent commands such as forceSpeed will no longer work after transfer and must be reapplied on the owning client.