onPlayerConnected

1.00

  

Click on the images for descriptions

Introduced in

Game:

Armed Assault

Version:

1.00

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.
• _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.
• _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.
• _jip: (since Arma 3 v1.49) Boolean - is a flag that indicated whether or not the player joined after the mission has started (Joined In Progress). true - when the player is JIP, otherwise false.

In order to keep compatability between official and community content the functions BIS_fnc_addStackedEventHandler and BIS_fnc_removeStackedEventHandler should be used instead.

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]};

Additional Information

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 statement.

See also:

onPlayerDisconnected

Notes

Only post proven facts here. Report bugs on the feedback tracker. Use the talk page or the forums for discussions.
Add New Note | How To