From Bohemia Interactive Community
Revision as of 23:09, 13 May 2023 by Lou Montana (talk | contribs) (Text replacement - ">Posted on July ([0-9]{2})[ a-zA-Z]*, ([0-9]{4})" to ">Posted on $2-07-$1")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Hover & click on the images for description


Changes the ownership of a group (and all its units) to a given client. The group leader must not be a player. This command only works when called from the server. Returns true if locality was changed. For agents use setOwner command.


group setGroupOwner clientID
group: Group -
clientID: Number - the machine network ID of the new owner.
Return Value:


Example 1:
_localityChanged = _someGroup setGroupOwner (owner _playerObject);

Additional Information

See also:
owner setOwner groupOwner


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 2015-07-30 - 12:49 (UTC)
In Arma 3 1.48, setGroupOwner does NOT work if group has no units
Posted on 2020-04-28 - 22:58 (UTC)
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 2020-04-30 - 21:15 (UTC)
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 2020-04-30 - 21:58 (UTC)
Locality dependent commands such as forceSpeed will no longer work after transfer and must be reapplied on the owning client.