local: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(add. ArmA2 classification) |
||
Line 54: | Line 54: | ||
[[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]] | [[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Command_Group:_Object_Information|{{uc:{{PAGENAME}}}}]] | [[Category:Command_Group:_Object_Information|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] |
Revision as of 16:52, 3 June 2009
Description
- Description:
- Check if given unit is local on the computer in Multiplayer games (see Locality in Multiplayer for general concepts). This can be used when some activation fields or scripts need to be performed only on one computer. In Singleplayer all objects are local. Note: All static objects are local everywhere.
- Problems:
- In MP remote objects are not initialised in functions called by initline or init eventhandlers.
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
- SQS
?!local _unitName : goto "multi"
- Example 2:
- SQF
If (local _unitName) then {
hint "multi";
};
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 August 4, 2006 - 10:56
- hardrock
- Notes from before the conversion: In multiplayer, a game logic will always be local to the host computer. This works on both dedicated and player-hosted servers.
Bottom Section
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.00
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands OFP 1.96
- Scripting Commands OFP 1.46
- Scripting Commands ArmA
- Command Group: Multiplayer
- Command Group: Object Information
- Scripting Commands ArmA2