Difference between revisions of "onPlayerConnected"

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Inverted _jip and _owner to reflect same order as PlayerConnected)
m (Text replacement - " {3,}\|" to " |")
 
(28 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
{{Command|= Comments
+
{{Command
−
____________________________________________________________________________________________
 
  
−
| arma |= Game name
+
| arma1
  
−
|1.00|= Game version
+
|1.00
−
|exec= server|= Exec
+
 
−
____________________________________________________________________________________________
+
|gr1 = Multiplayer
 +
 
 +
|gr2= Event Handlers
 +
 
 +
|serverExec= server |Exec=
  
 
| This command will execute attached code whenever a player is connected to a MP session. The code will receive a number of special variables:
 
| This command will execute attached code whenever a player is connected to a MP session. The code will receive a number of special variables:
−
 
 
* '''_id''': [[Number]] - is the unique DirectPlay ID. Quite useless as the number is too big for in-built string representation and gets rounded. It is also the same id used for user placed markers.
 
* '''_id''': [[Number]] - is the unique DirectPlay ID. Quite useless as the number is too big for in-built string representation and gets rounded. It is also the same id used for user placed markers.
 +
* '''_uid''': [[String]] - is [[getPlayerUID]] of the joining player. In Arma 3 it is also the same as Steam ID.
 
* '''_name''': [[String]] - is [[profileName]] of the joining player.
 
* '''_name''': [[String]] - is [[profileName]] of the joining player.
−
* '''_uid''': [[String]] - is [[getPlayerUID]] of the joining player. In Arma 3 it is also the same as Steam ID.
+
* '''_jip''': (''since Arma 3 v1.49'') [[Boolean]] - is a flag that indicates whether or not the player joined after the mission has started ('''J'''oined '''I'''n '''P'''rogress). [[true]] when the player is [[Multiplayer Scripting#Join In Progress|JIP]], otherwise [[false]].
−
* '''_jip''': (''since Arma 3 v1.49'') [[Boolean]] - is a flag that indicates whether or not the player joined after the mission has started ('''J'''oined '''I'''n '''P'''rogress). [[true]] - when the player is JIP, otherwise [[false]].
 
 
* '''_owner''': (''since Arma 3 v1.49'') [[Number]] - is [[owner]] id of the joining player. Can be used for kick or ban purposes or just for [[publicVariableClient]].
 
* '''_owner''': (''since Arma 3 v1.49'') [[Number]] - is [[owner]] id of the joining player. Can be used for kick or ban purposes or just for [[publicVariableClient]].
−
{{Informative|Since '''Arma 3''' ''v1.57'' a stackable version of this EH is available: [[Arma_3:_Event_Handlers/addMissionEventHandler#PlayerConnected|PlayerConnected]]}}
+
* '''_idstr''': (''since Arma 3 v1.95'') [[String]] - same as <tt>_id</tt> but in string format, so could be exactly compared to [[allMapMarkers | user marker]] ids.<br><br>
−
{{Feature arma3|In order to keep compatibility between official and community content the functions [[BIS_fnc_addStackedEventHandler]] and [[BIS_fnc_removeStackedEventHandler]] should be used instead.}}
+
{{Feature|arma3 | Since '''Arma 3''' ''v1.57'' a stackable MissionEventHandler is available and should be used: [[Arma_3:_Event_Handlers/addMissionEventHandler#PlayerConnected|PlayerConnected]].<br>
−
|= Description
+
Before that, the functions [[BIS_fnc_addStackedEventHandler]] and [[BIS_fnc_removeStackedEventHandler]] should be used instead in order to keep compatibility between official and community content.}}
−
____________________________________________________________________________________________
 
  
−
| '''onPlayerConnected''' code |= Syntax
+
| [[onPlayerConnected]] code
  
−
|p1= code: [[String]] or [[Code]] |= Parameter 1
+
|p1= code: [[String]] or [[Code]]
  
−
| [[Nothing]] |= Return value
+
| [[Nothing]]
  
−
____________________________________________________________________________________________
+
|x1= <code>[[onPlayerConnected]] "[_id, _name] [[execVM]] ""PlayerConnected.sqf""";</code>
−
|x1= <code>[[onPlayerConnected]] "[_id, _name] [[execVM]] ""PlayerConnected.sqf""";</code> |= Example 1
+
 
−
|x2= <code>[[onPlayerConnected]] {[[diag_log]] [_id, _uid, _name]};</code> |= Example 2
+
|x2= <code>[[onPlayerConnected]] { [[diag_log]] [_id, _uid, _name] };</code>
−
|x3= From Arma 3 v1.49: <code>[[onPlayerConnected]] {
+
 
 +
|x3= From '''{{arma3}}''' v1.49:
 +
<code>[[onPlayerConnected]] {
 
somevar = [[random]] 123;
 
somevar = [[random]] 123;
 
_owner [[publicVariableClient]] "somevar";
 
_owner [[publicVariableClient]] "somevar";
−
//this will set somevar on
+
{{cc|this will set somevar}}
−
//joining player PC to a random value  
+
{{cc|joining player PC to a random value}}
−
};</code>|= Example 2
+
};</code>
  
−
|x4= From Arma 3 v1.49: <code>[[onPlayerConnected]] {isJip = _jip; _owner [[publicVariableClient]] "isJip"};
+
|x4= From '''{{arma3}}''' v1.49:
−
//Each player will now have variable isJip containing individual JIP info</code>|= Example 2
+
<code>[[onPlayerConnected]] { isJip = _jip; _owner [[publicVariableClient]] "isJip" };
 +
{{cc|Each player will now have variable isJip containing individual JIP info}}</code>
  
 
|mp= The ''statement'' is executed only on the server, not on the joining player's computer, nor on any other client.<br>
 
|mp= The ''statement'' is executed only on the server, not on the joining player's computer, nor on any other client.<br>
 
This happens even if '''onPlayerConnected''' was issued on all machines. <br>
 
This happens even if '''onPlayerConnected''' was issued on all machines. <br>
−
Note that there is a player with the '''_name''' called __SERVER__ which will also connect to a multiplayer game, executing ''code''. |=
+
Note that there is a player with the '''_name''' called __SERVER__ which will also connect to a multiplayer game, executing ''code''. |Multiplayer=
−
 
 
−
| [[onPlayerDisconnected]], [[didJIP]], [[didJIPOwner]]|= See also
 
  
 +
| [[onPlayerDisconnected]], [[didJIP]], [[didJIPOwner]]
 
}}
 
}}
  
−
<h3 style="display:none">Notes</h3>
 
−
<dl class="command_description">
 
−
<!-- Note Section BEGIN -->
 
−
 
−
<!-- Note Section END -->
 
−
</dl>
 
−
 
−
<h3 style="display:none">Bottom Section</h3>
 
  
−
[[Category:Scripting Commands|ONPLAYERCONNECTED]]
+
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
−
[[Category:Scripting Commands OFP Elite |ONPLAYERCONNECTED]]
+
{{GameCategory|ofpe|Scripting Commands}}
−
[[Category:Scripting Commands ArmA|ONPLAYERCONNECTED]]
+
{{GameCategory|arma1|Scripting Commands}}
−
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
+
{{GameCategory|arma2|Scripting Commands}}
−
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
+
{{GameCategory|arma3|Scripting Commands}}
−
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]
+
{{GameCategory|tkoh|Scripting Commands}}
−
[[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]]
 

Latest revision as of 17:38, 18 January 2021

Introduced with Armed Assault version 1.001.00This scripting command must be executed on the server to work properly in multiplayer
Hover & click on the images for descriptions

Description

Description:
This command will execute attached code whenever a player is connected to a MP session. The code will receive a number of special variables:
  • _id: Number - is the unique DirectPlay ID. Quite useless as the number is too big for in-built string representation and gets rounded. It is also the same id used for user placed markers.
  • _uid: String - is getPlayerUID of the joining player. In Arma 3 it is also the same as Steam ID.
  • _name: String - is profileName of the joining player.
  • _jip: (since Arma 3 v1.49) Boolean - is a flag that indicates whether or not the player joined after the mission has started (Joined In Progress). true when the player is JIP, otherwise false.
  • _owner: (since Arma 3 v1.49) Number - is owner id of the joining player. Can be used for kick or ban purposes or just for publicVariableClient.
  • _idstr: (since Arma 3 v1.95) String - same as _id but in string format, so could be exactly compared to user marker ids.

Arma 3
Since Arma 3 v1.57 a stackable MissionEventHandler is available and should be used: PlayerConnected.
Before that, the functions BIS_fnc_addStackedEventHandler and BIS_fnc_removeStackedEventHandler should be used instead in order to keep compatibility between official and community content.


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.

Syntax

Syntax:
onPlayerConnected code
Parameters:
code: String or Code
Return Value:
Nothing

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
Groups:
MultiplayerEvent Handlers

Notes

i
Only post proven facts here. Report bugs on the Feedback Tracker and discuss on the Arma Discord or on the Forums.

+ Add Note (Help)

Retrieved from "https://community.bistudio.com/wiki?title=onPlayerConnected&oldid=215217"