xox

==Introduction==
Resources Mta का एक महत्वपूर्ण हिस्सा हैं. एक Resources अनिवार्य रूप से फाइलों का एक संग्रह है जिसमें एक फोल्डर या ज़िप फाइल है, plus Resources लोड किया जाना चाहिए कि कैसे सर्वर से वर्णन किया गया है और इसे नियंत्रित करता है क्या फ़ाइलों कि एक मेटा फ़ाइल. इसे शुरू कर दिया जा सकता और बंद कर दिया जा सकता है, और कई  Resources में एक बार चला सकते हैं.

पटकथा के साथ क्या करने के लिए सब कुछ है कि Resources में होता है. यह एक gamemode , एक नक्शा या कुछ और है कि अगर एक Resource परिभाषित करता है क्या. Mta इस तरह के एक खेल के मैदान के भीतर playings रखने के लिए maplimits या हथियार पिकप बनाने के लिए deathpickups के रूप में आप अपने gamemodes में उपयोग वैकल्पिक कर सकते हैं कि Resources के साथ आता है.
{{tip|Lua scripting शुरू करने के लिए आपका पहला कदम एक Lua editor का उपयोग किया जाना चाहिए. यह Scripting बहुत आसान बना देता है. हम अनुशंसा करते हैं[http://www.sublimetext.com/ Sublime Text], [http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] या [http://luaedit.sourceforge.net/ LuaEdit]. यह भी एक unoficial hai[[MTASE|MTA Script Editor]].}}
आप बाहर का परीक्षण कर सकते हैं.

==एक काम ki स्क्रिप्ट बनान==
हम पहले कदम से शहर , चरण में चारों ओर खिलाड़ी की पैदल दूरी पर देता है कि एक बुनियादी स्क्रिप्ट कैसे बनाने के लिए सीखना होगा।

===जहां सभी scripts क ha रहे हैं?===
स्क्रिप्ट की फ़ाइल संरचना पर एक नज़र रखना। अपने एमटीए सर्वर फ़ोल्डर में जाओ , और नीचे पथ का पालन करें:
सर्वर / Mods / Deathmatch / संसाधन /
आप एमटीए के साथ भेज दिया पैकेज्ड नमूना स्क्रिप्ट हैं जो .zip फ़ाइलें, का एक बहुत देखेंगे। प्रत्येक फ़ाइल एक "संसाधन " है, और यह शुरू होता है जब वे सभी सर्वर द्वारा unzipped और लोड किया जाएगा। अपने खुद के संसाधन बनाने के लिए, बस अपने पसंदीदा नाम से एक फोल्डर बना । हम इस ट्यूटोरियल के लिए " myserver " का उपयोग करेंगे।
अब आप इस निर्देशिका के तहत किया जाना चाहिए :

server/mods/deathmatch/resources/myserver/

===अपने resource की पहचान===
सर्वर संसाधन में क्या है यह बताने के लिए आदेश में , एक meta.xml फ़ाइल संसाधन की सामग्री की सूची के लिए बनाया जाना चाहिए। यह हमारे मामले में " myserver " फ़ोल्डर है जो संसाधन के रूट निर्देशिका में स्थित होना चाहिए । तो एक पाठ फ़ाइल बना सकते हैं और " meta.xml " यह नाम है, और नोटपैड के साथ खुला ।
Meta.xml फ़ाइल में निम्नलिखित कोड दर्ज करें:
<code>[xml]
<meta>
     <info author="aapkanam" type="gamemode" name="My Server" description="My first MTA server" />
     <script src="script.lua" />
</meta>
</code>
< info / > टैग में, संसाधन के बजाय एक नियमित रूप से एक gamemode शामिल है या बाद में समझाया जाएगा , जो एक नक्शा, इंगित करता है कि जो एक "प्रकार" क्षेत्र नहीं है। एक gamemode आप एक स्टैंड-अलोन सर्वर बनाने की जरूरत क्या है ।
< script / > टैग हम अगले पैदा करेगा जो संसाधन , में निहित स्क्रिप्ट फ़ाइलें इंगित करता है।.

===एक साधारण Script बनाना===
इसके बाद के संस्करण < script /> टैग में , .lua फ़ाइल एक और निर्देशिका के अंतर्गत नहीं है कि ध्यान दें। इसलिए हम meta.xml के रूप में एक ही फ़ोल्डर में फाइल बना देंगे। अब आप को कॉपी और script.lua में निम्न कोड पेस्ट कर सकते हैं :
<code>[lua]
local spawnX, spawnY, spawnZ = 1959.55, -1714.46, 10
function joinHandler()
	spawnPlayer(source, spawnX, spawnY, spawnZ)
	fadeCamera(source, true)
	setCameraTarget(source, source)
	outputChatBox("Welcome to My Server", source)
end
addEventHandler("onPlayerJoin", getRootElement(), joinHandler)
</code>
आप इस खेल में शामिल होने जब ​​स्क्रिप्ट, ऊपर निर्दिष्ट समन्वय (x, y, z ) में आप अंडे जाएगा। FadeCamera समारोह इस्तेमाल किया जाना चाहिए या स्क्रीन काला हो जाएगा कि ध्यान दें। इसके अलावा, DP2 के बाद रिलीज में , आप कैमरे के लक्ष्य निर्धारित करने की जरूरत है (अन्यथा देखेंगे सभी खिलाड़ी नीले आकाश है )।
स्रोत चर घटना शुरू हो जो इंगित करता है। कोड शुरू हो रहा है जब एक खिलाड़ी शामिल हो गया है , इसलिए आप शामिल हो गया है जो देखने के लिए इस चर का उपयोग करें। तो यह बजाय हर किसी की है कि खिलाड़ी या एक यादृच्छिक व्यक्ति अंडे देंगे।
यह आरंभ होता है जब जो इंगित करता है , ' onPlayerJoin ': हम [[addEventHandler]] पर एक करीब देखो है, तो आप तीन चीजें देख सकते हैं । यह चालू किया जा सकता है जो क्या / द्वारा जो दिखाता है getRootElement (), । और घटना शुरू हो जाने के बाद चालू किया जा करने के लिए है कि समारोह में इंगित करता है जो joinHandler , ( getRootElement () सब कुछ / हर कोई है )। अन्य विवरण बाद में एक अन्य उदाहरण में समझाया जाएगा , अब चलो बस सर्वर चलाने के लिए और इसे बाहर की कोशिश करते हैं!


===Running the script/स्क्रिप्ट रनिंग===
सर्वर प्राप्त करने के लिए बस सर्वर / निर्देशिका के अंतर्गत निष्पादन योग्य चलाने के लिए, शुरू कर दिया। सर्वर आँकड़े की सूची के पहले दिखाया जाएगा; खेल में शामिल होने के लिए जब आप की आवश्यकता होगी जो पोर्ट संख्या, ध्यान दें। फिर सर्वर Mods / Deathmatch / संसाधन / निर्देशिका के अंतर्गत भार सभी संसाधनों, और फिर "कनेक्शन स्वीकार करने के लिए तैयार हो जाओ!"

आप सर्वर से कनेक्ट करने से पहले, आप gamemode चलाना चाहिए। टाइप करें "myserver शुरू" और प्रेस दर्ज करें। सर्वर आपने अभी बनाया gamemode शुरू होगा, और यह भी इस बात से किसी भी त्रुटि और चेतावनियों को दिखाएगा। अब आप एमटीए ग्राहक शुरू, और अपने सर्वर का आईपी पता है और आप पहले देखा था पोर्ट नंबर का उपयोग कर "त्वरित कनेक्ट कर सकते हैं"। सब कुछ ठीकठाक रहा, तो कुछ ही सेकंड बाद अपने चरित्र लॉस सैंटोस की सड़कों पर चलने दिया जाएगा।

अगले हम खिलाड़ियों को अपनी स्थिति के बगल में एक वाहन के अंडे के लिए उपयोग कर सकते हैं कि आपकी स्क्रिप्ट के लिए एक कमांड जोड़ देंगे। आप इसे छोड़ और के साथ और अधिक उन्नत पटकथा बाहर की जाँच कर सकते हैं [[Map manager|Map Manager]] इस ट्यूटोरियल जारी है, जो। इस ट्यूटोरियल से एक और शाखा, आप एमटीए में यूजर इंटरफेस खींचा और पटकथा है कि कैसे ग्राफिकल यह देखने के लिए अनुसरण कर सकते हैं [[Introduction to Scripting GUI]] है।

===एक सरल कमांड बनाना===
की ' ' script.lua '' फाइल की सामग्री को वापस करने के लिए चलते हैं। जैसा कि ऊपर कहा , हम इस खेल में अपनी वर्तमान स्थिति के बगल में एक वाहन बनाने के लिए एक आदेश प्रदान करना चाहते हैं । सबसे पहले हम हम कॉल करना चाहते हैं एक समारोह और खिलाड़ी कंसोल में प्रवेश करने में सक्षम हो जाएगा आदेश बनाता है एक आदेश हैंडलर बनाने की जरूरत है ।

<code>[lua]
-- create the function the command handler calls, with the arguments: thePlayer, command, vehicleModel
function createVehicleForPlayer(thePlayer, command, vehicleModel)
   -- create a vehicle and stuff
end

-- create a command handler
addCommandHandler("createvehicle", createVehicleForPlayer)
</code>

'' नोट: समारोह के नाम विकी पर कोड के उदाहरण में क्लिक करने योग्य और कार्यों से जुड़े रहे हैं ' प्रलेखन ।''

====About command handlers====
The first argument of [[addCommandHandler]] is the name of the command the player will be able to enter, the second argument is the function this will call, in this case ''createVehicleForPlayer''.

If you have already experience in scripting, you will know that you call a function like this:
<code>[lua]
functionName(argument1, argument2, argument3, ..)
</code>
<code>[lua]
functionName(thePlayer, commandName, argument3, ..)
</code>
If we have a closer look on the lower example above, we can see argument1 is thePlayer and argument2 the commandName. thePlayer is simply the one who typed the command, so whatever you call it, the variable will contain the player who activated the command. commandName is simply the command they typed. So if they typed "/greet", this argument will contain "greet". Argument 3 is something extra the player typed, you'll learn it a little bit further in the tutorial. Never forget that the first 2 arguments are standard arguments, but you can name them to anything you want.

We called the [[addCommandHandler]] function this way already and since ''createVehicleForPlayer'' is a function too, it can be called that way as well. But we are using a command handler for that, which calls it in a similiar manner, internally.

For example: Someone types "createvehicle 468" ingame in the console to spawn a Sanchez, the command handler calls the createVehicleForPlayer function, as '''if''' we would have this line of code in the script:
<code>[lua]
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer is the player element of the player who entered the command
</code>
As we can see, it provides several parameters: the player who called the command, the command he entered and whatever text he had after that, in this case "468" as vehicle id for the Sanchez. The first two parameters are the same with all command handlers, which you can read on the [[addEventHandler]] page. For this fact, you always have to define at least those two parameters to use any after that (for example to process text that was entered after the command, like in our example the vehicle model id).

''Note: You have to add the command handler AFTER you defined the handler function, else it can't find it. The order of execution matters.''

====Writing the function====
In order to fill the function we created, we need to think about what we have to do:
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)
* Spawn the vehicle
* Check if it has been spawned successfully, or output a message

In order to achieve our goals, we have to use several functions. To find function we need to use, we should visit the [[Scripting Functions|Server Functions List]]. First we need a function to get the players position. Since players are Elements, we first jump to the '''Element functions''' where we find the [[getElementPosition]] function. By clicking on the function name in the list, you get to the function description. There we can see the syntax, what it returns and usually an example. The syntax shows us what arguments we can or have to submit.

For [[getElementPosition]], the syntax is:
<code>[lua]
float, float, float getElementPosition ( element theElement )
</code>

The three ''float'' in front of the function name are the return type. In this case it means the function returns three floating point numbers. (x, y and z) Within the parentheses, you can see what arguments you have to submit. In this case only the element whose position you want to get, which is the player in our example.

<code>[lua]
function createVehicleForPlayer(thePlayer, command, vehicleModel)
	-- get the position and put it in the x,y,z variables
	-- (local means, the variables only exist in the current scope, in this case, the function)
	local x,y,z = getElementPosition(thePlayer)
end
</code>

Next we want to ensure that the vehicle won't spawn directly in the player, so we add a few units to the ''x'' variable, which will make it spawn east from the player.

<code>[lua]
function createVehicleForPlayer(thePlayer, command, vehicleModel)
	local x,y,z = getElementPosition(thePlayer) -- get the position of the player
	x = x + 5 -- add 5 units to the x position
end
</code>

Now we need another function, one to spawn a vehicle. We once again search for it on the [[Scripting Functions|Server Functions List]], this time - since we are talking about vehicles - in the '''Vehicle functions''' section, where we will choose [[createVehicle]]. In this function's syntax, we only have one return type (which is more common), a vehicle element that points to the vehicle we just created. Also, we see that some arguments are enclosed within [ ] which means that those are optional.

We already have all arguments we need for [[createVehicle]] in our function: The position we just calculated in the ''x,y,z'' variables and the model id that we provided through the command ("createvehicle 468") and can access in the function as ''vehicleModel'' variable.

<code>[lua]
function createVehicleForPlayer(thePlayer, command, vehicleModel)
	local x,y,z = getElementPosition(thePlayer) -- get the position of the player
	x = x + 5 -- add 5 units to the x position
	-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable
	local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)
end
</code>

Of course this code can be improved in many ways, but at least we want to add a check whether the vehicle was created successfully or not. As we can read on the [[createVehicle]] page under '''Returns''', the function returns ''false'' when it was unable to create the vehicle. Thus, we check the value of the ''createVehicle'' variable.

Now we have our complete script:
<code>[lua]
function createVehicleForPlayer(thePlayer, command, vehicleModel)
	local x,y,z = getElementPosition(thePlayer) -- get the position of the player
	x = x + 5 -- add 5 units to the x position
	local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)
	-- check if the return value was ''false''
	if (createdVehicle == false) then
		-- if so, output a message to the chatbox, but only to this player.
		outputChatBox("Failed to create vehicle.",thePlayer)
	end
