ofp:locality_in_multiplayer
Differences
This shows you the differences between two versions of the page.
| ofp:locality_in_multiplayer [2009/04/17 11:16] – created locality_in_multiplayer initial page. snakeman | ofp:locality_in_multiplayer [2024/08/01 07:09] (current) – links added. snakeman | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Locality | + | ====== |
| - | **Locality in multiplayer.** | + | [[https:// |
| + | |||
| + | **Operation Flashpoint (OFP)** aka ArmA: Cold War Assault (CWA) | ||
| Entities in OFP are handled, in multiplayer (MP), by one computer alone, which sends updates about this entity to other computers connected to the MP game. A unit is said " | Entities in OFP are handled, in multiplayer (MP), by one computer alone, which sends updates about this entity to other computers connected to the MP game. A unit is said " | ||
| Line 25: | Line 27: | ||
| - | ====== Effects | + | ====== Effects |
| Knowing locality of a unit is very important as certain command only affect local units (see moveInDriver for example). Other commands have only local effect, nothing will be done outside of computer where the command was issued (see setFog for example). | Knowing locality of a unit is very important as certain command only affect local units (see moveInDriver for example). Other commands have only local effect, nothing will be done outside of computer where the command was issued (see setFog for example). | ||
| A unit can change locality during its lifetime. Typical cases are a player dying (his squad AI units are passed to server), use of a join command, or units or players entering or exiting vehicles. | A unit can change locality during its lifetime. Typical cases are a player dying (his squad AI units are passed to server), use of a join command, or units or players entering or exiting vehicles. | ||
| + | |||
ofp/locality_in_multiplayer.1239966980.txt.gz · Last modified: 2009/04/17 11:16 by snakeman