isServer: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (Not sure about this change. Technically, it was introduced in Arma I, and then backported to OFP 1.99.) |
||
Line 2: | Line 2: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| | |ofp|= Game name | ||
|1. | |1.99|= Game version | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
Revision as of 08:47, 25 September 2014
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)
Bottom Section
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.99
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands OFP 1.99
- Scripting Commands ArmA
- Command Group: Multiplayer
- Command Group: System Commands
- Scripting Commands ArmA2
- Scripting Commands Arma 3
- Scripting Commands Take On Helicopters