Element data - Revision history

Azure at 05:30, 11 July 2025

2025-07-11T05:30:33Z

← Older revision		Revision as of 05:30, 11 July 2025
Line 5:		Line 5:
	Since not all data types can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.		Since not all data types can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.

	{{Added feature/item\|1.6.1\|1.6.0\|22790\|Element data is not protected from ~~clinet~~ changes by default. You '''SHOULD''' enable [[Server_mtaserver.conf#elementdata_whitelisted\|elementdata_whitelisted]] in '''mtaserver.conf''' to protect your server simple cheats. Use the '''clientChangesPolicy''' parameter in [[setElementData]] to allow some changes.}}		{{Added feature/item\|1.6.1\|1.6.0\|22790\|Element data is not protected from client changes by default. You '''SHOULD''' enable [[Server_mtaserver.conf#elementdata_whitelisted\|elementdata_whitelisted]] in '''mtaserver.conf''' to protect your server simple cheats. Use the '''clientChangesPolicy''' parameter in [[setElementData]] to allow some changes.}}

	==Relevant functions==		==Relevant functions==

TheNormalnij: Add security options

2025-01-15T12:22:30Z

Add security options

← Older revision		Revision as of 12:22, 15 January 2025
Line 4:		Line 4:

	Since not all data types can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.		Since not all data types can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.

			{{Added feature/item\|1.6.1\|1.6.0\|22790\|Element data is not protected from clinet changes by default. You '''SHOULD''' enable [[Server_mtaserver.conf#elementdata_whitelisted\|elementdata_whitelisted]] in '''mtaserver.conf''' to protect your server simple cheats. Use the '''clientChangesPolicy''' parameter in [[setElementData]] to allow some changes.}}

	==Relevant functions==		==Relevant functions==

TheNormalnij: /* Relevant events */ Add onPlayerChangesProtectedData

2025-01-15T12:14:36Z

Relevant events: Add onPlayerChangesProtectedData

← Older revision		Revision as of 12:14, 15 January 2025
Line 11:		Line 11:
	==Relevant events==		==Relevant events==
	* [[onElementDataChange]]: triggered on the server after element data is changed.		* [[onElementDataChange]]: triggered on the server after element data is changed.
			* [[onPlayerChangesProtectedData]]: triggered on the server after the client attempts to change protected element data.
	* [[onClientElementDataChange]]: triggered on the client after element data is changed.		* [[onClientElementDataChange]]: triggered on the client after element data is changed.
	[[pt-br:Element_data]]		[[pt-br:Element_data]]

FileEX at 16:52, 12 September 2024

2024-09-12T16:52:47Z

← Older revision		Revision as of 16:52, 12 September 2024
Line 13:		Line 13:
	* [[onClientElementDataChange]]: triggered on the client after element data is changed.		* [[onClientElementDataChange]]: triggered on the client after element data is changed.
	[[pt-br:Element_data]]		[[pt-br:Element_data]]
			[[pl:Element data]]

			[[Category:Scripting Concepts]]

Srslyyyy at 16:38, 8 April 2024

2024-04-08T16:38:10Z

← Older revision		Revision as of 16:38, 8 April 2024
Line 1:		Line 1:
	Each [[element]] that is loaded is able to have [[element data]] values attached to it. These are values that can be accessed using a keyword string and directly correspond to the element's attributes in the map file, unless changed via scripting. Element data is a good way to store distributed information you want associated with an element, for example you could use it to associate a score with a player, or a team with a vehicle.		Each [[element]] that is loaded is able to have [[element data]] values attached to it. These are values that can be accessed using a keyword string and directly correspond to the element's attributes in the map file, unless changed via scripting. Element data is a good (but expensive) way to store distributed information you want associated with an element, for example you could use it to associate a score with a player, or a team with a vehicle.

	Element data is synchronized between the server and the client. Setting data from any of the two sides will force an update in the other, triggering the corresponding element data change events. This is very useful, as it provides a simple way to keep element properties synced without having to set special events to do it manually. This also means that excessive use of element data to store variables that are not required by both server and client becomes a waste of bandwidth.		Element data is synchronized by default between the server and the client (you can disable it via fourth argument in [[setElementData]]. Setting data from any of the two sides will force an update in the other, triggering the corresponding element data change events. This is very useful, as it provides a simple way to keep element properties synced without having to set special events to do it manually. This also means that excessive use of element data to store variables that are not required by both server and client becomes a waste of bandwidth.

	Since not all ~~datatypes~~ can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.		Since not all data types can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.

	==Relevant functions==		==Relevant functions==

Lettify: Indexing of the Portuguese version

2020-10-06T22:30:20Z

Indexing of the Portuguese version

← Older revision		Revision as of 22:30, 6 October 2020
Line 12:		Line 12:
	* [[onElementDataChange]]: triggered on the server after element data is changed.		* [[onElementDataChange]]: triggered on the server after element data is changed.
	* [[onClientElementDataChange]]: triggered on the client after element data is changed.		* [[onClientElementDataChange]]: triggered on the client after element data is changed.
			[[pt-br:Element_data]]

MrTasty at 12:28, 8 October 2018

2018-10-08T12:28:34Z

← Older revision		Revision as of 12:28, 8 October 2018
Line 8:		Line 8:
	* [[setElementData]]: sets an element data value.		* [[setElementData]]: sets an element data value.
	* [[getElementData]]: retrieves an element data value.		* [[getElementData]]: retrieves an element data value.

			==Relevant events==
			* [[onElementDataChange]]: triggered on the server after element data is changed.
			* [[onClientElementDataChange]]: triggered on the client after element data is changed.

Talidan at 13:11, 22 October 2007

2007-10-22T13:11:50Z

← Older revision		Revision as of 13:11, 22 October 2007
Line 1:		Line 1:
	Each [[element]] that is loaded is able to have [[element data]] values attached to it. These are values that can be accessed using a keyword string and directly correspond to the element's attributes in the map file, unless changed via scripting. Element data is a good way to store distributed information you want associated with an element, for example you could use it to associate a score with a player, or a team with a vehicle.		Each [[element]] that is loaded is able to have [[element data]] values attached to it. These are values that can be accessed using a keyword string and directly correspond to the element's attributes in the map file, unless changed via scripting. Element data is a good way to store distributed information you want associated with an element, for example you could use it to associate a score with a player, or a team with a vehicle.

	Element data is synchronized between the server and the client. Setting data from any of the two sides will force an update in the other, triggering the corresponding element data change events. This is very useful, as it provides a simple way to keep element properties synced without having to set special events to do it manually.		Element data is synchronized between the server and the client. Setting data from any of the two sides will force an update in the other, triggering the corresponding element data change events. This is very useful, as it provides a simple way to keep element properties synced without having to set special events to do it manually. This also means that excessive use of element data to store variables that are not required by both server and client becomes a waste of bandwidth.

	Since not all datatypes can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.		Since not all datatypes can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.

Jbeta at 15:27, 30 August 2007

2007-08-30T15:27:17Z

← Older revision		Revision as of 15:27, 30 August 2007
Line 6:		Line 6:

	==Relevant functions==		==Relevant functions==
	* [[setElementData]]: ~~Sets~~ an element data value.		* [[setElementData]]: sets an element data value.
	* [[getElementData]]: ~~Retrieve~~ an element data value.		* [[getElementData]]: retrieves an element data value.

Jbeta: Updated

2007-08-30T15:26:49Z

Updated

← Older revision		Revision as of 15:26, 30 August 2007
Line 1:		Line 1:
	Each [[element]] that is loaded is able to have [[element data]] values attached to it. These are values that can be accessed using a keyword string and directly correspond to the element's attributes in the map file. [[Element data]] is a good way to store information you want associated with an element, for example you could use it to associate a score with a player, or a team with a vehicle.		Each [[element]] that is loaded is able to have [[element data]] values attached to it. These are values that can be accessed using a keyword string and directly correspond to the element's attributes in the map file, unless changed via scripting. Element data is a good way to store distributed information you want associated with an element, for example you could use it to associate a score with a player, or a team with a vehicle.

			Element data is synchronized between the server and the client. Setting data from any of the two sides will force an update in the other, triggering the corresponding element data change events. This is very useful, as it provides a simple way to keep element properties synced without having to set special events to do it manually.

			Since not all datatypes can be packetized to be transferred, there are some restrictions. The types that cannot be stored as element data are ''non-element userdata'' (see [[MTA Classes]]), ''functions'' and ''threads''. Also, you may not send tables which contain one or more values of any of these types.

	==Relevant functions==		==Relevant functions==
	* [[setElementData]] ~~- Set~~ an element data value		* [[setElementData]]: Sets an element data value.
	* [[getElementData]] - Retrieve an element data value		* [[getElementData]]: Retrieve an element data value.

	~~[[Category:Stub]]~~