end
addCommandHandler("createvehicle", createVehicleForPlayer)
</code>

As you can see, we introduced another function with [[outputChatBox]]. By now, you should be able to explore the function's documentation page yourself. For more advanced scripting, please check out the [[Map manager|Map Manager]].

==What you need to know==
You already read some things about resources, command handlers and finding functions in the documentation in the first paragraph, but there is much more to learn. This section will give you a rather short overview over some of these things, while linking to related pages if possible.
===Clientside and Serverside scripts===
You may have already noticed these or similiar terms (Server/Client) somewhere on this wiki, mostly in conjunction with functions. MTA not only supports scripts that run on the server and provide commands (like the one we wrote above) or other features, but also scripts that run on the MTA client the players use to connect to the server. The reason for this is, that some features MTA provides have to be clientside (like a GUI - Graphical User Interface), others should be because they work better and still others are better off to be serverside or just don't work clientside.

Most scripts you will make (gamemodes, maps) will probably be serverside, like the one we wrote in the first section. If you run into something that can't be solved serverside, you will probably have to make it clientside. For a clientside script for example, you would create a ordinary script file (for example called ''client.lua'') and specify it in the meta.xml, like this:
<code>[xml]
<script src="client.lua" type="client" />
</code>
The ''type'' attribute defaults to 'server', so you only need to specify it for clientside scripts. When you do this, the clientside script will be downloaded to the player's computer once he connects to the server. Read more about [[Client side scripts]].

