isServer: Difference between revisions
Jump to navigation
Jump to search
m (VBS2 scripting category removal) |
m (Text replace - "{{uc:{{PAGENAME}}}}" to "{{uc:{{PAGENAME}}}} {{uc:{{PAGENAME}}}}") |
||
Line 47: | Line 47: | ||
[[Category:Command_Group:_System_Commands|{{uc:{{PAGENAME}}}}]] | [[Category:Command_Group:_System_Commands|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] |
Revision as of 11:15, 2 November 2011
Description
- Description:
- Returns true if the machine is either a server in a multiplayer game or if it is running a singleplayer game.
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
if (!isServer) exitWith {}
Additional Information
- See also:
- isDedicated
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
-
You can use isServer inside the condition of a trigger to have the trigger activate only for the server. All other conditions for the trigger will be checked across all machines, but it will only activate the trigger created on the server.
example:
this && isServer
The verb is misleading, it's correct interpretation is
NotMpClient
Mikero (nee Ook?) 15:27, 13 June 2011 (CEST)