onPlayerConnected: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (template:command argument fix) |
||
| (38 intermediate revisions by 17 users not shown) | |||
| Line 1: | Line 1: | ||
[[ | {{Command|= Comments | ||
[[ | ____________________________________________________________________________________________ | ||
[[ | |||
| arma |= Game name | |||
|1.00|= Game version | |||
|exec= 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: | |||
* '''_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 ('''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]].<br><br> | |||
{{Informative|Since '''Arma 3''' ''v1.57'' a stackable version of this EH is available: [[Arma_3:_Event_Handlers/addMissionEventHandler#PlayerConnected|PlayerConnected]]}}<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.}} | |||
|DESCRIPTION= | |||
____________________________________________________________________________________________ | |||
| '''onPlayerConnected''' code |SYNTAX= | |||
|p1= code: [[String]] or [[Code]] |PARAMETER1= | |||
| [[Nothing]] |RETURNVALUE= | |||
____________________________________________________________________________________________ | |||
|x1= <code>[[onPlayerConnected]] "[_id, _name] [[execVM]] ""PlayerConnected.sqf""";</code> |EXAMPLE1= | |||
|x2= <code>[[onPlayerConnected]] {[[diag_log]] [_id, _uid, _name]};</code> |EXAMPLE2= | |||
|x3= From Arma 3 v1.49: <code>[[onPlayerConnected]] { | |||
somevar = [[random]] 123; | |||
_owner [[publicVariableClient]] "somevar"; | |||
//this will set somevar on | |||
//joining player PC to a random value | |||
};</code>|EXAMPLE2= | |||
|x4= From Arma 3 v1.49: <code>[[onPlayerConnected]] {isJip = _jip; _owner [[publicVariableClient]] "isJip"}; | |||
//Each player will now have variable isJip containing individual JIP info</code>|EXAMPLE2= | |||
''' | |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> | |||
Note that there is a player with the '''_name''' called __SERVER__ which will also connect to a multiplayer game, executing ''code''. |= | |||
[[ | | [[onPlayerDisconnected]], [[didJIP]], [[didJIPOwner]]|SEEALSO= | ||
}} | |||
<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 OFP Elite |ONPLAYERCONNECTED]] | |||
[[Category:Scripting Commands ArmA|ONPLAYERCONNECTED]] | |||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]] | |||
Revision as of 15:44, 7 April 2019
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.
Template:Feature arma3 - 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:
- Uncategorised
Syntax
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 on //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