===More complex resources===
The previous section showed briefly how to add clientside scripts to the resource, but there is also much more possible. As mentioned at the very top of this page, resources can be pretty much everything. Their purpose is defined by what they do. Let's have some theoretical resources, by looking at the files it contains, the ''meta.xml'' and what they might do:

====First example - A utility script====
<code>[xml]
/admin_commands
	/meta.xml
	/commands.lua
	/client.lua
</code>
<code>[xml]
<meta>
	<info author="Someguy" description="admin commands" />
	<script src="commands.lua" />
	<script src="client.lua" type="client" />
</meta>
</code>

* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily

This example might be running all the time (maybe even auto-started when the server starts) as it's useful during the whole gaming experience and also wont interfere with the gameplay, unless an admin decides to take some action of course.

====Second example - A gamemode====
<code>[xml]
/counterstrike
	/meta.xml
	/counterstrike.lua
	/buymenu.lua
</code>
<code>[xml]
<meta>
	<info author="Someguy" description="Counterstrike remake" type="gamemode" />
	<script src="counterstrike.lua" />
	<script src="buymenu.lua" type="client" />
</meta>
</code>

* The ''counterstrike.lua'' contains similiar to the following features:
** Let players choose their team and spawn them
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)
** Define the game's rules, e.g. when does the round end, what happens when a player dies
** .. and maybe some more
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons

