Locality in Multiplayer - Revision history

Lou Montana: Redirect to Multiplayer Scripting#Locality

2019-01-31T20:35:44Z

Redirect to Multiplayer Scripting#Locality

← Older revision		Revision as of 22:35, 31 January 2019
Line 1:		Line 1:
	~~{{Delete\|All the page's information should have been moved to [[Multiplayer Scripting]]}}~~		#REDIRECT [[Multiplayer Scripting#Locality]]


	~~Entities in OFP are handled, in multiplayer, by one computer alone (the server), which sends updates about this entity to all clients connected to the MP game.~~
	~~A unit is "local" when it is handled by the local computer (only registered on that machine,other clients connected won't see that unit as local).~~

	~~To know if a unit is local, use the [[local]] script command.~~


	~~== Basic Rules ==~~

	~~The basic rules to determine locality are as follows:~~

	~~''server'' = The dedicated server or the client that is hosting the game~~

	~~''client'' = A game instance used by a player, normally each is on a separate computer~~

	* The player's unit is ''always'' local to its client
	* AI units are always local to the client of their leader
	* A vehicle is always local to the client of its driver
	* AI leaders are always local to the server, if placed in the mission editor
	* AI units created after mission start via scripting will be local to the computer that issued the command
	* Empty vehicles/objects placed in the mission editor are local to the server
	* Empty vehicles/objects created after mission start via scripting (with createVehicle for example) are local to the machine that issued the command


	~~== Effects of different localities ==~~

	~~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
	* Units or players entering or exiting a vehicle
	* [[Team_Switch\|TeamSwitch]]
	* [[selectPlayer]]


	~~== Further reading ==~~

	* [[Multiplayer Scripting]]
	* [[6thSense.eu:EG#Locality~~\|6thSense Editing Guide]]~~

	~~[[Category: Scripting Topics~~]]

Lou Montana: Add delete request

2019-01-29T00:41:47Z

Add delete request

← Older revision		Revision as of 02:41, 29 January 2019
Line 1:		Line 1:
	[[~~Category: Scripting_Topics~~ ]]		{{Delete\|All the page's information should have been moved to [[Multiplayer Scripting]]}}


	Entities in OFP are handled, in multiplayer, by one computer alone (the server), which sends updates about this entity to all clients connected to the MP game.		Entities in OFP are handled, in multiplayer, by one computer alone (the server), which sends updates about this entity to all clients connected to the MP game.
Line 5:		Line 6:

	To know if a unit is local, use the [[local]] script command.		To know if a unit is local, use the [[local]] script command.


	== Basic Rules ==		== Basic Rules ==
Line 21:		Line 23:
	* Empty vehicles/objects placed in the mission editor are local to the server		* Empty vehicles/objects placed in the mission editor are local to the server
	* Empty vehicles/objects created after mission start via scripting (with createVehicle for example) are local to the machine that issued the command		* Empty vehicles/objects created after mission start via scripting (with createVehicle for example) are local to the machine that issued the command


	== Effects of different localities ==		== Effects of different localities ==
Line 33:		Line 36:
	* [[Team_Switch\|TeamSwitch]]		* [[Team_Switch\|TeamSwitch]]
	* [[selectPlayer]]		* [[selectPlayer]]


	== Further reading ==		== Further reading ==

	* [[6thSense.eu:EG#Locality\|Editing Guide]]		* [[Multiplayer Scripting]]
			* [[6thSense.eu:EG#Locality\|6thSense Editing Guide]]

			[[Category: Scripting Topics]]

Austin medic: rewording for better explaination

2014-12-22T01:38:18Z

rewording for better explaination

← Older revision		Revision as of 03:38, 22 December 2014
Line 1:		Line 1:
	[[Category: Scripting_Topics ]]		[[Category: Scripting_Topics ]]

	Entities in OFP are handled, in multiplayer, by one computer alone, which sends updates about this entity to ~~other computers~~ connected to the MP game.		Entities in OFP are handled, in multiplayer, by one computer alone (the server), which sends updates about this entity to all clients connected to the MP game.
	A unit is ~~said~~ "local" when it is handled by the local computer.		A unit is "local" when it is handled by the local computer (only registered on that machine,other clients connected won't see that unit as local).

	To know if a unit is local, use the [[local]] script command.		To know if a unit is local, use the [[local]] script command.

.kju: /* Effects of different localities */

2011-07-16T17:33:40Z

Effects of different localities

← Older revision		Revision as of 19:33, 16 July 2011
Line 27:		Line 27:
	Other commands have only local effect, nothing will be done outside of computer where the command was issued (see [[setFog]] 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
			* Units or players entering or exiting a vehicle
			* [[Team_Switch\|TeamSwitch]]
			* [[selectPlayer]]

	== Further reading ==		== Further reading ==

	* [[6thSense.eu:EG#Locality\|Editing Guide]]		* [[6thSense.eu:EG#Locality\|Editing Guide]]

.kju at 17:31, 16 July 2011

2011-07-16T17:31:11Z

← Older revision		Revision as of 19:31, 16 July 2011
Line 28:		Line 28:

	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.

			== Further reading ==

			* [[6thSense.eu:EG#Locality\|Editing Guide]]

General Barron: A bit more clarification for stuff created after mission start

2008-08-05T22:50:37Z

A bit more clarification for stuff created after mission start

← Older revision		Revision as of 00:50, 6 August 2008
Line 16:		Line 16:
	* The player's unit is ''always'' local to its client		* The player's unit is ''always'' local to its client
	* AI units are always local to the client of their leader		* AI units are always local to the client of their leader
	* AI leaders are always local to the server
	* A vehicle is always local to the client of its driver		* A vehicle is always local to the client of its driver
	* ~~Objects~~/vehicles created after mission start via scripting (~~via~~ createVehicle for example) are local to the machine that issued the command		* AI leaders are always local to the server, if placed in the mission editor
			* AI units created after mission start via scripting will be local to the computer that issued the command
			* Empty vehicles/objects placed in the mission editor are local to the server
			* Empty vehicles/objects created after mission start via scripting (with createVehicle for example) are local to the machine that issued the command

	== Effects of different localities ==		== Effects of different localities ==

General Barron: added locality info for created objects

2008-02-19T01:59:08Z

added locality info for created objects

← Older revision		Revision as of 03:59, 19 February 2008
Line 18:		Line 18:
	* AI leaders are always local to the server		* AI leaders are always local to the server
	* A vehicle is always local to the client of its driver		* A vehicle is always local to the client of its driver
			* Objects/vehicles created after mission start via scripting (via createVehicle for example) are local to the machine that issued the command

	== Effects of different localities ==		== Effects of different localities ==

Ceeeb: client definition, client != computer

2007-03-15T02:26:28Z

client definition, client != computer

← Older revision		Revision as of 04:26, 15 March 2007
Line 12:		Line 12:
	''server'' = The dedicated server or the client that is hosting the game		''server'' = The dedicated server or the client that is hosting the game

	''client'' = ~~The computer of~~ a player		''client'' = A game instance used by a player, normally each is on a separate computer

	* The player's unit is ''always'' local to its client		* The player's unit is ''always'' local to its client
	* AI units are always local to the ~~computer~~ of their leader		* AI units are always local to the client of their leader
	* AI leaders are always local to the server		* AI leaders are always local to the server
	* A vehicle is always local to the ~~computer~~ of its driver		* A vehicle is always local to the client of its driver

	== Effects of different localities ==		== Effects of different localities ==

T D: removed table

2006-07-24T12:38:44Z

removed table

← Older revision		Revision as of 14:38, 24 July 2006
Line 25:		Line 25:

	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.

	~~== Table of locality ==~~
	~~{{listdev}}~~
	~~{\| border="1"~~
	\|-
	~~! style="color: rgb(0, 0, 102);" \| Global \|\| style="color: rgb(0, 0, 102);" \| Local~~
	\|-
	~~\| align="center" width=150px height=25\|~~
	~~\| align="center" width=150px height=25\|~~
	\|-
	~~\| align="center" width=150px height=25\|~~
	~~\| align="center" width=150px height=25\|~~
	\|-
	~~\| align="center" width=150px height=25\|~~
	~~\| align="center" width=150px height=25\|~~
	\|}

Hardrock: Reverted edits by Hardrock (Talk); changed back to last version by T D

2006-07-24T12:13:05Z

Reverted edits by Hardrock (Talk); changed back to last version by T D

← Older revision		Revision as of 14:13, 24 July 2006
Line 25:		Line 25:

	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.

			== Table of locality ==
			{{listdev}}
			{\| border="1"
			\|-
			! style="color: rgb(0, 0, 102);" \| Global \|\| style="color: rgb(0, 0, 102);" \| Local
			\|-
			\| align="center" width=150px height=25\|
			\| align="center" width=150px height=25\|
			\|-
			\| align="center" width=150px height=25\|
			\| align="center" width=150px height=25\|
			\|-
			\| align="center" width=150px height=25\|
			\| align="center" width=150px height=25\|
			\|}