setOwner: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
(Created page with "{{Command|= Comments ____________________________________________________________________________________________ | arma2oa |= Game name |1.61|= Game version __________________...")
 
(WOOPS)
(21 intermediate revisions by 9 users not shown)
Line 4: Line 4:
| arma2oa |= Game name
| arma2oa |= Game name


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


| From server machine, change the ownership of an object to a given client. Returns true if locality was changed. |= Description
| From server machine, change the ownership of an object to a given client. Returns [[true]] if locality was changed.<br>
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.<br>
To transfer ownership of all AI units in a group properly, use [[setGroupOwner]] instead.
 
|= Description
____________________________________________________________________________________________
____________________________________________________________________________________________


| [[Object]] '''setOwner''' [[Number]] |= Syntax
| object '''setOwner''' clientID |= Syntax
 
|p1= object: [[Object]] - |= PARAMETER1
 
|p2= clientID: [[Number]] - clientID of the new [[owner]] |= PARAMETER2


| [[Boolean]] |= Return value
| [[Boolean]] |= Return value
____________________________________________________________________________________________
____________________________________________________________________________________________
   
   
|x1= <pre>_someObject setOwner 12;</pre> |= Example 1
|x1= <code>_someObject [[setOwner]] 12;</code> |= Example 1


|x2= <pre>_someObject setOwner (owner _playerObject);</pre> |= Example 2
|x2= <code>_someObject [[setOwner]] ([[owner]] _playerObject);</code> |= Example 2
____________________________________________________________________________________________
____________________________________________________________________________________________


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


}}
}}
Line 35: Line 46:
[[Category:ArmA 2 OA: New Scripting Commands List|{{uc:{{PAGENAME}}}}]]
[[Category:ArmA 2 OA: New Scripting Commands List|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
[[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]]
<!-- CONTINUE Notes -->
<dl class="command_description">
<dd class="notedate">Posted on January 7, 2015 - 18:28 (UTC)</dd>
<dt class="note">[[User:Killzone Kid|Killzone Kid]]</dt>
<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
</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>
</dl>
<!-- 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.