onPlayerConnected: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\|gr([0-9]+) = " to "|gr$1= ") |
Lou Montana (talk | contribs) m (Text replacement - "{{uc:{{PAGENAME}}}} " to "") |
||
| Line 51: | Line 51: | ||
{{GameCategory|ofpe|Scripting Commands}} | {{GameCategory|ofpe|Scripting Commands}} | ||
{{GameCategory|arma1|Scripting Commands}} | {{GameCategory|arma1|Scripting Commands}} | ||
Revision as of 18:19, 8 June 2021
Description
- Description:
- Description needed
- Multiplayer:
- The statement is executed only on the server, not on the joining player's computer, nor on any other client.
This happens even if onPlayerConnected was issued on all machines.
Note that there is a player with the _name called __SERVER__ which will also connect to a multiplayer game, executing code. - Groups:
- MultiplayerEvent Handlers
Syntax
- Syntax:
- Syntax needed
- Parameters:
- code: String or Code
- Return Value:
- Return value needed
Examples
- Example 1:
onPlayerConnected "[_id, _name] execVM ""PlayerConnected.sqf""";- Example 2:
onPlayerConnected { diag_log [_id, _uid, _name] };- Example 3:
- From Arma 3 v1.49:
onPlayerConnected { somevar = random 123; _owner publicVariableClient "somevar"; // this will set somevar // joining player PC to a random value }; - Example 4:
- From Arma 3 v1.49:
onPlayerConnected { isJip = _jip; _owner publicVariableClient "isJip" }; // Each player will now have variable isJip containing individual JIP info
Additional Information
- See also:
- onPlayerDisconnecteddidJIPdidJIPOwner
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