Difference between revisions of "onPlayerConnected"
Jump to navigation
Jump to search
(add. classification) |
(Added Note for Function behaviour.) |
||
| Line 24: | Line 24: | ||
|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. |= | + | 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 ''statement''. |= | ||
| [[onPlayerDisconnected]] |= See also | | [[onPlayerDisconnected]] |= See also | ||
Revision as of 03:28, 20 January 2010
Description
- Description:
- This statement is launched whenever a player is connected to a MP session.
Variables _id and _name are set, _id being the session id number as seen in #userlist.
Note that as of 1.08, this command only accepts a code-string rather than code delimited by braces.
Note as of ArmA 2 version 1.02 this function returns also variable _uid with uniqueID of player. - 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. - Groups:
- Uncategorised
Syntax
Examples
- Example 1:
onPlayerConnected "[_id, _name] execVM ""PlayerConnected.sqf""";
Additional Information
- See also:
- onPlayerDisconnected
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