Lou Montana/Sandbox – User

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Update w/ links)
 
(110 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Informative|Future [[Multiplayer Scripting]] page}}
[[Category: Sandbox]]
{{SideTOC}}
{{Feature|informative|To go on [[Initialisation Order]].}}
{{Stub}}
== The basics ==


* In Multiplayer, players are connected to a server that distributes information among them.
{| class="wikitable sortable align-center align-left-col-1"
* The server can be either a dedicated machine, or hosted by a player; in the latter it means the server can have a [[player]] unit.
|+ Order of Initialisation (use column sorting for respective machine order)
* Players can join a game ''after'' it started: they are considered "[[Join In Progress|JIP]]" and scripting should be adapted to them.
! rowspan="2" class="unsortable" style="text-align: center" | Task
! rowspan="2" | Exec Environment
! rowspan="1" colspan="5" class="unsortable" | Machine
|-
! Single Player
! Dedicated Server
! Hosted Server
! Multiplayer Client
! [[Multiplayer Scripting#Join In Progress|JIP]] MP Client


{{Informative|In Singleplayer, the game acts as a player-hosted server ({{Inline code|[[isServer]]}} returns {{Inline code|[[true]]}}).}}
|-
{{Warning|Some Multiplayer commands will '''not''' work in Singleplayer, such as {{Inline code|[[netId]]}} !}}
| [[Arma 3: Functions Library|Functions]] with <syntaxhighlight lang="cpp" inline>recompile</syntaxhighlight> {{Link|Arma 3: Functions Library#Attributes 3|attribute}} are recompiled
| {{n/a}}
| 1 <!-- Single Player -->
| 1 <!-- Dedicated Server -->
| 1 <!-- Hosted Server -->
| 1 <!-- Multiplayer Client -->
| 1 <!-- JIP MP Client -->


|-
| [[Arma 3: Functions Library|Functions]] with <syntaxhighlight lang="cpp" inline>preInit</syntaxhighlight> {{Link|Arma 3: Functions Library#Attributes 3|attribute}} are called
| [[Scheduler#Unscheduled Environment|Unscheduled]]
| 2 <!-- Single Player -->
| 2 <!-- Dedicated Server -->
| 2 <!-- Hosted Server -->
| 2 <!-- Multiplayer Client -->
| 2 <!-- JIP MP Client -->


== Locality ==
|-
| Object Init Event Handlers are called
| [[Scheduler#Unscheduled Environment|Unscheduled]]
| 3 <!-- Single Player -->
| 3 <!-- Dedicated Server -->
| 3 <!-- Hosted Server -->
| 3 <!-- Multiplayer Client -->
| {{Icon|unchecked}} <!-- JIP MP Client -->


* '''LOCAL''' is an attribute for the machine where the command/script/function is executed.
|-
* '''REMOTE''' is an attribute for all the other machines. All clients are remote to a server, for example.
| Expressions of [[Eden Editor: Configuring Attributes|Eden Editor entity attributes]] are called<ref name="isPlayer"><sqf inline>isPlayer _entity</sqf> does not return [[true]] immediately. Once the entity has become a [[player]], it is transferred to the client.</ref>
* A [[player]]'s unit is '''always''' local to the player's machine. A dedicated server doesn't have a [[player]] unit.
| [[Scheduler#Unscheduled Environment|Unscheduled]]
* [[:Category:Scripting_Commands|commands]] arguments and effects can be either '''local''' or '''global''':
| 4 <!-- Single Player -->
** a '''local''' argument means an argument that is processed on the machine where the command is executed
| 4 <!-- Dedicated Server -->
** a '''global''' argument means any unit, even a remote one
| 4 <!-- Hosted Server -->
** a '''local''' effect means that the effect will only happen on the machine where the command is executed
| {{Icon|unchecked}} <!-- Multiplayer Client -->
** a '''global''' effect means that all the computers will receive it
| {{Icon|unchecked}} <!-- JIP MP Client -->
See [[Locality in Multiplayer]] for more information.


=== Examples ===
{|class="bikitable"
!Code
!Argu-ments
!Effect
!Description
|-
|-
|{{Inline code|remoteUnit [[setDamage]] 1;}}
| Object initialisation fields are called
|align="center"|{{EffArg|cmd|arg|glob}}
| [[Scheduler#Unscheduled Environment|Unscheduled]]
|align="center"|{{EffArg|cmd|eff|glob}}
| 5 <!-- Single Player -->
|Any unit (local or remote) will die, and all the computers will know
| 5 <!-- Dedicated Server -->
| 5 <!-- Hosted Server -->
| 4 <!-- Multiplayer Client -->
| 3 <!-- JIP MP Client -->
 
|- style="background-color: #95F0AD"
| [[Event Scripts#init.sqs|init.sqs]] is executed
|
| 6 <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->
 
|- style="background-color: #95F0AD"
| [[Event Scripts#init.sqf|init.sqf]] is executed
| [[Scheduler#Scheduled Environment|Scheduled]]<ref name="enginewaits">Note '''in single player''' that while the environment is [[Scheduler#Scheduled Environment|Scheduled]] ([[canSuspend]] returns true), the engine seems to wait until the script is done executing, essentially behaving similarly to an [[Scheduler#Unscheduled Environment|Unscheduled environment]] - infinite loops will freeze the game, [[uiSleep]] may pause the game for up to ~20s (postInit), [[waitUntil]] can cause catastrophic issues, etc.</ref>
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->
 
|-
|-
|{{Inline code|localUnit [[addMagazine]] "30Rnd_556x45_STANAG";}}
| Expressions of [[Eden Editor: Configuring Attributes|Eden Editor scenario attributes]] are called<ref name="playerCommandNotAvailable">[[player]] is not available immediately.</ref>
|align="center"|{{EffArg|cmd|arg|loc}}
| [[Scheduler#Unscheduled Environment|Unscheduled]]
|align="center"|{{EffArg|cmd|eff|glob}}
| <!-- Single Player -->
|Only a local unit can have its inventory edited with this command, but all the machines will be notified: if a player looks into the localUnit inventory, the added magazine will be there
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->
 
|- style="background-color: #95DEF0"
| Persistent functions are called
|
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->
 
|-
|-
|{{Inline code|remoteUnit [[setFace]] "Miller";}}
| [[Modules]] are initialised
|align="center"|{{EffArg|cmd|arg|glob}}
|
|align="center"|{{EffArg|cmd|eff|loc}}
| <!-- Single Player -->
|Any unit (local or remote) can get its face changed, but the new face will not be propagated through the network. Only the local machine's player will see the effect of the command
| <!-- Dedicated Server -->
{{Informative|This command should ideally be '''executed on every machine''', for example with:
| <!-- Hosted Server -->
[remoteUnit, "Miller"] [[remoteExec]] ["setFace", 0, true];
| <!-- Multiplayer Client -->
See [[#Remote Execution|Remote Execution]] paragraph for more information.}}
| {{Icon|unchecked}} <!-- JIP MP Client -->
|-
 
|{{Inline code|localCamera [[cameraEffect]] ["Internal", "Back"];}}
|- style="background-color: #DEF0AD"
|align="center"|{{EffArg|cmd|arg|loc}}
| [[Event Scripts#initServer.sqf|initServer.sqf]] is executed
|align="center"|{{EffArg|cmd|eff|loc}}
| [[Scheduler#Scheduled Environment|Scheduled]]
|Only a local camera can be entered, and of course only the local machine will see through this camera – no network traffic is generated here
| <!-- Single Player -->
|}
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| {{n/a}} <!-- Multiplayer Client -->
| {{n/a}} <!-- JIP MP Client -->


=== Different machines ===
|- style="background-color: #DEF0AD"
{|class="bikitable"
| [[Event Scripts#initPlayerLocal.sqf|initPlayerLocal.sqf]] is executed
!Machine
| [[Scheduler#Scheduled Environment|Scheduled]]
!Conditions
| <!-- Single Player -->
|-
| {{n/a}} <!-- Dedicated Server -->
|Dedicated Server
| <!-- Hosted Server -->
|{{Inline code|[[isDedicated]]}}
| <!-- Multiplayer Client -->
|-
| <!-- JIP MP Client -->
|Player Server
|{{Inline code|[[hasInterface]] && [[isServer]]}}
|-
|Client
|{{Inline code|[[hasInterface]] && not [[isServer]]}}
|-
|[[Join In Progress|JIP]] Client
|{{Inline code|[[didJIP]]}}
|-
|[[Arma 3 Headless Client|Headless Client]]
|{{Inline code|not [[hasInterface]] && not [[isDedicated]]}}
|}
* If you want to know if the current machine is a server (Dedicated Server or Player Server), use {{Inline code|[[isServer]]}}.
* If you want to know if the current machine has a player (Player Server included), use {{Inline code|[[hasInterface]]}}.


|- style="background-color: #DEF0AD"
| [[Event Scripts#initPlayerServer.sqf|initPlayerServer.sqf]] is executed on the server
| [[Scheduler#Scheduled Environment|Scheduled]]
| <!-- Single Player -->
| {{n/a}} <!-- Dedicated Server -->
| ?? <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->


== PublicVariable commands ==
PublicVariable commands allow to send '''global''' variables to specified machines.
* Network reception is guaranteed
* Short variable names should be used for network performance
* These commands shouldn't be used intensely for the same reason
{|class="bikitable"
!Command
!Effect
|-
|[[publicVariable]]
|Set/update a variable value from the local machine to all the other machines (including server)
|-
|[[publicVariableServer]]
|Set/update a variable value '''from a client to the server'''
|-
|-
|[[publicVariableClient]]
| [[Arma 3: Functions Library|Functions]] with <syntaxhighlight lang="cpp" inline>postInit</syntaxhighlight> {{Link|Arma 3: Functions Library#Attributes 3|attribute}} are called
|Set/update a variable value '''from the local machine''' (not necessarily the server) '''to a specific client'''<br />{{Important|The information will be lost if the targeted client disconnects!}}
| [[Scheduler#Scheduled Environment|Scheduled]]<ref name="enginewaits"/>
|}
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->


=== How it works ===
|- style="background-color: #95DEF0"
The server has the variable {{Inline code|ABC_Score}} to send to everyone, it then uses {{Inline code|[[publicVariable]] "ABC_Score"}} (do not forget the quotes!)<br />
| [[Event Scripts#init.sqs|init.sqs]] is executed
This sends the variable name and value to the clients.
| [[Scheduler#Scheduled Environment|Scheduled]]
* If the variable is not yet declared on their machine, it will declare it as well.
| <!-- Single Player -->
* If the variable already exists, '''the value is overridden''' by the server's value.
| <!-- Dedicated Server -->
* If the variable changes again on the server, it has to be manually [[publicVariable]]'d once again!
| <!-- Hosted Server -->
* A [[Join In Progress|JIP]] player will synchronise '''server's''' public variables '''before''' executing '''init.sqf'''. See [[Initialization Order]] for more information.
| <!-- Multiplayer Client -->
** A JIP player will '''not''' synchronise [[publicVariableClient]]-received variables after he disconnects/reconnects. Only server-known public variables sent with [[publicVariable]] will be synchronised.
| <!-- JIP MP Client -->


|- style="background-color: #95DEF0"
| [[Event Scripts#init.sqf|init.sqf]] is executed
| [[Scheduler#Scheduled Environment|Scheduled]]
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->


== Remote Execution ==
|-
{{arma2}} introduced the (now obsolete) [[Multiplayer framework]], used as follow:
| [[remoteExec]]'s [[Multiplayer Scripting#Join In Progress|JIP]] queue
waitUntil{ not isNil "BIS_MPF_InitDone"; };
| {{n/a}}
[nil, nil, rHINT, "Message to everyone!"] call RE;
| {{n/a}} <!-- Single Player -->
| {{n/a}} <!-- Dedicated Server -->
| {{n/a}} <!-- Hosted Server -->
| {{n/a}} <!-- Multiplayer Client -->
| 42 <!-- JIP MP Client -->


{{arma3}} alpha introduced [[BIS_fnc_MP]]:
|- style="background-color: #EEE"
["Message to everyone, including JIP players!", "hint", true, true] call BIS_fnc_MP;
| ''Scenario going''
| {{n/a}}
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->


{{Warning|These two methods above are considered '''OBSOLETE''' since {{arma3}} v1.50 introduced two engine commands: [[remoteExec]] and [[remoteExecCall]].}}
|-
| [[Event Scripts#exit.sqf|exit.sqf]]
|
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->


|-
| [[Event Scripts#exit.sqs|exit.sqs]]
|
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->


'''{{arma3}} (&gt; v1.50):'''
|-
["Message to everyone, including JIP players!", 0, true] remoteExec ["hint"];
| {{Link|Arma 3: Mission Event Handlers#Ended|"Ended" Mission Event Handler}}
See [[Arma 3 Remote Execution]] for more information.
|
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->


|-
|  {{Link|Arma 3: Mission Event Handlers#MPEnded|"MPEnded" Mission Event Handler}}
|
| <!-- Single Player -->
| <!-- Dedicated Server -->
| <!-- Hosted Server -->
| <!-- Multiplayer Client -->
| <!-- JIP MP Client -->


== See also ==
|}
* [[Arma 3 Headless Client|Headless Client]]
* [[Locality in Multiplayer]]
* [[:Category:Commands by effects and arguments locality|Commands by effects and arguments locality]]
** [[:Category:Commands requiring server side execution|Server-only commands]]
* [[Initialization Order]]
* [[Arma 3 Remote Execution]]




[[Category: Scripting Topics]]
== See Also ==


[[Category:Sandbox]]
* [[Arma 3: Functions Library]]<!--
* [[Arma 2: Functions Library]] -->
* [[Arma 3: Remote Execution]], [[BIS_fnc_MP]] <!-- keep? -->
* [[Eden Editor: Configuring Attributes|Eden Editor: Configuring Attributes]]
* [[Event Scripts]]
* [[Scheduler]]

Latest revision as of 00:29, 18 March 2024

ⓘ
Order of Initialisation (use column sorting for respective machine order)
Task Exec Environment Machine
Single Player Dedicated Server Hosted Server Multiplayer Client JIP MP Client
Functions with recompile attribute are recompiled N/A 1 1 1 1 1
Functions with preInit attribute are called Unscheduled 2 2 2 2 2
Object Init Event Handlers are called Unscheduled 3 3 3 3 Unchecked
Expressions of Eden Editor entity attributes are called[1] Unscheduled 4 4 4 Unchecked Unchecked
Object initialisation fields are called Unscheduled 5 5 5 4 3
init.sqs is executed 6
init.sqf is executed Scheduled[2]
Expressions of Eden Editor scenario attributes are called[3] Unscheduled
Persistent functions are called
Modules are initialised Unchecked
initServer.sqf is executed Scheduled N/A N/A
initPlayerLocal.sqf is executed Scheduled N/A
initPlayerServer.sqf is executed on the server Scheduled N/A ??
Functions with postInit attribute are called Scheduled[2]
init.sqs is executed Scheduled
init.sqf is executed Scheduled
remoteExec's JIP queue N/A N/A N/A N/A N/A 42
Scenario going N/A
exit.sqf
exit.sqs
"Ended" Mission Event Handler
"MPEnded" Mission Event Handler


See Also

  1. ↑ isPlayer _entity does not return true immediately. Once the entity has become a player, it is transferred to the client.
  2. ↑ 2.0 2.1 Note in single player that while the environment is Scheduled (canSuspend returns true), the engine seems to wait until the script is done executing, essentially behaving similarly to an Unscheduled environment - infinite loops will freeze the game, uiSleep may pause the game for up to ~20s (postInit), waitUntil can cause catastrophic issues, etc.
  3. ↑ player is not available immediately.
Retrieved from "https://community.bistudio.com/wiki?title=User:Lou_Montana/Sandbox&oldid=353415"