Resources - Revision history

BotGrzesieKK: adding polish site

2021-08-20T21:37:34Z

adding polish site

← Older revision		Revision as of 21:37, 20 August 2021
Line 95:		Line 95:
	[[pt-br:Recursos]]		[[pt-br:Recursos]]
	[[ru:Resources]]		[[ru:Resources]]
			[[pl:Zasoby]]

Haxardous at 19:46, 19 April 2020

2020-04-19T19:46:43Z

Surge: Undo revision 60146 by Surge (talk)

2018-10-28T22:37:33Z

Undo revision 60146 by Surge (talk)

← Older revision		Revision as of 22:37, 28 October 2018
Line 51:		Line 51:
	Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".		Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".

	~~Az ''~~include'' tag ~~megadja egy resource-nak, hogy előbb induljon el, mint egy másik resource~~. ~~Más szóval~~, ~~ha egy~~ resource ~~függ egy másiktól resource-től~~, ~~akkor itt megadhatja, hogy a másik~~ resource ~~induljon el előbb~~.		The include tag specifies other resources that should be started before this resoucre is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first.


	~~Minden resourcenak saját virtuális gépe van~~ (VM). ~~Ez tartalmazza a~~ resource ~~összes script-jét~~. ~~Ez azt jelenti, hogy a változókat nem lehet megosztani egy másik resource-val~~. ~~A legjobb módja annak, hogy más resource-kkal tudjon kommunkálni, használja a~~ ''export'' ~~tagot, és exportáljon~~ function-t. This will enable other resources to fire this function using the [[call]] scripting function.		Each resource has its own virtual machine (VM). This contains every script in the resource. This means that variables are not shared with other resources. The best way to communicate with other resources is by using the ''export'' tag and exporting a function. This will enable other resources to fire this function using the [[call]] scripting function.

Surge: /* The Meta File */

2018-10-28T22:34:23Z

The Meta File

← Older revision		Revision as of 22:34, 28 October 2018
Line 51:		Line 51:
	Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".		Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".

	~~The~~ include tag ~~specifies other resources that should be started before this resoucre is started~~. ~~In other words~~, ~~if your~~ resource ~~is dependent on another~~, ~~you can include it so that the other~~ resource ~~is started first~~.		Az ''include'' tag megadja egy resource-nak, hogy előbb induljon el, mint egy másik resource. Más szóval, ha egy resource függ egy másiktól resource-től, akkor itt megadhatja, hogy a másik resource induljon el előbb.


	~~Each resource has its own virtual machine~~ (VM). ~~This contains every~~ script ~~in the~~ resource. ~~This means that variables are not shared with other resources. The best way to communictate with other resources is by using the~~ ''export'' ~~tag and exporting a~~ function. This will enable other resources to fire this function using the [[call]] scripting function.		Minden resourcenak saját virtuális gépe van (VM). Ez tartalmazza a resource összes script-jét. Ez azt jelenti, hogy a változókat nem lehet megosztani egy másik resource-val. A legjobb módja annak, hogy más resource-kkal tudjon kommunkálni, használja a ''export'' tagot, és exportáljon function-t. This will enable other resources to fire this function using the [[call]] scripting function.

Surge at 22:12, 28 October 2018

2018-10-28T22:12:46Z

← Older revision		Revision as of 22:12, 28 October 2018
Line 51:		Line 51:
	Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".		Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".

	The include tag specifies other resources that should be started before this resoucre is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first,		The include tag specifies other resources that should be started before this resoucre is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first.

Myonlake: Undo revision 58215 by WolfPiotrK2 (talk)

2018-08-16T12:49:13Z

Undo revision 58215 by WolfPiotrK2 (talk)

