isServer: Difference between revisions
Jump to navigation
Jump to search
m (misleading) |
m (template:command argument fix) |
||
(20 intermediate revisions by 6 users not shown) | |||
Line 7: | Line 7: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| Returns [[true]] if the machine is | | Returns [[true]] if the machine (executing the command) is the server in a multiplayer game or is running single player. [[isServer]] will return [[true]] for both, dedicated server and player hosted. Dedicated server could be detected with [[isDedicated]] command. Hosted by player server can be detected by presense of UI: [[isServer]] && [[hasInterface]]|DESCRIPTION= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| | | '''isServer''' |SYNTAX= | ||
|p1= |= | |p1= |PARAMETER1= | ||
| [[Boolean]] |= | | [[Boolean]] |RETURNVALUE= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
|x1= <code>if (!isServer) [[exitWith]] {}</code>|= | |x1= <code>[[if]] (![[isServer]]) [[exitWith]] {};</code>|EXAMPLE1= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| [[isDedicated]] |= | | [[isDedicated]], [[isMultiplayer]], [[hasInterface]], [[local]]|SEEALSO= | ||
}} | }} | ||
Line 27: | Line 27: | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<!-- Note Section BEGIN --> | <!-- Note Section BEGIN --> | ||
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. | <dd class="notedate">Posted on April 8, 2011 | ||
<dt class="note">'''[[User:Igneous01|Igneous01]]''' | |||
<dd class="note">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. For example: <code>this && [[isServer]]</code> | |||
<!-- Note Section END --> | <!-- Note Section END --> | ||
</dl> | </dl> | ||
Line 44: | Line 37: | ||
[[Category:Scripting Commands|ISSERVER]] | [[Category:Scripting Commands|ISSERVER]] | ||
[[Category:Scripting Commands ArmA|ISSERVER]] | [[Category:Scripting Commands ArmA|ISSERVER]] | ||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]] | [[Category:Command_Group:_Multiplayer|{{uc:{{PAGENAME}}}}]] | ||
[[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}}}}]] | ||
[[ | |||
<!-- CONTINUE Notes --> | |||
<dl class="command_description"> | |||
<dd class="notedate">Posted on December 21, 2014 - 14:51 (UTC)</dd> | |||
<dt class="note">[[User:Killzone Kid|Killzone Kid]]</dt> | |||
<dd class="note"> | |||
<code>[[if]] ([[isDedicated]]) [[then]] { | |||
//run on dedicated server only | |||
}; | |||
[[if]] ([[isServer]]) [[then]] { | |||
//run on dedicated server or player host | |||
}; | |||
[[if]] ([[hasInterface]]) [[then]] { | |||
//run on all player clients incl. player host | |||
}; | |||
[[if]] (![[isDedicated]]) [[then]] { | |||
//run on all player clients incl. player host and headless clients | |||
}; | |||
[[if]] (![[isServer]]) [[then]] { | |||
//run on all player clients incl. headless clients but not player host | |||
}; | |||
[[if]] (![[hasInterface]]) [[then]] { | |||
//run on headless clients and dedicated server | |||
}; | |||
[[if]] (![[hasInterface]] && ![[isDedicated]]) [[then]] { | |||
//run on headless clients only | |||
};</code> | |||
</dd> | |||
</dl> | |||
<!-- DISCONTINUE Notes --> |
Revision as of 15:41, 7 April 2019
Description
- Description:
- Returns true if the machine (executing the command) is the server in a multiplayer game or is running single player. isServer will return true for both, dedicated server and player hosted. Dedicated server could be detected with isDedicated command. Hosted by player server can be detected by presense of UI: isServer && hasInterface
- Groups:
- Uncategorised
Syntax
- Syntax:
- isServer
- Return Value:
- Boolean
Examples
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
Notes
- Posted on April 8, 2011
- Igneous01
- 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. For example:
this && isServer
Bottom Section
- Posted on December 21, 2014 - 14:51 (UTC)
- Killzone Kid
-
if (isDedicated) then { //run on dedicated server only }; if (isServer) then { //run on dedicated server or player host }; if (hasInterface) then { //run on all player clients incl. player host }; if (!isDedicated) then { //run on all player clients incl. player host and headless clients }; if (!isServer) then { //run on all player clients incl. headless clients but not player host }; if (!hasInterface) then { //run on headless clients and dedicated server }; if (!hasInterface && !isDedicated) then { //run on headless clients only };