setOwner
Jump to navigation
Jump to search
Description
- Description:
- Description needed
- Groups:
- Multiplayer
Syntax
- Syntax:
- Syntax needed
- Parameters:
- object: Object -
- clientID: Number - the machine network ID of the new owner.
- Return Value:
- Return value needed
Examples
Additional Information
- See also:
- See also needed
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 January 7, 2015 - 18:28 (UTC)
- Killzone Kid
- The ownership can only be given from server to client. For some reason the server cannot return ownership back with this command. This is fixed in Arma 3 1.40
- Posted on August 22, 2017 - 18:56 (UTC)
- Demellion
-
NOTE: There are some interesting behaviour about the specific owner digits like 0 -2 and 2:
1. Any mission objects (generated from SQM) initially have 0 owner state, but it is not local to ANYONE (0) like it is expected to be, but actually only to a SERVER (2). You can't make any object owner to be 0 once it was changed.
2. Trying to change ownership to any negative digit will always result in attempt to transfer ownership to SERVER (2). Once it is unit (non-agent) it will fail and revert* to initial ownership.
3. *Changing ownership of a unit (non-agent) actually gives a result for a brief time after this action is performed. What actually happens next - ownership is getting reverted with a message to RPT of a server. This can be seen by reading results of (owner _object) in really fast cycle. - Posted on February 12, 2019 - 01:15 (UTC)
- jonpas
- Prints RPT warning "setGroupOwner should be used" as soon as there is one unit inside the vehicle, but performs the action successfully.