PMC Editing Wiki

User Tools

Site Tools

Trace: • wrptutorial • satellite_image_tutorial
arma:missions:mp_tutorial

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

arma:missions:mp_tutorial [2011/06/30 13:52] – created mp_tutorial initial page. snakemanarma:missions:mp_tutorial [2024/08/01 08:27] (current) – links added. snakeman
Line 1: Line 1:
-====== Multiplayer Tutorial ======+====== ArmA 1 Multiplayer Tutorial ======
  
-The purpose of this tutorial is to discuss some of the scripting issues that are particular to the creation of multi-player missions. It is assumed that the reader is at least a competent scripter in a single-player setting.+[[https://www.pmctactical.org/forum/viewforum.php?f=42|ArmA 1 Forum]], [[:arma|ArmA 1 Home]], [[arma:config|ArmA 1 Config]], [[arma:tools|ArmA 1 Tools]], [[arma:file_formats|ArmA 1 File Formats]], [[arma:missions|ArmA 1 Missions]], [[arma:modeling|ArmA 1 3D Modeling]], [[arma:terrain|ArmA 1 Terrain]], [[arma:texturing|ArmA 1 Texturing]], [[arma:scripting|ArmA 1 Scripting]]
  
-======  Locality ======+**ArmA 1** aka Armed Assault (ArmA)
  
-===== Locality of Objects =====+The purpose of this tutorial is to discuss some of the scripting issues that are particular to the creation of multi-player missions. It is assumed that the reader is at least a competent script writer in a single-player setting. 
 + 
 +====== Locality ====== 
 + 
 +===== Locality Of Objects =====
  
 The locality of an object determines which computer is the owner of this object. Many commands affect only to local objects, so the locality must be considered when we want to execute these commands over existing objects. The locality of an object determines which computer is the owner of this object. Many commands affect only to local objects, so the locality must be considered when we want to execute these commands over existing objects.
Line 21: Line 25:
  
  
-===== Locality of markers =====+===== Locality Of Markers =====
  
 Any marker placed in the editor is global and will be seen by any player. If you want markers to be local for a particular machine (only visible from this machine) create it using createMarkerLocal (and use the corresponding local commands to configure it). Any marker placed in the editor is global and will be seen by any player. If you want markers to be local for a particular machine (only visible from this machine) create it using createMarkerLocal (and use the corresponding local commands to configure it).
  
  
-===== Locality of commands =====+===== Locality Of Commands =====
  
 The locality of a command covers two different concepts: The locality of a command covers two different concepts:
Line 40: Line 44:
  
  
-===== Determining the locality of an object =====+===== Determining The Locality Of An Object =====
  
 Using the local comand: Using the local comand:
Line 82: Line 86:
  
  
-===== Determining whether the script is running on a client or the server =====+===== Determining Whether The Script Is Running On A Client Or The Server =====
  
 In older versions of the game, the most common way to check for server was to add a gamelogic named "server" from the editor to the mission, and then just do the following check: In older versions of the game, the most common way to check for server was to add a gamelogic named "server" from the editor to the mission, and then just do the following check:
Line 104: Line 108:
  
  
-===== The importance of determining where the server is =====+===== The Importance Of Determining Where The Server Is =====
  
 For example, your mission might have many scripts that should not be executed on every connected machine and that isn't required to affect non-local units. For these cases you have two options: For example, your mission might have many scripts that should not be executed on every connected machine and that isn't required to affect non-local units. For these cases you have two options:
Line 124: Line 128:
  
  
-===== Where script files, and scripts input into the editor, are executed =====+===== Where Script Files, And Scripts Input Into The Editor, Are Executed =====
  
 In many situations we must execute a script or command only once, not in every machine connected, or we must execute some code only there were a particular unit is local, or only in the server. To start with, let's see where the code is executed by default: In many situations we must execute a script or command only once, not in every machine connected, or we must execute some code only there were a particular unit is local, or only in the server. To start with, let's see where the code is executed by default:
Line 137: Line 141:
  
  
-===== Running object initialization code on every machine =====+===== Running Object Initialization Code On Every Machine =====
  
 For that purpose, use the setVehicleInit command to set the init commands of your newly created units. This is similar to writing these commands in the init field of a unit placed in the editor, but setVehicleInit doesn't have any immediate effect. You may set the init field of one or many existing units by executing setVehicleInit, but then you must execute the processInitCommands command to actually execute all the commands configured with setVehicleInit. For that purpose, use the setVehicleInit command to set the init commands of your newly created units. This is similar to writing these commands in the init field of a unit placed in the editor, but setVehicleInit doesn't have any immediate effect. You may set the init field of one or many existing units by executing setVehicleInit, but then you must execute the processInitCommands command to actually execute all the commands configured with setVehicleInit.
Line 153: Line 157:
  
  
-====== Server and Clients ======+====== Server And Clients ======
  
 The simplest way to communicate is to use publicVariable, which will allow synchronisation of a global variable's value across all machines. Unfortunately, this simple technique will not allow the transfer of some data types (sides, arrays) and is limited in its usefulness, since it does not inform the other machines that anything has been changed. The simplest way to communicate is to use publicVariable, which will allow synchronisation of a global variable's value across all machines. Unfortunately, this simple technique will not allow the transfer of some data types (sides, arrays) and is limited in its usefulness, since it does not inform the other machines that anything has been changed.
  
  
-===== Remote command execution =====+===== Remote Command Execution =====
  
 There are two ways to execute commands, whenever required, on other machines: There are two ways to execute commands, whenever required, on other machines:
Line 273: Line 277:
   * Server: The machine controlling the game and the player interactions.   * Server: The machine controlling the game and the player interactions.
   * Single-player game (SP): A game run from within ArmA, such as the campaign, where the client and (non-dedicated) server are actually the same machine. This makes scripting considerably simpler, since one does not have to manage communication between machines, as one would in a multi-player game.   * Single-player game (SP): A game run from within ArmA, such as the campaign, where the client and (non-dedicated) server are actually the same machine. This makes scripting considerably simpler, since one does not have to manage communication between machines, as one would in a multi-player game.
 +
arma/missions/mp_tutorial.1309441968.txt.gz · Last modified: 2011/06/30 13:52 by snakeman
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

All PMC web site download services are temporarily suspended until web site yearly fees have been recovered, want to download addons/mods? Then Support PMC.

If you are grateful for all the work PMC has done in the past 25 years, use Support PMC page.