This example can be called a gamemode, since it not only intereferes with the gameplay, but actually defines the rules of it. The ''type'' attribute indicates that this example works with the [[Map manager]], yet another resource that was written by the QA Team to manage gamemodes and map loading. It is highly recommended that you base your gamemodes on the techniques it provides.

This also means that the gamemode probably won't run without a map. Gamemodes should always be as generic as possible. An example for a map is stated in the next example.

====Third example - A Map====
<code>[xml]
/cs-airport
	/meta.xml
	/airport.map
	/airport.lua
</code>
<code>[xml]
<meta>
	<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" />
	<map src="airport.map" />
	<script src="airport.lua" />
</meta>
</code>

* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:
** Where the players should spawn, with what weapons, what teams there are
** What the targets are
** Weather, World Time, Timelimit
** Provide vehicles
* The ''airport.lua'' might contain map-specific features, that may include:
** Opening some door/make something explode when something specific happens
** Create or move some custom objects, or manipulate objects that are created through the .map file
** .. anything else map-specific you can think of

As you can see, the ''type'' attribute changed to 'map', telling the [[Map manager]] that this resource is a map, while the ''gamemodes'' attribute tells it for which gamemodes this map is valid, in this case the gamemode from the above example.
What may come as a surprise is that there is also a script in the Map resource. Of course this is not necessarily needed in a map, but opens a wide range of possibilities for map makers to create their own world within the rules of the gamemode they create it for.

