onPlayerDisconnected: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<code>([^<]*)\[\[([a-zA-Z][a-zA-Z0-9_]+)\]\]([^<]*) *<\/code>" to "<code>$1$2$3</code>") |
Lou Montana (talk | contribs) m (Text replacement - "<sqf>([^↵][^\/]*↵[^\/]*)<\/sqf>" to "<sqf> $1 </sqf>") |
||
(3 intermediate revisions by the same user not shown) | |||
Line 30: | Line 30: | ||
|s1= [[onPlayerDisconnected]] code | |s1= [[onPlayerDisconnected]] code | ||
|p1= code: [[String]] or [[Code]] - | |p1= code: [[String]] or [[Code]] - code executed. 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 leaving player. In Arma 3 it is also the same as Steam ID. | * _uid: [[String]] - Is [[getPlayerUID]] of the leaving player. In Arma 3 it is also the same as Steam ID. | ||
* _name: [[String]] - Is [[profileName]] of the leaving player. | * _name: [[String]] - Is [[profileName]] of the leaving player. | ||
* {{GVI|arma3|1.50|size=0. | * {{GVI|arma3|1.50|size= 0.75}} _jip: [[Boolean]] - Is a flag that indicated whether or not the player joined after the mission has started ('''J'''oined '''I'''n '''P'''rogress). [[true]] - if the player was JIP, otherwise [[false]]. | ||
* {{GVI|arma3|1.50|size=0. | * {{GVI|arma3|1.50|size= 0.75}} _owner: [[Number]] - Is [[owner]] id of the leaving player. Can be used for kick or ban purposes or just for [[publicVariableClient]]. | ||
* {{GVI|arma3|1.96|size=0. | * {{GVI|arma3|1.96|size= 0.75}} _idstr: [[String]] - Same as {{hl|_id}} but in string format, so could be exactly compared to [[allMapMarkers | user marker]] ids. | ||
|r1= [[Nothing]] | |r1= [[Nothing]] | ||
|x1= < | |x1= <sqf>onPlayerDisconnected {diag_log [_id, _uid, _name]};</sqf> | ||
|x2= < | |x2= <sqf> | ||
onPlayerDisconnected { | |||
if (count allPlayers == 0) then { | if (count allPlayers == 0) then { | ||
endMission "END1"; | endMission "END1"; | ||
}; | }; | ||
};</ | }; | ||
</sqf> | |||
|seealso= [[onPlayerConnected]] [[didJIP]] [[didJIPOwner]] [[Arma 3: Mission Event Handlers#HandleDisconnect|HandleDisconnect]] [[Arma 3: Mission Event Handlers#playerDisconnected|playerDisconnected]] | |seealso= [[onPlayerConnected]] [[didJIP]] [[didJIPOwner]] [[Arma 3: Mission Event Handlers#HandleDisconnect|HandleDisconnect]] [[Arma 3: Mission Event Handlers#playerDisconnected|playerDisconnected]] | ||
}} | }} |
Latest revision as of 11:34, 3 September 2024
Description
- Description:
- This command will execute attached code whenever a player is leaving an MP session. The code will receive a number of special variables:
- Multiplayer:
- In multiplayer onPlayerDisconnected is executed only on the server.
- Groups:
- MultiplayerEvent Handlers
Syntax
- Syntax:
- onPlayerDisconnected code
- Parameters:
- code: String or Code - code executed. 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 leaving player. In Arma 3 it is also the same as Steam ID.
- _name: String - Is profileName of the leaving player.
- 1.50 _jip: Boolean - Is a flag that indicated whether or not the player joined after the mission has started (Joined In Progress). true - if the player was JIP, otherwise false.
- 1.50 _owner: Number - Is owner id of the leaving player. Can be used for kick or ban purposes or just for publicVariableClient.
- 1.96 _idstr: String - Same as _id but in string format, so could be exactly compared to user marker ids.
- Return Value:
- Nothing
Examples
- Example 1:
- Example 2:
Additional Information
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
Categories:
- Scripting Commands
- Introduced with Armed Assault version 1.00
- ArmA: Armed Assault: New Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Multiplayer
- Command Group: Event Handlers
- Scripting Commands: Server Execution