player: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (VBS2 scripting category removal) |
||
Line 64: | Line 64: | ||
[[Category:Scripting Commands ArmA|PLAYER]] | [[Category:Scripting Commands ArmA|PLAYER]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | ||
Revision as of 05:16, 19 July 2011
Description
- Description:
- Person controlled by player. In MP this value is different on each computer. In Intros and Outros this isn't set by default and must be assigned.
- Problems:
- In MP the command is not initialised in functions called by initline or init eventhandlers.
- Groups:
- Uncategorised
Syntax
Examples
Additional Information
- See also:
- See also needed
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
Notes
- Posted on 20 Jul, 2010
- GalZohar
-
Before you use the player object (usually to avoid JIP issues) all you need is to run:
waitUntil {!isNull player}; Anything else you see in other scripts is equivalent and/or redundant. Of course JIP players may need more than just the player to point at the actual JIP player unit, but that's script/mission-specific. - Posted on 27 Jan, 2008
- Dr_Eyeball
-
(isNull player) is true for JIP players on their client during initialization.
After initialization, it will be set, making it valid again.
To cater for this, some people use code similar to the following in their spawned scripts: if (!isServer && (player != player)) then { waitUntil {player == player}; waitUntil {time > 10}; }; // 'player' will now be valid _action = player addAction ["heal", "heal.sqf", [], -1, false, false, ""];
See JIP/player topic for additional helpful information.