The ''airport.map'' file might look similiar to this:
<code>[xml]
<map mode="deathmatch" version="1.0">
	<terrorists>
		<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" />
	</terrorists>
	<counterterrorists>
		<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" />
	</counterterrorists>

	<bomb posX="23342.23" posY="" posZ="" />

	<vehicle posX="" posY="" posZ="" model="602" />
	<vehicle posX="" posY="" posZ="" model="603" />
</map>
</code>

When a gamemode is started with a map, the map resources is automatically started by the mapmanager and the information it contains can be read by the gamemode resource. When the map changes, the current map resource is stopped and the next map resource is started. For a more in-depth explanation and examples of how map resources are utilized in the main script, please visit the [[Writing Gamemodes]] page.

===Events===
[[Event|Events]] are the way MTA tells scripts about things that happen. For example when a player dies, the [[onPlayerWasted]] event is triggered. In order to perform any actions when a player dies, you have to prepare yourself similiar to adding a command handler, as shown in [[#Writing_the_script|the first chapter]].

This example will output a message with the name of the player who died:
<code>[lua]
function playerDied(totalAmmo, killer, killerWeapon, bodypart)
	outputChatBox(getPlayerName(source).." died!")
end
addEventHandler("onPlayerWasted",getRootElement(),playerDied)
</code>

Instead of showing what arguments are needed, the documentation page for Events shows what parameters are passed to the handler function, similiar to the way a [[#About_command_handlers|command handler]] does, just that it is different from event to event. Another important point is the ''source'' variable, that exists in handler functions. It doesn't have to be added to the parameter list of the function, but it still exists. It has a different value from event to event, for player events (as in the example above) it is the player element. As another example, you can take a look at the basic spawning player script in the first section to get an idea how ''source'' is used.

==Where to go from here==
You should now be familiar with the most basic aspects of MTA scripting and also a bit with the documentation. The [[Main Page]] provides you with links to more information, Tutorials and References that allow a deeper look into the topics you desire to learn about.
{{note|From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts. We also recommend you to use the [[predefined variables list]] to help you with certain tasks and make scripting easier and faster.}}
'''See also:'''
* [[OOP_Introduction|OOP Scripting Introduction]]
* [[Advanced Topics]]
* [[Script_security|Script security]]
* [[Scripting Introduction Urdu]]
[[es:Introducción a la Programación]]
[[it:Introduzione allo scripting]]
[[nl:Scripting_introductie]]
[[pt-br:Introdução ao Scripting]]
[[ru:Scripting Introduction]]
[[ar:مقدمه_في_البرمجه]]
[[zh-cn:脚本编写介绍]]
[[Category:Tutorials]]