← Older revision		Revision as of 12:49, 16 August 2018
Line 1:		Line 1:
	[[~~Image~~:~~mtapl~~.~~jpg~~]]		Resources are a key part of MTA. A resource is essentially a folder or zip file that contains a collection of files - including script files, plus a ''meta'' file that describes how the resource should be loaded. A resource can be seen as being partly equivalent to a program running in an operating system - it can be started and stopped, and multiple resources can run at once. Its worth remember though, that unlike programs on an operating system, there is no multi-tasking between resources.

			==Terminology==
			* '''Resource''' - A zip file or folder containing a meta.xml file and a number of resource items. These are placed in the ''mods/deathmatch/resources'' folder in the server directory.
			* '''Resource item''' - A file contained within a resource, currently this can be a map, script, images etc.

			==The Meta File==
			''See main article [[Meta.xml]] for details''

			The Meta file is the core of each the resource. It describes exactly what files in the resource should be used, and how. The following is an example that covers every option there is, your meta files can have as many or as few of these tags as you require:

			<syntaxhighlight lang="xml">
			<meta>
			<info author="eAi" description="This is a basic CTF script" version="4"/>

			<include resource="radarblips"/>
			<include resource="markermanagement" />

			<script src="ctf.lua" />
			<script src="flag.lua" />
			<script src="ctf_client.lua" type="client" />

			<file src="model.dff" />
			<file src="quitbutton.png" />
			<file src="killed.png" />

			<html src="test.htm" default="true"/>
			<html src="logo.png" raw="true" />

			<export function="multiply" http="true" />
			<export function="getPlayerList" />
			<export function="getElementOwner" type="client"/>

			<config src="vehicle-list.xml" type="client" />
			<config src="markerconfig.xml" type="server" />

			<map src="somestuff.map" dimension="99" />
			</meta>
			</syntaxhighlight>
			While a CTF map may have a meta.xml that looks like:
			<syntaxhighlight lang="xml">
			<meta>
			<include resource="ctf" />
			<map src="myuberl33tctfmap.map" />

			<info author="Tom" instructions="this is uber l33t !!!!!1111111" type="map" />
			</meta>
			</syntaxhighlight>


			Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".

			The include tag specifies other resources that should be started before this resoucre is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first,


			Each resource has its own virtual machine (VM). This contains every script in the resource. This means that variables are not shared with other resources. The best way to communictate with other resources is by using the ''export'' tag and exporting a function. This will enable other resources to fire this function using the [[call]] scripting function.


			Scripts sent to clients are started as soon as all the scripts have been downloaded.


			Scripts are able to read and write to their own resource folder with functions such as [[xmlCreateFile]] and [[fileCreate]]. They can also read and write to other resources, but must have [[Access_Control_List\|ACL]] access.


			Each resource can only be loaded once, the server will ensure this. If a resource is included more than once, the same instance will be used by each resource that includes it.

			==File storage==
			Resource files can either be stored in a zip or a directory. This is located in:

			server/mods/deathmatch/resources/ (if you've installed your server with the client)

			or

			mods/deathmatch/resources/ (for dedicated server installations)

			Each resource can have a zip file, a directory or both. In the case of both existing, the directory has precedence over the zip file, as such files can be placed in the directory to over-ride the files in the zip file. This allows directories to be used for testing and developing of maps/scripts while zip files used by end-users.

			==Other things to note==
			*Resource names can't have dots in.
			*If the resource does any file saving, the file names used should not be listed in the meta.xml
			*Files listed in the meta.xml should be considered read only by your scripts. Do not modify them with xmlSaveFile, FileSave etc.
			*When making a zip file of your resource, do not include save files. If your resource uses save files, they must be created by your resource when needed.
			*When making a zip file of your resource, only include files that are listed in the meta.xml. Do not include 'example' save files, otherwise bad things will happen.
			*We recommend avoiding spaces and exotic characters from resources names.

			==Script functions==
			The resource system can be manipulated by script. As such, the following Serverside scripting functions are provided:
			{{Resource functions}}

			The following events are also provided:
			{{Resource_events}}

			[[hu:Resources]]
			[[it:Introduzione alle Risorse]]
			[[pt-br:Recursos]]
			[[ru:Resources]]

WolfPiotrK2: Replaced content with "Image:mtapl.jpg"

2018-08-16T12:45:59Z

Replaced content with "Image:mtapl.jpg"

← Older revision		Revision as of 12:45, 16 August 2018
Line 1:		Line 1:
	Resources are a key part of MTA. A resource is essentially a folder or zip file that contains a collection of files - including script files, plus a ''meta'' file that describes how the resource should be loaded. A resource can be seen as being partly equivalent to a program running in an operating system - it can be started and stopped, and multiple resources can run at once. Its worth remember though, that unlike programs on an operating system, there is no multi-tasking between resources.		[[Image:mtapl.jpg]]

	~~==Terminology==~~
	* '''Resource''' - A zip file or folder containing a meta.xml file and a number of resource items. These are placed in the ''mods/deathmatch/resources'' folder in the server directory.
	* '''Resource item''' - A file contained within a resource, currently this can be a map, script, images etc.

	~~==The Meta File==~~
	~~''See main article~~ [[~~Meta.xml]] for details''~~

	The Meta file is the core of each the resource. It describes exactly what files in the resource should be used, and how. The following is an example that covers every option there is, your meta files can have as many or as few of these tags as you require:

	~~<syntaxhighlight lang="xml">~~
	~~<meta>~~
	~~<info author="eAi" description="This is a basic CTF script" version="4"/>~~

	~~<include resource="radarblips"/>~~
	~~<include resource="markermanagement" />~~

	~~<script src="ctf.lua" />~~
	~~<script src="flag.lua" />~~
	~~<script src="ctf_client.lua" type="client" />~~

	~~<file src="model.dff" />~~
	~~<file src="quitbutton.png" />~~
	~~<file src="killed.png" />~~

	~~<html src="test.htm" default="true"/>~~
	~~<html src="logo.png" raw="true" />~~

	~~<export function="multiply" http="true" />~~
	~~<export function="getPlayerList" />~~
	~~<export function="getElementOwner" type="client"/>~~

	~~<config src="vehicle-list.xml" type="client" />~~
	~~<config src="markerconfig.xml" type="server" />~~

	~~<map src="somestuff.map" dimension="99" />~~
	~~</meta>~~
	~~</syntaxhighlight>~~
	~~While a CTF map may have a meta.xml that looks like~~:
	~~<syntaxhighlight lang="xml">~~
	~~<meta>~~
	~~<include resource="ctf" />~~
	~~<map src="myuberl33tctfmap.map" />~~

	~~<info author="Tom" instructions="this is uber l33t !!!!!1111111" type="map" />~~
	~~</meta>~~
	~~</syntaxhighlight>~~


	~~Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server"~~.

	The include tag specifies other resources that should be started before this resoucre is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first,


	Each resource has its own virtual machine (VM). This contains every script in the resource. This means that variables are not shared with other resources. The best way to communictate with other resources is by using the ''export'' tag and exporting a function. This will enable other resources to fire this function using the [[call]] scripting function.


	~~Scripts sent to clients are started as soon as all the scripts have been downloaded.~~


	Scripts are able to read and write to their own resource folder with functions such as [[xmlCreateFile]] and [[fileCreate]]. They can also read and write to other resources, but must have [[Access_Control_List\|ACL]] access.


	~~Each resource can only be loaded once, the server will ensure this. If a resource is included more than once, the same instance will be used by each resource that includes it.~~

	~~==File storage==~~
	~~Resource files can either be stored in a zip or a directory. This is located in:~~

	~~server/mods/deathmatch/resources/ (if you've installed your server with the client)~~

	or

	~~mods/deathmatch/resources/ (for dedicated server installations)~~

	Each resource can have a zip file, a directory or both. In the case of both existing, the directory has precedence over the zip file, as such files can be placed in the directory to over-ride the files in the zip file. This allows directories to be used for testing and developing of maps/scripts while zip files used by end-users.

	~~==Other things to note==~~
	*Resource names can't have dots in.
	*If the resource does any file saving, the file names used should not be listed in the meta.xml
	*Files listed in the meta.xml should be considered read only by your scripts. Do not modify them with xmlSaveFile, FileSave etc.
	*When making a zip file of your resource, do not include save files. If your resource uses save files, they must be created by your resource when needed.
	*When making a zip file of your resource, only include files that are listed in the meta.xml. Do not include 'example' save files, otherwise bad things will happen.
	*We recommend avoiding spaces and exotic characters from resources names.

	~~==Script functions==~~
	~~The resource system can be manipulated by script. As such, the following Serverside scripting functions are provided:~~
	~~{{Resource functions}}~~

	~~The following events are also provided:~~
	~~{{Resource_events}}~~

	~~[[hu:Resources]]~~
	~~[[it:Introduzione alle Risorse]]~~
	~~[[pt-br:Recursos]]~~
	~~[[ru:Resources~~]]

Surge at 12:55, 30 July 2018

2018-07-30T12:55:23Z

← Older revision		Revision as of 12:55, 30 July 2018
Line 91:		Line 91:
	{{Resource_events}}		{{Resource_events}}

			[[hu:Resources]]
	[[it:Introduzione alle Risorse]]		[[it:Introduzione alle Risorse]]
	[[pt-br:Recursos]]		[[pt-br:Recursos]]
	[[ru:Resources]]		[[ru:Resources]]

JHXP: Reverted edits by Marcin778 (talk) to last revision by Cristiano Cardoso

2017-01-01T18:43:55Z

Reverted edits by Marcin778 (talk) to last revision by Cristiano Cardoso

← Older revision		Revision as of 18:43, 1 January 2017
Line 1:		Line 1:
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~		Resources are a key part of MTA. A resource is essentially a folder or zip file that contains a collection of files - including script files, plus a ''meta'' file that describes how the resource should be loaded. A resource can be seen as being partly equivalent to a program running in an operating system - it can be started and stopped, and multiple resources can run at once. Its worth remember though, that unlike programs on an operating system, there is no multi-tasking between resources.
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~		==Terminology==
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~		* '''Resource''' - A zip file or folder containing a meta.xml file and a number of resource items. These are placed in the ''mods/deathmatch/resources'' folder in the server directory.
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~		* '''Resource item''' - A file contained within a resource, currently this can be a map, script, images etc.
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~		==The Meta File==
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		''See main article [[Meta.xml]] for details''
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~		The Meta file is the core of each the resource. It describes exactly what files in the resource should be used, and how. The following is an example that covers every option there is, your meta files can have as many or as few of these tags as you require:
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<syntaxhighlight lang="xml">
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<meta>
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<info author="eAi" description="This is a basic CTF script" version="4"/>
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<include resource="radarblips"/>
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<include resource="markermanagement" />
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~		<script src="ctf.lua" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<script src="flag.lua" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<script src="ctf_client.lua" type="client" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<file src="model.dff" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<file src="quitbutton.png" />
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~		<file src="killed.png" />
	~~Extrem liże hazowi dupsko~~ a ~~Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<html src="test.htm" default="true"/>
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<html src="logo.png" raw="true" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<export function="multiply" http="true" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<export function="getPlayerList" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<export function="getElementOwner" type="client"/>
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<config src="vehicle-list.xml" type="client" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<config src="markerconfig.xml" type="server" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		<map src="somestuff.map" dimension="99" />
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		</meta>
	~~Extrem liże hazowi dupsko a Barcioo liże cipsko Trinowi~~		</syntaxhighlight>
			While a CTF map may have a meta.xml that looks like:
			<syntaxhighlight lang="xml">
			<meta>
			<include resource="ctf" />
			<map src="myuberl33tctfmap.map" />

			<info author="Tom" instructions="this is uber l33t !!!!!1111111" type="map" />
			</meta>
			</syntaxhighlight>


			Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".

			The include tag specifies other resources that should be started before this resoucre is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first,


			Each resource has its own virtual machine (VM). This contains every script in the resource. This means that variables are not shared with other resources. The best way to communictate with other resources is by using the ''export'' tag and exporting a function. This will enable other resources to fire this function using the [[call]] scripting function.


			Scripts sent to clients are started as soon as all the scripts have been downloaded.


			Scripts are able to read and write to their own resource folder with functions such as [[xmlCreateFile]] and [[fileCreate]]. They can also read and write to other resources, but must have [[Access_Control_List\|ACL]] access.


			Each resource can only be loaded once, the server will ensure this. If a resource is included more than once, the same instance will be used by each resource that includes it.

			==File storage==
			Resource files can either be stored in a zip or a directory. This is located in:

			server/mods/deathmatch/resources/ (if you've installed your server with the client)

			or

			mods/deathmatch/resources/ (for dedicated server installations)

			Each resource can have a zip file, a directory or both. In the case of both existing, the directory has precedence over the zip file, as such files can be placed in the directory to over-ride the files in the zip file. This allows directories to be used for testing and developing of maps/scripts while zip files used by end-users.

			==Other things to note==
			*Resource names can't have dots in.
			*If the resource does any file saving, the file names used should not be listed in the meta.xml
			*Files listed in the meta.xml should be considered read only by your scripts. Do not modify them with xmlSaveFile, FileSave etc.
			*When making a zip file of your resource, do not include save files. If your resource uses save files, they must be created by your resource when needed.
			*When making a zip file of your resource, only include files that are listed in the meta.xml. Do not include 'example' save files, otherwise bad things will happen.
			*We recommend avoiding spaces and exotic characters from resources names.

			==Script functions==
			The resource system can be manipulated by script. As such, the following Serverside scripting functions are provided:
			{{Resource functions}}

			The following events are also provided:
			{{Resource_events}}


			[[it:Introduzione alle Risorse]]
			[[pt-br:Recursos]]
			[[ru:Resources]]

Marcin778 at 18:10, 1 January 2017

2017-01-01T18:10:46Z

Show changes

← Older revision		Revision as of 19:46, 19 April 2020
Line 1:		Line 1:
	Resources are a key part of MTA. A resource is essentially a folder or zip file that contains a collection of files - including script files, plus a ''meta'' file that describes how the resource should be loaded. A resource can be seen as being partly equivalent to a program running in an operating system - it can be started and stopped, and multiple resources can run at once. Its worth ~~remember~~ though, that unlike programs on an operating system, there is no multi-tasking between resources.		Resources are a key part of MTA. A resource is essentially a folder or zip file that contains a collection of files - including script files, plus a ''meta'' file that describes how the resource should be loaded. A resource can be seen as being partly equivalent to a program running in an operating system - it can be started and stopped, and multiple resources can run at once. Its worth remembers though, that unlike programs on an operating system, there is no multi-tasking between resources.

	==Terminology==		==Terminology==
	* '''Resource''' - A zip file or folder containing a meta.xml file and a number of resource items. These are placed in the ''mods/deathmatch/resources'' folder in the server directory.		* '''Resource''' - A zip file or folder containing a meta.xml file and a number of resource items. These are placed in the ''mods/deathmatch/resources'' folder in the server directory.
	* '''Resource item''' - A file contained within a resource, currently this can be a map, script, images etc.		* '''Resource item''' - A file contained within a resource, currently this can be a map, script, images, etc.

	==The Meta File==		==The Meta File==
	''See main article [[Meta.xml]] for details''		''See main article [[Meta.xml]] for details''

	The ~~Meta file~~ is the core of each the resource. It describes exactly what files in the resource should be used, and how. The following is an example that covers every option there is, your ~~meta files~~ can have as many or as few of these tags as you require:		The Metafile is the core of each the resource. It describes exactly what files in the resource should be used, and how. The following is an example that covers every option there is, your metafiles can have as many or as few of these tags as you require:

	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
Line 49:		Line 49:


	Script/type, Config/type and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".		Script/type, Config/type, and File/type attributes specify if the script/resource should be sent to clients or not, and defaults to "server".

	The include tag specifies other resources that should be started before this ~~resoucre~~ is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first.		The include tag specifies other resources that should be started before this resource is started. In other words, if your resource is dependent on another, you can include it so that the other resource is started first.


Line 60:		Line 60:


	Scripts are able to read and write to their own resource folder with functions such as [[xmlCreateFile]] and [[fileCreate]]. They can also read and write to other resources, but must have [[Access_Control_List\|ACL]] access.		Scripts are able to read and write to their own resource folder with functions such as [[xmlCreateFile]] and [[fileCreate]]. They can also read and write to other resources but must have [[Access_Control_List\|ACL]] access.


Line 79:		Line 79:
	*Resource names can't have dots in.		*Resource names can't have dots in.
	*If the resource does any file saving, the file names used should not be listed in the meta.xml		*If the resource does any file saving, the file names used should not be listed in the meta.xml
	*Files listed in the meta.xml should be considered read only by your scripts. Do not modify them with xmlSaveFile, FileSave etc.		*Files listed in the meta.xml should be considered read-only by your scripts. Do not modify them with xmlSaveFile, FileSave etc.
	*When making a zip file of your resource, do not include save files. If your resource uses save files, they must be created by your resource when needed.		*When making a zip file of your resource, do not include save files. If your resource uses to save files, they must be created by your resource when needed.
	*When making a zip file of your resource, only include files that are listed in the meta.xml. Do not include 'example' save files, otherwise bad things will happen.		*When making a zip file of your resource, only include files that are listed in the meta.xml. Do not include 'example' save files, otherwise, bad things will happen.
	*We recommend avoiding spaces and exotic characters from ~~resources~~ names.		*We recommend avoiding spaces and exotic characters from resource names.

	==Script functions==		==Script functions==