setOwner: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
No edit summary
(WOOPS)
(4 intermediate revisions by 3 users not shown)
Line 5: Line 5:


|1.62|= Game version
|1.62|= Game version
|exec= server|=
____________________________________________________________________________________________
____________________________________________________________________________________________


Line 29: Line 31:
____________________________________________________________________________________________
____________________________________________________________________________________________


| [[owner]] [[groupOwner]] |= See also
| [[owner]], [[setGroupOwner]], [[groupOwner]], [[didJIPOwner]] |= See also


}}
}}
Line 55: Line 57:
<dd class="note">
<dd class="note">
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
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
</dd>
</dl>
<dl class="command_description">
<dd class="notedate">Posted on August 22, 2017 - 18:56 (UTC)</dd>
<dt class="note">[[User:Demellion|Demellion]]</dt>
<dd class="note">
'''NOTE''': There are some interesting behaviour about the specific owner digits like '''0''' '''-2''' and '''2''': <br>
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. <br>
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.<br>
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. 
</dd>
</dd>
</dl>
</dl>
<!-- DISCONTINUE Notes -->
<!-- DISCONTINUE Notes -->

Revision as of 18:30, 22 August 2017

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 display an on-screen warning and 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.