setOwner: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
No edit summary
m (Fix typo)
Line 76: Line 76:
<dt class="note">[[User:jonpas|jonpas]]</dt>
<dt class="note">[[User:jonpas|jonpas]]</dt>
<dd class="note">
<dd class="note">
Prints RPT warning "setGroupOwner should be used" as soon as there is at one unit inside the vehicle, but performs the action successfully.
Prints RPT warning "setGroupOwner should be used" as soon as there is one unit inside the vehicle, but performs the action successfully.
</dd>
</dd>
</dl>
</dl>
<!-- DISCONTINUE Notes -->
<!-- DISCONTINUE Notes -->

Revision as of 02:16, 12 February 2019

Hover & click on the images for description

Description

Description:
From server machine, change the ownership of an object to a given client. Returns true if locality was changed.
Since Arma 3 v1.40, this command should not be used to transfer ownership of units with AI (agents are an exception to this rule). Using command in an unintended way will log a message to .rpt file.
To transfer ownership of all AI units in a group properly, use setGroupOwner instead.
Groups:
Uncategorised

Syntax

Syntax:
object setOwner clientID
Parameters:
object: Object -
clientID: Number - clientID of the new owner
Return Value:
Boolean

Examples

Example 1:
_someObject setOwner 12;
Example 2:
_someObject setOwner (owner _playerObject);

Additional Information

See also:
ownersetGroupOwnergroupOwnerdidJIPOwner

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

Notes

Bottom Section

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.