clientOwner: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Arma[ _]3(\|.*)]]" to "{{GameCategory|arma3|Scripting Commands}}") |
Lou Montana (talk | contribs) m (Text replacement - "\{\{GameCategory\|(arma[0123])\|New[ _]Scripting[ _]Commands[ _]List\}\}" to "{{GameCategory|$1|New Scripting Commands}}") |
||
Line 28: | Line 28: | ||
<h3 style="display:none">Bottom Section</h3> | <h3 style="display:none">Bottom Section</h3> | ||
{{GameCategory|arma3| | {{GameCategory|arma3|New Scripting Commands}} | ||
{{GameCategory|arma3|Scripting Commands}} | {{GameCategory|arma3|Scripting Commands}} | ||
Revision as of 21:58, 12 January 2021
Description
- Description:
- Returns the machine network ID of the client executing the command.
- Groups:
- Multiplayer
Syntax
- Syntax:
- clientOwner
- Return Value:
- Number
Examples
- Example 1:
_id = clientOwner;
Additional Information
- See also:
- ownergroupOwneronPlayerConnectedonPlayerDisconnectedgetClientStategetClientStateNumberadminremoteExecutedOwner
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
Bottom Section
Notes
Bottom Section
- Posted on February 17, 2016 - 18:54 (UTC)
- Killzone Kid
- On hosted server there could be some inconsistency between clientOwner, owner and object creator id, especially in missions started from save. On the dedicated server this command however works reliably.