https://wiki.multitheftauto.com/api.php?action=feedcontributions&feedformat=atom&user=JaberMulti Theft Auto: Wiki - User contributions [en]2026-04-26T05:00:41ZUser contributionsMediaWiki 1.39.3https://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=49198AR/مقدمه في البرمجه2016-09-19T15:59:53Z<p>Jaber: </p>
<hr />
<div><p align="right"><br />
==بداية == <br />
<br />
تختلف أنواع السكربتات فمنها خريطة أو وضع للعب <br />
<br />
MTA السكربتات جزء اساسي في تشغيل<br />
<br />
...وغيرها " freeroam , race , deathmatch " فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب <br />
<br />
(Lua) [www.lua.org] برمجة السكربتات تعتمد على لغة البرمجة<br />
<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
<br />
فهو يسهل برمجتها MTASE لكن يفضل استخدام برنامج :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
. أو مجلد عادي zip سترى الكثير من الملفات. ربما ترى مجلدات صيغتها , MTA .. وجميعها يقبله الـ<br />
<br />
وهو الذي سنستخدمه بالبرنامج التعليمي "myserver" ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته <br />
<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
=== meta.xml تعريف السكربت اضافة ملف===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
<br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
<br />
ولإنشاء ملف meta.xml :<br />
<br />
وافتحه باستخدام المفكرة =) meta.xml أفتح ملف نصي جديد وقم بتسميته<br />
<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=49197AR/مقدمه في البرمجه2016-09-19T15:58:31Z<p>Jaber: </p>
<hr />
<div><p align="right"><br />
==بداية == <br />
تختلف أنواع السكربتات فمنها خريطة أو وضع للعب <br />
<br />
MTA السكربتات جزء اساسي في تشغيل<br />
<br />
...وغيرها " freeroam , race , deathmatch " فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب <br />
<br />
(Lua) [www.lua.org] برمجة السكربتات تعتمد على لغة البرمجة<br />
<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
<br />
فهو يسهل برمجتها MTASE لكن يفضل استخدام برنامج :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
. أو مجلد عادي zip سترى الكثير من الملفات. ربما ترى مجلدات صيغتها , MTA .. وجميعها يقبله الـ<br />
<br />
وهو الذي سنستخدمه بالبرنامج التعليمي "myserver" ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته <br />
<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
=== meta.xml تعريف السكربت اضافة ملف===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
<br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
<br />
ولإنشاء ملف meta.xml :<br />
<br />
وافتحه باستخدام المفكرة =) meta.xml أفتح ملف نصي جديد وقم بتسميته<br />
<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=49196AR/مقدمه في البرمجه2016-09-19T15:57:05Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
تختلف أنواع السكربتات فمنها خريطة أو وضع للعب <br />
<br />
MTA السكربتات جزء اساسي في تشغيل<br />
<br />
...وغيرها " freeroam , race , deathmatch " فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب <br />
<br />
(Lua) [www.lua.org] برمجة السكربتات تعتمد على لغة البرمجة<br />
<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
<br />
فهو يسهل برمجتها MTASE لكن يفضل استخدام برنامج :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
. أو مجلد عادي zip سترى الكثير من الملفات. ربما ترى مجلدات صيغتها , MTA .. وجميعها يقبله الـ<br />
<br />
وهو الذي سنستخدمه بالبرنامج التعليمي "myserver" ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته <br />
<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
=== meta.xml تعريف السكربت اضافة ملف===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
<br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
<br />
ولإنشاء ملف meta.xml :<br />
<br />
وافتحه باستخدام المفكرة =) meta.xml أفتح ملف نصي جديد وقم بتسميته<br />
<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=CenterWindow&diff=48941CenterWindow2016-08-31T11:01:42Z<p>Jaber: </p>
<hr />
<div>{{Useful Function}}<br />
__NOTOC__<br />
This function center the window in any resolution.<br><br />
* '''NOTE:''' This is made to be used clientside!.<br />
<br />
==Syntax==<br />
<syntaxhighlight lang="lua">bool centerWindow ( element TheElement )</syntaxhighlight><br />
<br />
===Required Arguments===<br />
* '''theElement''': The element you want to center it.<br />
<br />
===Returns===<br />
Returns ''true'' if the window has been successfully centered, ''false'' otherwise.<br />
<br />
==Code==<br />
<section name="Clientside script" class="client" show="true"><br />
<syntaxhighlight lang="lua"><br />
function centerWindow (center_window)<br />
local screenW, screenH = guiGetScreenSize()<br />
local windowW, windowH = guiGetSize(center_window, false)<br />
local x, y = (screenW - windowW) /2,(screenH - windowH) /2<br />
return guiSetPosition(center_window, x, y, false)<br />
end<br />
</syntaxhighlight><br />
</section><br />
<br />
==Example==<br />
This example center the window.<br />
<syntaxhighlight lang="lua"><br />
addEventHandler( "onClientResourceStart", resourceRoot, function()<br />
myWindow = guiCreateWindow( 350, 100, 200, 250, "Window Title", false )<br />
end )<br />
<br />
addCommandHandler( "center", function()<br />
if myWindow then<br />
centerWindow( myWindow )<br />
end<br />
end )<br />
</syntaxhighlight><br />
<br />
<br />
Author: laserlaser<br />
<br />
==See Also==<br />
{{Useful_Functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/getElementsWithinColShape&diff=47648AR/getElementsWithinColShape2016-06-17T19:39:15Z<p>Jaber: Created page with "{{Server client function}} __NOTOC__ هذه الوظيفة تستخدم لجلب الألمنتات التي بداخل الكول شيب ==Syntax== <syntaxhighlight lang="lua"> table getE..."</p>
<hr />
<div>{{Server client function}}<br />
__NOTOC__<br />
هذه الوظيفة تستخدم لجلب الألمنتات التي بداخل الكول شيب<br />
<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
table getElementsWithinColShape ( colshape shape, [ string elemType = nil ] ) <br />
</syntaxhighlight> <br />
{{OOP| |[[colshape]]:getElementsWithin||}}<br />
===Required Arguments=== <br />
*'''shape:''' الكول شيب الذي تبي تجيب الالمنتات التي به .<br />
<br />
===Optional Arguments=== <br />
*'''elemType:''' نوع الألمنت :<br />
**'''"player":''' لاعب<br />
**'''"ped":''' بيد , شخصية وهمية<br />
**'''"vehicle":''' سيارة<br />
**'''"object":''' ابجكت<br />
**'''"pickup":''' <br />
**'''"marker":''' ماركر<br />
<!--**'''"spawnpoint":''' A spawnpoint<br />
**'''"remoteclient":''' A remote client connected to the server<br />
**'''"console":''' The server Console--><br />
<br />
===Returns===<br />
Returns a ''table'' containing all the elements inside the colshape, of the specified type. Returns an empty ''table'' if there are no elements inside. Returns ''false'' if the colshape is invalid.<br />
<br />
==Example== <br />
هذه الوظيفة تقوم بجلب الاعبين الذين بداخل الابجكت واخراج اسمائهم بالشات .<br />
<syntaxhighlight lang="lua"><br />
local newcolshape = createColSphere ( 1, 2, 3, 4 )<br />
local players = getElementsWithinColShape ( newcolshape, "player" ) -- جلب جميع الاعبين بداخل الكول شيب<br />
for theKey,thePlayer in ipairs(players) do -- لوب لجميع الاعبين داخل الكول شيب<br />
outputChatBox ( getPlayerName ( thePlayer ) .. " is in our new sphere" ) -- اخراج اسمائهم بالشات<br />
end<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{Element_functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/createColRectangle&diff=47647AR/createColRectangle2016-06-17T19:32:31Z<p>Jaber: </p>
<hr />
<div>__NOTOC__ <br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لصنع كول شيب مستطيل.<br />
<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
colshape createColRectangle ( float fX, float fY, float fWidth, float fHeight)<br />
</syntaxhighlight> <br />
{{OOP| |ColShape.Rectangle||}}<br />
===Required Arguments=== <br />
*'''fX:''' احداثيات X <br />
*'''fY:''' احداثيات Y<br />
*'''fWidth:''' العرض<br />
*'''fHeight:''' الارتفاع<br />
<br />
===Returns===<br />
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.<br />
<br />
==Example== <br />
<section name="Server" class="server" show="true"><br />
This example displays a chat message when a player enters the colshape and allows the colshape to be created using a console function ''set_zone''.<br />
<syntaxhighlight lang="lua"><br />
theZone = false<br />
<br />
function shapeHit ( thePlayer ) <br />
outputChatBox ( getPlayerName ( thePlayer ) .. " is in the zone!" ) -- display a message in everyone's chat box<br />
end<br />
<br />
function setZone ( playerSource, commandName, fX, fY )<br />
if ( fY and fX ) then -- check we've got the 2 args we need<br />
local tempCol = createColRectangle ( fX, fY, 10.0, 10.0 ) -- create a col<br />
if ( tempCol == false ) then -- did the col get created successfully?<br />
outputConsole ( "Syntax is: set_zone <X> <Y>" ) -- inform the user what the valid syntax is<br />
else<br />
if ( theZone ~= false ) then -- did we already have a zone?<br />
destroyElement ( theZone ) -- if so, destroy it<br />
else<br />
addEventHandler ( "onColShapeHit", theZone, shapeHit ) -- add a handler for the onColShapeHit event<br />
end<br />
theZone = tempCol -- and store the new zone we've made<br />
outputChatBox ( "Zone has moved!" ) -- and tell everyone<br />
end<br />
end<br />
end<br />
addCommandHandler ( "set_zone", setZone ) -- add a console function called set_zone that will trigger the function setZone<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Collision shape functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/createColRectangle&diff=47646AR/createColRectangle2016-06-17T19:31:31Z<p>Jaber: Created page with "__NOTOC__ {{Server client function}} هذه الوظيفة تستخدم لصنع كول شيب مستطيل. ==Syntax== <syntaxhighlight lang="lua"> colshape createColRectangle ( float fX..."</p>
<hr />
<div>__NOTOC__ <br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لصنع كول شيب مستطيل.<br />
<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
colshape createColRectangle ( float fX, float fY, float fWidth, float fHeight)<br />
</syntaxhighlight> <br />
{{OOP| |ColShape.Rectangle||}}<br />
===Required Arguments=== <br />
*'''fX:''' The X position of the collision rectangle's west side<br />
*'''fY:''' The Y position of the collision rectangle's south side<br />
*'''fWidth:''' The collision rectangle's width<br />
*'''fHeight:''' The collision rectangle's height<br />
<br />
===Returns===<br />
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.<br />
<br />
==Example== <br />
<section name="Server" class="server" show="true"><br />
This example displays a chat message when a player enters the colshape and allows the colshape to be created using a console function ''set_zone''.<br />
<syntaxhighlight lang="lua"><br />
theZone = false<br />
<br />
function shapeHit ( thePlayer ) <br />
outputChatBox ( getPlayerName ( thePlayer ) .. " is in the zone!" ) -- display a message in everyone's chat box<br />
end<br />
<br />
function setZone ( playerSource, commandName, fX, fY )<br />
if ( fY and fX ) then -- check we've got the 2 args we need<br />
local tempCol = createColRectangle ( fX, fY, 10.0, 10.0 ) -- create a col<br />
if ( tempCol == false ) then -- did the col get created successfully?<br />
outputConsole ( "Syntax is: set_zone <X> <Y>" ) -- inform the user what the valid syntax is<br />
else<br />
if ( theZone ~= false ) then -- did we already have a zone?<br />
destroyElement ( theZone ) -- if so, destroy it<br />
else<br />
addEventHandler ( "onColShapeHit", theZone, shapeHit ) -- add a handler for the onColShapeHit event<br />
end<br />
theZone = tempCol -- and store the new zone we've made<br />
outputChatBox ( "Zone has moved!" ) -- and tell everyone<br />
end<br />
end<br />
end<br />
addCommandHandler ( "set_zone", setZone ) -- add a console function called set_zone that will trigger the function setZone<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Collision shape functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/createColCuboid&diff=47645AR/createColCuboid2016-06-17T19:29:50Z<p>Jaber: </p>
<hr />
<div>__NOTOC__ <br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لصنع كول شيب متوازي مستطيلات.<br />
<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
colshape createColCuboid ( float fX, float fY, float fZ, float fWidth, float fDepth, float fHeight )<br />
</syntaxhighlight> <br />
{{OOP| |ColShape.Cuboid||}}<br />
===Required Arguments=== <br />
*'''fX:''' احداثيات x<br />
*'''fY:''' احداثيات y<br />
*'''fZ:''' احداثيات z<br />
*'''fWidth:''' العرض<br />
*'''fDepth:''' العمق<br />
*'''fHeight:''' الارتفاع<br />
<br />
===Returns===<br />
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.<br />
<br />
==Example== <br />
<section name="Server" class="server" show="true"><br />
This example displays a chat message when a player enters the colshape and allows the colshape to be created using a console function ''set_zone''.<br />
<syntaxhighlight lang="lua"><br />
theZone = false<br />
<br />
function shapeHit ( thePlayer ) <br />
outputChatBox ( getPlayerName ( thePlayer ) .. " is in the zone!" ) -- display a message in everyone's chat box<br />
end<br />
<br />
function setZone ( playerSource, commandName, fX, fY, fZ )<br />
if ( fZ and fY and fX ) then -- check we've got all 3 args we need<br />
local tempCol = createColCuboid ( fX, fY, fZ, 10.0, 10.0, 10.0 ) -- create a col<br />
if ( tempCol == false ) then -- did the col get created successfully?<br />
outputConsole ( "Syntax is: set_zone <X> <Y> <Z>" ) -- inform the user what the valid syntax is<br />
else<br />
if ( theZone ~= false ) then -- did we already have a zone?<br />
destroyElement ( theZone ) -- if so, destroy it<br />
else<br />
addEventHandler ( "onColShapeHit", theZone, shapeHit ) -- add a handler for the onColShapeHit event<br />
end<br />
theZone = tempCol -- store the new zone we've made<br />
outputChatBox ( "Zone has moved!" ) -- and tell everyone<br />
end<br />
end<br />
end<br />
addCommandHandler ( "set_zone", setZone ) -- add a console function called set_zone that will trigger the function setZone<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Collision shape functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/createColCuboid&diff=47644AR/createColCuboid2016-06-17T19:29:18Z<p>Jaber: Created page with "__NOTOC__ {{Server client function}} هذه الوظيفة تستخدم لصنع كول شيب متوازي مستطيلات. {{VisualizeColshape}} {{Note|Attaching a cuboid ..."</p>
<hr />
<div>__NOTOC__ <br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لصنع كول شيب متوازي مستطيلات.<br />
{{VisualizeColshape}}<br />
{{Note|Attaching a cuboid colshape to another element may give unexpected results as the origin is not at the cuboid centre. Try using a [[createColSphere|collision sphere]] for attaching instead}}<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
colshape createColCuboid ( float fX, float fY, float fZ, float fWidth, float fDepth, float fHeight )<br />
</syntaxhighlight> <br />
{{OOP| |ColShape.Cuboid||}}<br />
===Required Arguments=== <br />
*'''fX:''' احداثيات x<br />
*'''fY:''' احداثيات y<br />
*'''fZ:''' احداثيات z<br />
*'''fWidth:''' العرض<br />
*'''fDepth:''' العمق<br />
*'''fHeight:''' الارتفاع<br />
<br />
===Returns===<br />
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.<br />
<br />
==Example== <br />
<section name="Server" class="server" show="true"><br />
This example displays a chat message when a player enters the colshape and allows the colshape to be created using a console function ''set_zone''.<br />
<syntaxhighlight lang="lua"><br />
theZone = false<br />
<br />
function shapeHit ( thePlayer ) <br />
outputChatBox ( getPlayerName ( thePlayer ) .. " is in the zone!" ) -- display a message in everyone's chat box<br />
end<br />
<br />
function setZone ( playerSource, commandName, fX, fY, fZ )<br />
if ( fZ and fY and fX ) then -- check we've got all 3 args we need<br />
local tempCol = createColCuboid ( fX, fY, fZ, 10.0, 10.0, 10.0 ) -- create a col<br />
if ( tempCol == false ) then -- did the col get created successfully?<br />
outputConsole ( "Syntax is: set_zone <X> <Y> <Z>" ) -- inform the user what the valid syntax is<br />
else<br />
if ( theZone ~= false ) then -- did we already have a zone?<br />
destroyElement ( theZone ) -- if so, destroy it<br />
else<br />
addEventHandler ( "onColShapeHit", theZone, shapeHit ) -- add a handler for the onColShapeHit event<br />
end<br />
theZone = tempCol -- store the new zone we've made<br />
outputChatBox ( "Zone has moved!" ) -- and tell everyone<br />
end<br />
end<br />
end<br />
addCommandHandler ( "set_zone", setZone ) -- add a console function called set_zone that will trigger the function setZone<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Collision shape functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/createColCircle&diff=47643AR/createColCircle2016-06-17T19:26:29Z<p>Jaber: Created page with "__NOTOC__ {{Server client function}} هذه الوظيفة تستخدم لصنع كول شيب دائري الشكل. {{VisualizeColshape}} ==Syntax== <syntaxhighlight lang="lua"> colshape..."</p>
<hr />
<div>__NOTOC__ <br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لصنع كول شيب دائري الشكل.<br />
{{VisualizeColshape}}<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
colshape createColCircle ( float fX, float fY, float radius ) <br />
</syntaxhighlight> <br />
<br />
===Required Arguments=== <br />
*'''fX:''' الاحداثيات x<br />
*'''fY:''' الاحداثيات y<br />
*'''radius''' نصف قطر الدائرة<br />
<br />
===Returns===<br />
Returns a [[colshape]] element if successful, ''false'' if invalid arguments were passed to the function.<br />
<br />
==Example== <br />
<section name="Server" class="server" show="true"><br />
This example displays a chat message when a player enters the colshape and allows the colshape to be created using a console function ''set_zone''.<br />
<syntaxhighlight lang="lua"><br />
theZone = false<br />
<br />
function shapeHit ( thePlayer ) <br />
outputChatBox ( getPlayerName ( thePlayer ) .. " is in the zone!" ) -- display a message in everyone's chat box<br />
end<br />
<br />
function setZone ( playerSource, commandName, fX, fY )<br />
if ( fY and fX ) then -- check we've got all 3 args we need<br />
local tempCol = createColCircle ( fX, fY, 10.0 ) -- create a col<br />
if ( tempCol == false ) then -- did the col get created successfully?<br />
outputConsole ( "Syntax is: set_zone <X> <Y>" ) -- inform the user what the valid syntax is<br />
else<br />
if ( theZone ~= false ) then -- did we already have a zone?<br />
destroyElement ( theZone ) -- if so, destroy it<br />
else<br />
addEventHandler ( "onColShapeHit", theZone, shapeHit ) -- add a handler for the onColShapeHit event<br />
end<br />
theZone = tempCol -- and store the new zone we've made<br />
outputChatBox ( "Zone has moved!" ) -- and tell everyone<br />
end<br />
end<br />
end<br />
addCommandHandler ( "set_zone", setZone ) -- add a console function called set_zone that will trigger the function setZone<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Collision shape functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/isChatVisible&diff=47642AR/isChatVisible2016-06-17T19:19:25Z<p>Jaber: </p>
<hr />
<div>{{Client function}}<br />
__NOTOC__<br />
{{New items|4.0132|1.4|<br />
هذه الوظيفة تستخدم للتحقق ان الشات ظاهر.<br />
<br />
ملاحظة : تعمل في اصدار 1.4 فقط<br />
}}<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
bool isChatVisible ( )<br />
</syntaxhighlight> <br />
<br />
===Returns===<br />
Returns ''true'' if the chat is visible, ''false'' otherwise.<br />
<br />
==Example==<br />
<br />
<syntaxhighlight lang="lua"><br />
addCommandHandler("sc",<br />
function ()<br />
showChat(not isChatVisible())<br />
end)<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{Client_output_functions}}<br />
[[ru:isChatVisible]]<br />
[[en:isChatVisible]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/isChatVisible&diff=47641AR/isChatVisible2016-06-17T19:17:27Z<p>Jaber: Created page with "{{Client function}} __NOTOC__ {{New items|4.0132|1.4| هذه الوظيفة تستخدم للتحقق ان الشات ظاهر. }} ==Syntax== <syntaxhighlight lang="lua"> bool isChatVisible..."</p>
<hr />
<div>{{Client function}}<br />
__NOTOC__<br />
{{New items|4.0132|1.4|<br />
هذه الوظيفة تستخدم للتحقق ان الشات ظاهر.<br />
}}<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
bool isChatVisible ( )<br />
</syntaxhighlight> <br />
<br />
===Returns===<br />
Returns ''true'' if the chat is visible, ''false'' otherwise.<br />
<br />
==Example==<br />
<br />
<syntaxhighlight lang="lua"><br />
addCommandHandler("sc",<br />
function ()<br />
showChat(not isChatVisible())<br />
end)<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{Client_output_functions}}<br />
[[ru:isChatVisible]]<br />
[[en:isChatVisible]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47529AR/مقدمه في البرمجه2016-05-15T15:19:57Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
تختلف أنواع السكربتات فمنها خريطة أو وضع للعب <br />
<br />
<br />
السكربتات جزء أساسي في تشغيل MTA <br />
<br />
<br />
فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ،" freeroam , race , deathmatch " وغيرها ..<br />
<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
. أو مجلد عادي zip سترى الكثير من الملفات. ربما ترى مجلدات صيغتها , MTA .. وجميعها يقبله الـ<br />
<br />
وهو الذي سنستخدمه بالبرنامج التعليمي "myserver" ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته <br />
<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
=== meta.xml تعريف السكربت اضافة ملف===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
<br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
<br />
ولإنشاء ملف meta.xml :<br />
<br />
وافتحه باستخدام المفكرة =) meta.xml أفتح ملف نصي جديد وقم بتسميته<br />
<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47528AR/مقدمه في البرمجه2016-05-15T15:19:19Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
تختلف أنواع السكربتات فمنها خريطة أو وضع للعب <br />
<br />
السكربتات جزء أساسي في تشغيل MTA <br />
<br />
فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ،<br />
" freeroam , race , deathmatch " وغيرها ..<br />
<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
. أو مجلد عادي zip سترى الكثير من الملفات. ربما ترى مجلدات صيغتها , MTA .. وجميعها يقبله الـ<br />
<br />
وهو الذي سنستخدمه بالبرنامج التعليمي "myserver" ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته <br />
<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
=== meta.xml تعريف السكربت اضافة ملف===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
<br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
<br />
ولإنشاء ملف meta.xml :<br />
<br />
وافتحه باستخدام المفكرة =) meta.xml أفتح ملف نصي جديد وقم بتسميته<br />
<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47527AR/مقدمه في البرمجه2016-05-15T15:18:14Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
السكربتات جزء أساسي في تشغيل MTA فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ، تختلف أنواع السكربتات فمنها خريطة أو وضع للعب " freeroam , race , deathmatch " وغيرها ..<br />
<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
. أو مجلد عادي zip سترى الكثير من الملفات. ربما ترى مجلدات صيغتها , MTA .. وجميعها يقبله الـ<br />
<br />
وهو الذي سنستخدمه بالبرنامج التعليمي "myserver" ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته <br />
<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
=== meta.xml تعريف السكربت اضافة ملف===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
<br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
<br />
ولإنشاء ملف meta.xml :<br />
<br />
وافتحه باستخدام المفكرة =) meta.xml أفتح ملف نصي جديد وقم بتسميته<br />
<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47526AR/مقدمه في البرمجه2016-05-15T15:15:48Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
السكربتات جزء أساسي في تشغيل MTA فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ، تختلف أنواع السكربتات فمنها خريطة أو وضع للعب " freeroam , race , deathmatch " وغيرها ..<br />
<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
. أو مجلد عادي zip سترى الكثير من الملفات. ربما ترى مجلدات صيغتها , MTA .. وجميعها يقبله الـ<br />
<br />
وهو الذي سنستخدمه بالبرنامج التعليمي "myserver" ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته <br />
<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
===تعريف السكربت (إضافة ملف meta.xml)===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
ولإنشاء ملف meta.xml : أفتح ملف نصي جديد وقم بتسميته meta.xml وافتحه باستخدام المفكرة =)<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47525AR/مقدمه في البرمجه2016-05-15T15:12:08Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
السكربتات جزء أساسي في تشغيل MTA فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ، تختلف أنواع السكربتات فمنها خريطة أو وضع للعب " freeroam , race , deathmatch " وغيرها ..<br />
<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
سترى الكثير من الملفات. ربما ترى مجلدات صيغتها .zip أو مجلد عادي , وجميعها يقبله الـ MTA ..<br />
ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته "myserver" وهو الذي سنستخدمه بالبرنامج التعليمي<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
===تعريف السكربت (إضافة ملف meta.xml)===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
ولإنشاء ملف meta.xml : أفتح ملف نصي جديد وقم بتسميته meta.xml وافتحه باستخدام المفكرة =)<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47524AR/مقدمه في البرمجه2016-05-15T15:10:37Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
السكربتات جزء أساسي في تشغيل MTA فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ، تختلف أنواع السكربتات فمنها خريطة أو وضع للعب " freeroam , race , deathmatch " وغيرها ..<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
<br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
سترى الكثير من الملفات. ربما ترى مجلدات صيغتها .zip أو مجلد عادي , وجميعها يقبله الـ MTA ..<br />
ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته "myserver" وهو الذي سنستخدمه بالبرنامج التعليمي<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
===تعريف السكربت (إضافة ملف meta.xml)===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
ولإنشاء ملف meta.xml : أفتح ملف نصي جديد وقم بتسميته meta.xml وافتحه باستخدام المفكرة =)<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47523AR/مقدمه في البرمجه2016-05-15T15:10:10Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
السكربتات جزء أساسي في تشغيل MTA فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ، تختلف أنواع السكربتات فمنها خريطة أو وضع للعب " freeroam , race , deathmatch " وغيرها ..<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
سترى الكثير من الملفات. ربما ترى مجلدات صيغتها .zip أو مجلد عادي , وجميعها يقبله الـ MTA ..<br />
ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته "myserver" وهو الذي سنستخدمه بالبرنامج التعليمي<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
===تعريف السكربت (إضافة ملف meta.xml)===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
ولإنشاء ملف meta.xml : أفتح ملف نصي جديد وقم بتسميته meta.xml وافتحه باستخدام المفكرة =)<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47522AR/مقدمه في البرمجه2016-05-15T15:09:44Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
السكربتات جزء أساسي في تشغيل MTA فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ، تختلف أنواع السكربتات فمنها خريطة أو وضع للعب " freeroam , race , deathmatch " وغيرها ..<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
اولا لا بد من معرفة انواع ملفات السكربت <br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
سترى الكثير من الملفات. ربما ترى مجلدات صيغتها .zip أو مجلد عادي , وجميعها يقبله الـ MTA ..<br />
ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته "myserver" وهو الذي سنستخدمه بالبرنامج التعليمي<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
===تعريف السكربت (إضافة ملف meta.xml)===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
ولإنشاء ملف meta.xml : أفتح ملف نصي جديد وقم بتسميته meta.xml وافتحه باستخدام المفكرة =)<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/%D9%85%D9%82%D8%AF%D9%85%D9%87_%D9%81%D9%8A_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%87&diff=47521AR/مقدمه في البرمجه2016-05-15T15:08:52Z<p>Jaber: </p>
<hr />
<div><p align="right"> <br />
السكربتات جزء أساسي في تشغيل MTA فتستطيع بإستخدامهم إنشاء تطبيقات لتحسين اللعب ، تختلف أنواع السكربتات فمنها خريطة أو وضع للعب " freeroam , race , deathmatch " وغيرها ..<br />
<br />
برمجة السكربتات تعتمد على لغة البرمجة (Lua) [www.lua.org] .<br />
لغة البرمجة تعتمد إعتماداً كلياً على اللغة الإنجليزية , فيجب أن تكون لديك خلفية في اللغة الإنجليزية قبل المتابعة.<br />
لبرمجة سكربت ما تحتاج لمحرر .. ويفضل إستخدام محرر إحترافي لكي يسهل عليك البرمجة مثل :<br />
*Notepad++ [http://notepad-plus-plus.org/download]<br />
*Lua Edit [http://luaedit.sourceforge.net/ LuaEdit]<br />
لكن يفضل إستخدام برنامج MTASE فهو يسهل عملية إنشاء السكربتات وبرمجتها :<br />
* [[MTASE|MTA Script Editor]].'''<br />
<br />
<br />
==إنشاء سكربت ==<br />
سوف نتعلم كيف نقوم بإنشاء سكربت يدخل اللاعب إلى اللعبة .. خطوة بحطوة<br />
اولا للابد من معرفة انواع ملفات السكربت<br />
1-Meta.xml -- يقوم هذا الملف بتعرف الملفات الموجود في السكربت للسيرفر <br />
2-Client -- يقوم هذا الملف بتشغيل جميع أوامر المتعلقة بالاعب فقط <br />
<br />
3-Server -- يقوم هذا الملف بتشغيل جميع الاوامر سواء كانت للسيرفر او الاعب<br />
<br />
===أين مسار كل البرامج النصية (السكريبتات أو المودات)؟===<br />
الان نتعرف على مجلد المودات أو السكربتات.<br />
اذهب إلى مجلد Multi Theft Auto واتبع المسار التالي:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/<br />
<br />
سترى الكثير من الملفات. ربما ترى مجلدات صيغتها .zip أو مجلد عادي , وجميعها يقبله الـ MTA ..<br />
ولإنشاء المودات الخاصة بك: قم بعمل مجلد جديد واجعل اسمه كما تريد فمثلاً قم بتسميته "myserver" وهو الذي سنستخدمه بالبرنامج التعليمي<br />
والان يجب أن يكون مسار المجلد الذي قمت بعمله هذا:<br />
<br />
/Your MTA Server/mods/deathmatch/resources/myserver/<br />
<br />
* myserver: اسم المجلد الذي قمت بتسميته<br />
<br />
===تعريف السكربت (إضافة ملف meta.xml)===<br />
حتى يستطيع السيرفر من معرفة المودات, يجب علينا إنشاء ملف meta.xml <br />
" ويكون بداخل مجلد السكربت الذي قمنا بإنشائه وهو "myserver" <br />
ولإنشاء ملف meta.xml : أفتح ملف نصي جديد وقم بتسميته meta.xml وافتحه باستخدام المفكرة =)<br />
ولا تنسى ان يكون بداخل مجلد السكربت .<br />
<br />
<br />
أدخل الكود التالي في ملف ''meta.xml'':<br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="إسمك" type="gamemode" name="إسم السكربت" description="وصف بسيط للسكربت" /><br />
<script src="script.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
هنا يتم تعريف أجزاء السكربت فمثلاً :<br />
* <info ..><br />
تضع فيه بيانات السكربت .. مثل الإسم والنوع والوصف<br />
* type="gamemode"<br />
تعني أن نوع السكربت هو مود لعب وتوجد أنواع عديدة مثل :<br />
**gamemode<br />
**map<br />
**script<br />
<br />
===إنشاء ملف السكربت Lua===<br />
قمنا بوضع هذا السطر في :<br />
*meta.xml<br />
:<br />
<script src="script.lua" /><br />
<br />
الآن نقوم بإنشاء ملف نصي بنفس الإسم<br />
**script.lua<br />
بإستخدام برنامج التحرير لديك .. نقوم بإنشاء الكود<br />
<br />
<syntaxhighlight lang="lua"><br />
function joinHandler() -- الوظيفة .. وبعدها نقوم بكتابة الإسم<br />
local x = 1959.55 -- تعريف x<br />
local y = -1714.46 -- تعريف y<br />
local z = 10 -- تعريف z<br />
spawnPlayer(source, x, y, z) -- نقوم بإستخدام هذه الوظيفة لإنتاج اللاعب ونقوم بتحديد اللاعب وهو المصدر : source<br />
fadeCamera(source, true) -- نقوم بعمل fade للكاميرا<br />
setCameraTarget(source, source) -- نجعل هدف الكاميرا هو اللاعب <br />
outputChatBox("مرحباً بك في السيرفر", source) -- نقوم بإخراج نص في الدردشة<br />
end<br />
addEventHandler("onPlayerJoin", getRootElement(), joinHandler) -- نقوم بإضافة المعالج حيث سيتم تشغيله بعد الحدث المحدد وهو عند دخول اللا<br />
</syntaxhighlight><br />
وصف وشرح الكود اعلاه : <br />
سيقوم السكربت بوضع اللاعب في الاحداثيات (x,y,z) المحدده اعلاه, عند دخوله الى السيرفر<br />
لاحظ انه يجب استخدام وظيفة [ ''fadeCamera'' ] ستكون الشاشة سوداء وأيضاً يجب تعيين الكاميرا ( setTargetCamera ) ..<br />
<br />
نرى أن '''source''' هو المصدر وهو اللاعب الذي يقوم بالدخول <br />
<br />
*[[addEventHandler]] - الاحداث وهي ما يجب فعله من قبل المستخدم او السيرفر<br />
*[[function]] - وظيفة تعمل عند حدث من الاحداث وتحتوي على امر او أوامر<br />
أيضاً لو رأينا في المعالج <br />
*[[addEventHandler]] - إضافة معالج للحدث<br />
نرى 3 أشياء<br />
*: onPlayerJoin - عند دخول اللاعب<br />
وهو الحدث .. حيث يحدد متى يتم تشغيل المعالج - في هذه الحالة عند دخول اللاعب<br />
*getRootElement() - جلب العنصر الحالي<br />
هذا يقوم بتعيين العنصر الذي يقوم بتشغيل الحدث <br />
*joinHandler <br />
وهو إسم الوظيفة التي قمنا بصناعتها <br />
<br />
يمكنك التوسع أكثر في : [[addEventHandler]]<br />
<br />
===تشغيل السكربت===<br />
بعد أن تقوم بحفظ أجزاء السكربت في ملف واحد ويمكن حفظه في الملفات التالية :<br />
* مجلد<br />
* أرشيف .zip<br />
ونقوم بنسخه إلى مجلد السكربتات داخل سيرفرك ونقوم بتشغيله بالطريقة العادية.<br />
<br />
الآن إنتهينا من صنع السكربت .. بعد هذا سنقوم بصنع سكربت مع أمر <br />
* command<br />
يمكنك المتابعة أو الذهاب إلى دورة صناعة النوافذ<br />
*[[Introduction to Scripting GUI]]<br />
<br />
===إنشاء سكربت بطريقة مفصلة===<br />
<br />
==صناعة أمر بسيط==<br />
لنعد الآن إلى ملف<br />
*script.lua<br />
ونقوم بتعديله قليلاً لإنشاء أمر بسيط يقوم بإنشاء سيارة بجانب اللاعب<br />
<br />
<syntaxhighlight lang="lua"><br />
-- في البداية نقوم بكتب وظيفة إنشاء السيارة<br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- هنا نقوم بكتابة وظيفة إنشاء السيارة كـ<br />
-- createVehicle<br />
end<br />
<br />
-- نقوم بإضافة الأمر<br />
addCommandHandler("createvehicle", createVehicleForPlayer) <br />
</syntaxhighlight><br />
''ملاحظة: يمكنك الضغط على الوظائف والتعمق فيها بداخل الويكي.<br />
<br />
<br />
== الوظيفة ==<br />
الوظيفة هي شيء يسمى<br />
<br />
function<br />
<br />
الوظيفة هي الشيء التي يتكون عليها الحدث<br />
<br />
يمكنك ان تسمي الوظيفة كما شئت ويمكنك أيضاً عدم وضع اسم للوظيفة<br />
<br />
<br />
'''مثال لـ وظيفة لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
function arabs( ) -- الوظيفة<br />
outputChatBox("مرحباً بك") --s ستلاحظ بـ أن كلمة " مرحباً بك " ظهرت في الشات عند دخول الاعب <br />
end<br />
addEventHandler("onPlayerJoin", root, arabs) -- .الحدث مع اسم الوظيفة<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
<br />
'''مثال لـ وظيفة ليس لها إسم'''<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onPlayerWasted", root,<br />
function(_,killer)<br />
outputChatBox( killer .. " من قبل" .. getPlayerName(source) .. " لقد قُتل الاعب" )<br />
end)<br />
</syntaxhighlight><br />
<br />
كما تلاحظ ووضع قوس قريباً من<br />
<br />
end)<br />
<br />
هذا القوس يكمل القوس الآخر كما نلاحظ في الحدث <br />
<br />
addEventHandler(<br />
<br />
<br />
----<br />
<br />
<br />
== الحدث ==<br />
الحدث هو شيء يسمى<br />
<br />
event<br />
<br />
الحدث هو الذي يتكون على بناء الوظيفة<br />
فـ اذا رجعنا الى الامثلة التي في الاعلى سوف نرى عدة احداث ومنها<br />
<br />
[[onPlayerWasted]]<br />
<br />
الحدث ببساطة يحدد متى سوف تحدث او كيف سوف تحدث الوظائف التي ادخلتها<br />
<br />
onPlayerWasted<br />
<br />
عند موت الاعب<br />
<br />
'''مثال للحدث'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source) -- s يآتي بمكان الاعب x, y, z<br />
local theVehicle = createVehicle(445, x, y, z) -- s السيارة التي سـ تصنع بمكان الاعب الذي تم تحديده مسبقاً<br />
warpPedIntoVehicle(source, theVehicle) -- s يجعل الاعب داخل السيارة<br />
end<br />
addEventHandler("onPlayerJoin", root, onJoin) -- s الحدث<br />
-- root = getRootElement()<br />
</syntaxhighlight><br />
هذه الوظيفة مع هذا الحدث سوف يعطون الاعب سيارة عند دخوله السيرفر<br />
<br />
ملاحظة الحدث ليس دائم على الوظيفة فـ أيصاً يمكنك تكوين هذه الوظيفة على حدث آخر<br />
<br />
'''مثال'''<br />
<syntaxhighlight lang="lua"><br />
function onJoin()<br />
x, y, z = getElementPosition(source)<br />
local theVehicle = createVehicle(445, x, y, z)<br />
warpPedIntoVehicle(source, theVehicle)<br />
end<br />
addEventHandler("onPlayerLogin", root, onJoin)<br />
</syntaxhighlight><br />
هذا سوف يعطي الاعب سيارة لاكن ليس عند دخوله السيرفر , إنما عند دخوله حسابه<br />
<br />
'''Edit'''<br />
<br />
مثال آخر<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onVehicleExplode",root, -- نضيف حدث عند إنفجار اي سيارة<br />
function() -- الوظيفة<br />
setTimer(destroyElement,5000,1,source) -- يخفي السيارة بعد 5 ثواني من انفاجرها <br />
end<br />
)<br />
</syntaxhighlight><br />
يمكنك ان تجد<br />
الاحداث<br />
والوظائف <br />
كلنت وسيرفر<br />
هنا<br />
<br />
كلنت:<br />
<br />
'''وظائف كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Functions<br />
<br />
<br />
'''احداث كلنت'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Client_Scripting_Events<br />
<br />
سيرفر:<br />
<br />
'''وظائف سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Functions<br />
<br />
<br />
'''احداث سيرفر'''<br />
<br />
http://wiki.multitheftauto.com/wiki/Server_Scripting_Events<br />
<br />
<br />
----<br />
<br />
== String الـ ==<br />
السترنج هو شيء يوجد في بعض الوظايف التي توجد داخل الام تي اي<br />
<br />
مثلاً<br />
<syntaxhighlight lang="lua"><br />
addEventHandler("onResourceStart",resourceRoot, -- الايفنت هنا يجب ان تكون بين سترنق كما الموضح هنا<br />
function()<br />
outputChatBox("تم بدء السكربت") -- s هنا سوف يظهر رسالة بالشات " تم بدء السكربت " عند بدء السكربت ويجب ان تكون سترنق<br />
end<br />
) -- نهاية قوس الحدث<br />
</syntaxhighlight><br />
السترنق له عدة أشكال , فيمكن ان يكون كالآتي<br />
<br />
""<br />
<br />
أو<br />
<br />
' '<br />
<br />
أو<br />
<br />
[[]]<br />
<br />
فمثلاً اذا نريد ان نخرج رسالة بعلبة الشات<br />
<br />
يمكن ان تكون كذلك <br />
<syntaxhighlight lang="lua"><br />
outputChatBox([[مرحباً]])<br />
<br />
-- أو كذلك<br />
outputChatBox('مرحباً')<br />
<br />
-- أو كذلك<br />
<br />
outputChatBox("مرحباً")<br />
</syntaxhighlight><br />
<br />
====Command handlerعن الـ====<br />
.(`) أو زر F8 التي يمكن للاعب ان يعرضها باستخدام زر Consoleهو اسم الامر الذي يمكن للاعب ان يدخله في الـ [[addCommandHandler]] في argument أول<br />
<br />
."createVehicleForPlayer"هي وظيفة تُنفذ عند كتابة اللاعب الامر في هذه الحالة لـ [[addCommandHandler]] في argument ثاني<br />
<br />
<br />
:اذا كنت متمرس في البرمجة, ستعرف انك ستحتاج ان تنفذ وظيفة مثل<br />
<br />
<syntaxhighlight lang="lua"><br />
functionName(argument1, argument2, argument3, ..)<br />
</syntaxhighlight><br />
<syntaxhighlight lang="lua"><br />
functionName(thePlayer, commandName, argument3, ..)<br />
</syntaxhighlight><br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="lua"><br />
createVehicleForPlayer(thePlayer,"createvehicle","468") -- thePlayer هو الشيء الي كتب الكومند<br />
</syntaxhighlight><br />
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).<br />
<br />
''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.''<br />
<br />
====Writing the function====<br />
In order to fill the function we created, we need to think about what we have to do:<br />
* Get the players position, so we know where to spawn the vehicle (we want it to appear right beside the player)<br />
* Calculate the position we want to spawn the vehicle at (we don't want it to appear in the player)<br />
* Spawn the vehicle<br />
* Check if it has been spawned successfully, or output a message<br />
<br />
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.<br />
<br />
For [[getElementPosition]], the syntax is:<br />
<syntaxhighlight lang="lua"><br />
float, float, float getElementPosition ( element theElement )<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
-- نأتي باحداثيات المكان الي نبغي نضع فيه السيارة بشكل x, y, z<br />
-- (local تعني ان هاد الاختصار ما رح يشغل غير في هاد الفنكشن)<br />
local x,y,z = getElementPosition(thePlayer)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
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.<br />
<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- add 5 units to the x position<br />
-- create the vehicle and store the returned vehicle element in the ''createdVehicle'' variable<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
end<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
Now we have our complete script:<br />
<syntaxhighlight lang="lua"><br />
function createVehicleForPlayer(thePlayer, command, vehicleModel)<br />
local x,y,z = getElementPosition(thePlayer) -- نأتي بمكان الاعب<br />
x = x + 5 -- نضيف 5 وحد ل الاحداثيات X<br />
local createdVehicle = createVehicle(tonumber(vehicleModel),x,y,z)<br />
-- نشوف لو السيارة اتعملت ام لا<br />
if (createdVehicle == false) then<br />
-- لو السياره اتعملت يبقي نعمل رسالة,لكن للاعب فقط<br />
outputChatBox("Failed to create vehicle.",thePlayer)<br />
end<br />
end<br />
addCommandHandler("createvehicle", createVehicleForPlayer)<br />
</syntaxhighlight><br />
<br />
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]].<br />
<br />
==What you need to know==<br />
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.<br />
===Clientside and Serverside scripts===<br />
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.<br />
<br />
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:<br />
<syntaxhighlight lang="xml"><br />
<script src="client.lua" type="client" /><br />
</syntaxhighlight><br />
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]].<br />
<br />
===More complex resources===<br />
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:<br />
<br />
====First example - A utility script====<br />
<syntaxhighlight lang="xml"><br />
/admin_commands<br />
/meta.xml<br />
/commands.lua<br />
/client.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="admin commands" /><br />
<script src="commands.lua" /><br />
<script src="client.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''commands.lua'' provides some admin commands, like banning a player, muting or something else that can be used to admin the server<br />
* The ''client.lua'' provides a GUI to be able to perform the mentioned actions easily<br />
<br />
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.<br />
<br />
====Second example - A gamemode====<br />
<syntaxhighlight lang="xml"><br />
/counterstrike<br />
/meta.xml<br />
/counterstrike.lua<br />
/buymenu.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike remake" type="gamemode" /><br />
<script src="counterstrike.lua" /><br />
<script src="buymenu.lua" type="client" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''counterstrike.lua'' contains similiar to the following features:<br />
** Let players choose their team and spawn them<br />
** Provide them with weapons, targets and instructions (maybe read from a Map, see below)<br />
** Define the game's rules, e.g. when does the round end, what happens when a player dies<br />
** .. and maybe some more<br />
* The ''buymenu.lua'' is a clientside script and creates a menu to buy weapons<br />
<br />
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.<br />
<br />
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.<br />
<br />
====Third example - A Map====<br />
<syntaxhighlight lang="xml"><br />
/cs-airport<br />
/meta.xml<br />
/airport.map<br />
/airport.lua<br />
</syntaxhighlight><br />
<syntaxhighlight lang="xml"><br />
<meta><br />
<info author="Someguy" description="Counterstrike airport map" type="map" gamemodes="counterstrike" /><br />
<map src="airport.map" /><br />
<script src="airport.lua" /><br />
</meta><br />
</syntaxhighlight><br />
<br />
* The ''airport.map'' in a XML file that provides information about the map to the gamemode, these may include:<br />
** Where the players should spawn, with what weapons, what teams there are<br />
** What the targets are<br />
** Weather, World Time, Timelimit<br />
** Provide vehicles<br />
* The ''airport.lua'' might contain map-specific features, that may include:<br />
** Opening some door/make something explode when something specific happens<br />
** Create or move some custom objects, or manipulate objects that are created through the .map file<br />
** .. anything else map-specific you can think of<br />
<br />
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.<br />
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.<br />
<br />
The ''airport.map'' file might look similiar to this:<br />
<syntaxhighlight lang="xml"><br />
<map mode="deathmatch" version="1.0"><br />
<terrorists><br />
<spawnpoint posX="2332.23" posY="-12232.33" posZ="4.42223" skins="23-40" /><br />
</terrorists><br />
<counterterrorists><br />
<spawnpoint posX="2334.23443" posY="-12300.233" posZ="10.2344" skins="40-50" /><br />
</counterterrorists><br />
<br />
<bomb posX="23342.23" posY="" posZ="" /><br />
<br />
<vehicle posX="" posY="" posZ="" model="602" /> <br />
<vehicle posX="" posY="" posZ="" model="603" /> <br />
</map><br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
===Events===<br />
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]].<br />
<br />
This example will output a message with the name of the player who died:<br />
<syntaxhighlight lang="lua"><br />
function playerDied(totalAmmo, killer, killerWeapon, bodypart)<br />
outputChatBox(getPlayerName(source).." died!")<br />
end<br />
addEventHandler("onPlayerWasted",getRootElement(),playerDied)<br />
</syntaxhighlight><br />
<br />
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.<br />
<br />
==Where to go from here==<br />
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.<br />
<br />
From here we recommend reading the [[debugging]] tutorial. Good debugging skills are an absolute necessity when you are making scripts.<br />
<br />
[[ru:Scripting Introduction]]<br />
[[it:Introduzione allo scripting]]<br />
[[es:Introducción a la Programación]]<br />
</p></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/showChat&diff=47460AR/showChat2016-05-05T19:24:27Z<p>Jaber: Created page with "__NOTOC__ {{Server client function}} هذه الوظيفة تستخدم لاخفاء واظهار الكلام بالشات. ==Syntax== <section name="Client" class="client..."</p>
<hr />
<div>__NOTOC__ <br />
{{Server client function}} <br />
هذه الوظيفة تستخدم لاخفاء واظهار الكلام بالشات.<br />
<br />
==Syntax==<br />
<section name="Client" class="client" show="true"><br />
<syntaxhighlight lang="lua"><br />
bool showChat ( bool show )<br />
</syntaxhighlight><br />
<br />
===شرح الارقمنات=== <br />
*'''show:''' الظهور true = اظهار الشات , false = اخفاء الشات.<br />
<br />
===Returns===<br />
Returns ''true'' if the player's chat was shown or hidden successfully, ''false'' otherwise.<br />
</section><br />
<section name="Server" class="server" show="true"><br />
<syntaxhighlight lang="lua"><br />
bool showChat ( player thePlayer, bool show )<br />
</syntaxhighlight><br />
<br />
===شرح الارقمنات=== <br />
*'''thePlayer:''' الاعب الذي تبي تخفي له الشات.<br />
*'''show:''' الظهور true = اظهار الشات , false = اخفاء الشات.<br />
<br />
===Returns===<br />
Returns ''true'' if the player's chat was shown or hidden successfully, ''false'' otherwise.<br />
</section><br />
<br />
==Example== <br />
<section name="Client" class="client" show="true"><br />
هذا المثال يخفي الشات عند الضغط على حر ف 'i'<br />
<syntaxhighlight lang="lua"><br />
--This example below is for all versions until 1.4:<br />
local isChatVisible = true --Let's assume the chat is visible as soon as the resource starts.<br />
<br />
function chat(key, keyState)<br />
if isChatVisible then --Check or the chat is visible.<br />
showChat(false) --If it is, hide it.<br />
isChatVisible = false<br />
else<br />
showChat(true) --If it is not, show it.<br />
isChatVisible = true<br />
end<br />
end<br />
<br />
bindKey("i", "down", chat) --Make a bind key to start the function as soon as a player presses the key 'i'<br />
<br />
<br />
--This example below is for version 1.4 and up:<br />
function chat(key, keyState)<br />
if isChatVisible() then --Check or the chat is visible.<br />
showChat(false) --If it is, hide it.<br />
else<br />
showChat(true) --If it is not, show it.<br />
end<br />
end<br />
<br />
bindKey("i", "down", chat) --Make a bind key to start the function as soon as a player presses the key 'i'<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Server functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setElementPosition&diff=47398AR/setElementPosition2016-04-17T16:20:43Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لنقل الالمنت او الشيئ لاحداثيات محددة.<br />
<br />
<div style="background: #FF7070; border: 3px solid #FF0000;"><br />
'''Attention:''' Do not use this function to spawn a [[player]]. It will cause problems with other functions like [[warpPedIntoVehicle]]. <br><br />
Use [[spawnPlayer]] instead.<br />
</div><br />
<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
bool setElementPosition ( element theElement, float x, float y, float z [, bool warp = true ] ) <br />
</syntaxhighlight> <br />
{{OOP||[[element]]:setPosition|position|getElementPosition}}<br />
<br />
===شرح الارقمنتات=== <br />
*'''theElement:''' الالمنت الذي تريد جلب احداثيات.<br />
*'''x:''' الاحداثيات x.<br />
*'''y:''' الاحداثيات y.<br />
*'''z:''' الاحداثيات z.<br />
<br />
===Optional Arguments===<br />
*'''warp:''' ان كنت تريد نقل الاعب.<br />
<br />
===Returns===<br />
Returns ''true'' if the function was successful, ''false'' otherwise.<br />
<br />
==Example== <br />
<section name="Example 1" class="server" show="true"><br />
هذه الوظيفة عند كتابة امر باف8 تقوم بنقل الاعب.<br />
<syntaxhighlight lang="lua"><br />
function consoleSetPlayerPosition ( source, commandName, posX, posY, posZ )<br />
setElementPosition ( source, posX, posY, posZ )<br />
end<br />
addCommandHandler ( "setpos", consoleSetPlayerPosition )<br />
</syntaxhighlight><br />
</section><br />
<section name="Example 2" class="client" show="false"><br />
<br />
<syntaxhighlight lang="lua"><br />
function consoleSetPlayerPosition ( commandName, posX, posY, posZ )<br />
setElementPosition ( localPlayer, posX, posY, posZ )<br />
end<br />
addCommandHandler ( "setpos", consoleSetPlayerPosition )<br />
</syntaxhighlight><br />
</section><br />
<section name="Example 3" class="server" show="false"><br />
This example enables a player to type /warpto <playername> to warp to them. If the player being warped to is in a vehicle with a free passenger seat, it will warp into the vehicle.<br />
<syntaxhighlight lang="lua"><br />
function consoleWarpTo ( sourcePlayer, commandName, player2nick )<br />
-- Make sure required parameters are set<br />
if ( not sourcePlayer or not player2nick ) then return end<br />
-- Setup the variables we will be using for teleportation<br />
local x, y, z, r, d = 0, 0, 0, 0, 2.5<br />
-- Grab the element identifier of the player we are trying to warp to<br />
local player2 = getPlayerFromNick ( player2nick )<br />
-- Make sure it exists!<br />
if ( player2 ) then<br />
-- Is the player we're warping to in a vehicle?<br />
if ( isPlayerInVehicle ( player2 ) ) then<br />
-- Indeed they are, let's get the vehicle information such as the vehicle element itself, and the seats it's got.<br />
local player2vehicle = getPlayerOccupiedVehicle ( player2 )<br />
local numseats = getVehicleMaxPassengers ( player2vehicle )<br />
local i = 0<br />
-- Loop over the seats to see if there's a free one<br />
while ( i < numseats ) do<br />
if ( getVehicleOccupant ( player2vehicle, i ) ) then<br />
-- This seat isn't free, go ahead and check the next one<br />
i = i + 1<br />
else<br />
-- This seat is free, get out of the loop<br />
break<br />
end<br />
end<br />
-- Check if 'i' is lower than the number of seats. If it is, it means it's the number of a free seat<br />
if ( i < numseats ) then<br />
-- Teleport the player into the seat<br />
warpPlayerIntoVehicle ( sourcePlayer, player2vehicle, i )<br />
else<br />
-- There are no free seats, tell the player that.<br />
outputChatBox ( "Sorry, the player's vehicle is full (" .. getVehicleName ( player2vehicle ) .. " " .. i .. "/" .. numseats .. ")", sourcePlayer )<br />
end<br />
else<br />
-- The player isn't in a vehicle, let's get the player's position and warp to them.<br />
x, y, z = getElementPosition ( player2 )<br />
r = getPlayerRotation ( player2 )<br />
-- Make sure we get interior data, they might be inside one!<br />
interior = getElementInterior ( player2 )<br />
dimension = getElementDimension ( player2 )<br />
-- Do some funky math to make sure that we dont teleport inside of them (get us both stuck inside each other)<br />
x = x - ( ( math.cos ( math.rad ( r + 90 ) ) ) * d )<br />
y = y - ( ( math.sin ( math.rad ( r + 90 ) ) ) * d )<br />
-- Set a few timers for setting interiors, dimensions and positions<br />
setTimer ( setElementInterior, 800, 1, sourcePlayer, interior )<br />
setTimer ( setElementDimension, 900, 1, sourcePlayer, dimension )<br />
setTimer ( setElementPosition, 1000, 1, sourcePlayer, x, y, z )<br />
setTimer ( setPlayerRotation, 1000, 1, sourcePlayer, r )<br />
-- Fade the camera to make it look nicer<br />
fadeCamera ( sourcePlayer, false, 1, 0, 0, 0 )<br />
-- Fade it back once it's all complete!<br />
setTimer ( fadeCamera, 1000, 1, sourcePlayer, true, 1 )<br />
end<br />
else<br />
-- No player by the specified name was found, tell the warper this.<br />
outputChatBox ( "No such player.", sourcePlayer )<br />
end<br />
end<br />
addCommandHandler ( "warpto", consoleWarpTo )<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{AR/Element functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setElementPosition&diff=47397AR/setElementPosition2016-04-17T16:18:45Z<p>Jaber: Created page with "__NOTOC__ {{Server client function}} هذه الوظيفة تستخدم لنقل الالمنت او الشيئ لاحداثيات محددة. <div style="background: #FF7070..."</p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لنقل الالمنت او الشيئ لاحداثيات محددة.<br />
<br />
<div style="background: #FF7070; border: 3px solid #FF0000;"><br />
'''Attention:''' Do not use this function to spawn a [[player]]. It will cause problems with other functions like [[warpPedIntoVehicle]]. <br><br />
Use [[spawnPlayer]] instead.<br />
</div><br />
<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
bool setElementPosition ( element theElement, float x, float y, float z [, bool warp = true ] ) <br />
</syntaxhighlight> <br />
{{OOP||[[element]]:setPosition|position|getElementPosition}}<br />
<br />
===شرح الارقمنتات=== <br />
*'''theElement:''' الالمنت الذي تريد جلب احداثيات.<br />
*'''x:''' الاحداثيات x.<br />
*'''y:''' الاحداثيات y.<br />
*'''z:''' الاحداثيات z.<br />
<br />
===Optional Arguments===<br />
*'''warp:''' ان كنت تريد نقل الاعب.<br />
<br />
===Returns===<br />
Returns ''true'' if the function was successful, ''false'' otherwise.<br />
<br />
==Example== <br />
<section name="Example 1" class="server" show="true"><br />
هذه الوظيفة عند كتابة امر باف8 تقوم بنقل الاعب.<br />
<syntaxhighlight lang="lua"><br />
function consoleSetPlayerPosition ( source, commandName, posX, posY, posZ )<br />
setElementPosition ( source, posX, posY, posZ )<br />
end<br />
addCommandHandler ( "setpos", consoleSetPlayerPosition )<br />
</syntaxhighlight><br />
</section><br />
<section name="Example 2" class="client" show="false"><br />
<br />
<syntaxhighlight lang="lua"><br />
function consoleSetPlayerPosition ( commandName, posX, posY, posZ )<br />
setElementPosition ( localPlayer, posX, posY, posZ )<br />
end<br />
addCommandHandler ( "setpos", consoleSetPlayerPosition )<br />
</syntaxhighlight><br />
</section><br />
<section name="Example 3" class="server" show="false"><br />
This example enables a player to type /warpto <playername> to warp to them. If the player being warped to is in a vehicle with a free passenger seat, it will warp into the vehicle.<br />
<syntaxhighlight lang="lua"><br />
function consoleWarpTo ( sourcePlayer, commandName, player2nick )<br />
-- Make sure required parameters are set<br />
if ( not sourcePlayer or not player2nick ) then return end<br />
-- Setup the variables we will be using for teleportation<br />
local x, y, z, r, d = 0, 0, 0, 0, 2.5<br />
-- Grab the element identifier of the player we are trying to warp to<br />
local player2 = getPlayerFromNick ( player2nick )<br />
-- Make sure it exists!<br />
if ( player2 ) then<br />
-- Is the player we're warping to in a vehicle?<br />
if ( isPlayerInVehicle ( player2 ) ) then<br />
-- Indeed they are, let's get the vehicle information such as the vehicle element itself, and the seats it's got.<br />
local player2vehicle = getPlayerOccupiedVehicle ( player2 )<br />
local numseats = getVehicleMaxPassengers ( player2vehicle )<br />
local i = 0<br />
-- Loop over the seats to see if there's a free one<br />
while ( i < numseats ) do<br />
if ( getVehicleOccupant ( player2vehicle, i ) ) then<br />
-- This seat isn't free, go ahead and check the next one<br />
i = i + 1<br />
else<br />
-- This seat is free, get out of the loop<br />
break<br />
end<br />
end<br />
-- Check if 'i' is lower than the number of seats. If it is, it means it's the number of a free seat<br />
if ( i < numseats ) then<br />
-- Teleport the player into the seat<br />
warpPlayerIntoVehicle ( sourcePlayer, player2vehicle, i )<br />
else<br />
-- There are no free seats, tell the player that.<br />
outputChatBox ( "Sorry, the player's vehicle is full (" .. getVehicleName ( player2vehicle ) .. " " .. i .. "/" .. numseats .. ")", sourcePlayer )<br />
end<br />
else<br />
-- The player isn't in a vehicle, let's get the player's position and warp to them.<br />
x, y, z = getElementPosition ( player2 )<br />
r = getPlayerRotation ( player2 )<br />
-- Make sure we get interior data, they might be inside one!<br />
interior = getElementInterior ( player2 )<br />
dimension = getElementDimension ( player2 )<br />
-- Do some funky math to make sure that we dont teleport inside of them (get us both stuck inside each other)<br />
x = x - ( ( math.cos ( math.rad ( r + 90 ) ) ) * d )<br />
y = y - ( ( math.sin ( math.rad ( r + 90 ) ) ) * d )<br />
-- Set a few timers for setting interiors, dimensions and positions<br />
setTimer ( setElementInterior, 800, 1, sourcePlayer, interior )<br />
setTimer ( setElementDimension, 900, 1, sourcePlayer, dimension )<br />
setTimer ( setElementPosition, 1000, 1, sourcePlayer, x, y, z )<br />
setTimer ( setPlayerRotation, 1000, 1, sourcePlayer, r )<br />
-- Fade the camera to make it look nicer<br />
fadeCamera ( sourcePlayer, false, 1, 0, 0, 0 )<br />
-- Fade it back once it's all complete!<br />
setTimer ( fadeCamera, 1000, 1, sourcePlayer, true, 1 )<br />
end<br />
else<br />
-- No player by the specified name was found, tell the warper this.<br />
outputChatBox ( "No such player.", sourcePlayer )<br />
end<br />
end<br />
addCommandHandler ( "warpto", consoleWarpTo )<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Element functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=GetElementInterior&diff=47396GetElementInterior2016-04-17T16:13:05Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
This function allows you to retrieve the interior of any element. An interior is the current loaded place, 0 being outside.<br />
<br />
==Syntax==<br />
<syntaxhighlight lang="lua"><br />
int getElementInterior ( element theElement )<br />
</syntaxhighlight><br />
{{OOP||[[element]]:getInterior|interior|setElementInterior}}<br />
<br />
===Required Arguments===<br />
*'''theElement:''' The element of which you'd like to retrieve the interior<br />
<br />
===Returns===<br />
Returns an [[int]] for the interior if '''theElement''' is valid, ''false'' otherwise.<br />
<br />
==Example==<br />
<section show="true" name="Server" class="server"><br />
This example shows a player if he is outside or not, when he enters the command 'AmIOutside'.<br />
<syntaxhighlight lang="lua"><br />
function AmIOutside ( thePlayer, command )<br />
if ( getElementInterior(thePlayer) == 0 ) then<br />
outputChatBox ( "Yes you are outside " .. getPlayerName(thePlayer), thePlayer )<br />
else<br />
outputChatBox ( "No you aren't outside " .. getPlayerName(thePlayer), thePlayer )<br />
end<br />
end<br />
addCommandHandler ( "AmIOutside", AmIOutside )<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Element functions}}<br />
<br />
[[de:getElementInterior]]<br />
[[ar:getElementInterior]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/getElementInterior&diff=47395AR/getElementInterior2016-04-17T16:12:46Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
هذه الوظيفة تقوم بجلب رقم المبنى الموجود به الالمنت.<br />
<br />
==Syntax==<br />
<syntaxhighlight lang="lua"><br />
int getElementInterior ( element theElement )<br />
</syntaxhighlight><br />
{{OOP||[[element]]:getInterior|interior|setElementInterior}}<br />
<br />
===شرح الارقمنتات===<br />
*'''theElement:''' الالمنت او الشيئ الذي تريد جلب رقم المبنى الموجود به<br />
<br />
===Returns===<br />
Returns an [[int]] for the interior if '''theElement''' is valid, ''false'' otherwise.<br />
<br />
==Example==<br />
<section show="true" name="Server" class="server"><br />
هذا الكود يتحقق ان كان الاعب داخل المبنى 0 عند كتابة امر باف8'.<br />
<syntaxhighlight lang="lua"><br />
function AmIOutside ( thePlayer, command )<br />
if ( getElementInterior(thePlayer) == 0 ) then --ان كان الاعب داخل المبنى 0<br />
outputChatBox ( "Yes you are outside " .. getPlayerName(thePlayer), thePlayer ) --اخراج كلام بالشات<br />
else --ان لم يكن<br />
outputChatBox ( "No you aren't outside " .. getPlayerName(thePlayer), thePlayer ) --اخراج كلام بالشات<br />
end<br />
end<br />
addCommandHandler ( "AmIOutside", AmIOutside )--عند كتابة الامر باف8 "AmIOutside"<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{AR/Element functions}}<br />
<br />
[[de:getElementInterior]]<br />
[[en:getElementInterior]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/getElementInterior&diff=47394AR/getElementInterior2016-04-17T16:12:28Z<p>Jaber: Created page with "__NOTOC__ {{Server client function}} هذه الوظيفة تقوم بجلب رقم المبنى الموجود به الالمنت. ==Syntax== <syntaxhighlight lang="lua"> int getElementIn..."</p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
هذه الوظيفة تقوم بجلب رقم المبنى الموجود به الالمنت.<br />
<br />
==Syntax==<br />
<syntaxhighlight lang="lua"><br />
int getElementInterior ( element theElement )<br />
</syntaxhighlight><br />
{{OOP||[[element]]:getInterior|interior|setElementInterior}}<br />
<br />
===شرح الارقمنتات===<br />
*'''theElement:''' الالمنت او الشيئ الذي تريد جلب رقم المبنى الموجود به<br />
<br />
===Returns===<br />
Returns an [[int]] for the interior if '''theElement''' is valid, ''false'' otherwise.<br />
<br />
==Example==<br />
<section show="true" name="Server" class="server"><br />
هذا الكود يتحقق ان كان الاعب داخل المبنى 0 عند كتابة امر باف8'.<br />
<syntaxhighlight lang="lua"><br />
function AmIOutside ( thePlayer, command )<br />
if ( getElementInterior(thePlayer) == 0 ) then --ان كان الاعب داخل المبنى 0<br />
outputChatBox ( "Yes you are outside " .. getPlayerName(thePlayer), thePlayer ) --اخراج كلام بالشات<br />
else --ان لم يكن<br />
outputChatBox ( "No you aren't outside " .. getPlayerName(thePlayer), thePlayer ) --اخراج كلام بالشات<br />
end<br />
end<br />
addCommandHandler ( "AmIOutside", AmIOutside )--عند كتابة الامر باف8 "AmIOutside"<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Element functions}}<br />
<br />
[[de:getElementInterior]]<br />
[[en:getElementInterior]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=Client_Scripting_Events&diff=47358Client Scripting Events2016-04-07T12:43:27Z<p>Jaber: </p>
<hr />
<div><pageclass class="client"></pageclass><br />
This page lists all '''client-side''' scripting [[event]]s that have been implemented and are available in the Deathmatch mod.<br />
<br />
To request a function or event, use [[Requested Functions and Events]].<br />
<br />
'''Server-side scripting events can be found here: [[Server Scripting Events]]<br />
<br />
==Browser events==<br />
{{CEF_events}}<br />
<br />
==Colshape events==<br />
{{Client_colshape_events}}<br />
<br />
==Element events==<br />
{{Client_element_events}}<br />
<br />
==GUI events==<br />
{{GUI_events}}<br />
<br />
==Marker events==<br />
{{Client_marker_events}}<br />
<br />
==Ped events==<br />
{{Client_ped_events}}<br />
<br />
==Pickup events==<br />
{{Client_pickup_events}}<br />
<br />
==Player events==<br />
{{Client_player_events}}<br />
<br />
==Object events==<br />
{{Client_object_events}}<br />
<br />
==Projectile events==<br />
{{Client_projectile_events}}<br />
<br />
==Resource events==<br />
{{Client_resource_events}}<br />
<br />
==Sound events==<br />
{{Sound_events}}<br />
<br />
==Vehicle events==<br />
{{Client_vehicle_events}}<br />
<br />
==Weapon creation events==<br />
{{Client_weapon_creation_events}}<br />
<br />
==Other events==<br />
{{Client_other_events}}<br />
<br />
[[pl:PL/Client Scripting Events]]<br />
[[ru:Client Scripting Events]]<br />
[[es:Client Scripting Events]]<br />
[[fr:Client Scripting Events]]<br />
[[tr:Client Taraflı Eventler]]<br />
[[ar:Client Scripting Events]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setPlayerNametagShowing&diff=46984AR/setPlayerNametagShowing2016-03-24T14:47:34Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}}<br />
<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
<br />
===شرح الارقمنتات=== <br />
*'''thePlayer:''' الاعب الذي تريد اظهار\اخفاء اسمه<br />
*'''showing:''' استخدم true\false حتى تخفي\تظهر الاسم<br />
<br />
''true'' = اظهار الاسم , ''false'' = اخفاء الاسم .<br />
<br />
==Example== <br />
هذه الامثلة تخفي اسم الاعب<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) <br />
for key, player in ipairs ( players ) do -- لوب لكل الاعبين<br />
setPlayerNametagShowing ( player, false ) -- اخفاء اسمائهم (false)<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
--مثال اخر<br />
<br />
function onPlayerJoin ( )<br />
setPlayerNametagShowing ( source, false ) --اخفاء اسمه (false)<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin ) --حدث عندما الاعب يدخل<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{AR/Player functions}}<br />
<br />
<br />
<br />
<br />
[[en:setPlayerNametagShowing]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=SetPlayerNametagShowing&diff=46983SetPlayerNametagShowing2016-03-24T14:12:28Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|This function allows you to set whether a player's nametag visibility both clientside and serverside}}<br />
<br />
Use this to define whether the player's name tag is visible or invisible.<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
{{OOP||[[player]]:setNametagShowing|nametagShowing|isPlayerNametagShowing}}<br />
===Required Arguments=== <br />
*'''thePlayer:''' Define the player whos tag visiblity status you want to change<br />
*'''showing:''' Use true or false to show/hide the tag<br />
<br />
===Returns===<br />
Returns ''true'' if successful, ''false'' otherwise<br />
<br />
==Example== <br />
This script will turn off player tags for everyone<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) -- Store all the players in the server into a table<br />
for key, player in ipairs ( players ) do -- for all the players in the table<br />
setPlayerNametagShowing ( player, false ) -- turn off their nametag<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
function onPlayerJoin ( )<br />
-- Whoever joins the server should also have their nametags deactivated<br />
setPlayerNametagShowing ( source, false )<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin )<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{Player functions}}<br />
<br />
<br />
[[ar:setPlayerNametagShowing]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setPlayerNametagShowing&diff=46982AR/setPlayerNametagShowing2016-03-24T14:12:16Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}}<br />
<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
<br />
===شرح الارقمنتات=== <br />
*'''thePlayer:''' الاعب الذي تريد اظهار\اخفاء اسمه<br />
*'''showing:''' استخدم true\false حتى تخفي\تظهر الاسم<br />
<br />
''true'' = اظهار الاسم , ''false'' = اظفار الاسم .<br />
<br />
==Example== <br />
هذه الامثلة تخفي اسم الاعب<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) <br />
for key, player in ipairs ( players ) do -- لوب لكل الاعبين<br />
setPlayerNametagShowing ( player, false ) -- اخفاء اسمائهم (false)<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
--مثال اخر<br />
<br />
function onPlayerJoin ( )<br />
setPlayerNametagShowing ( source, false ) --افخاء اسمه (false<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin ) --حدث عندما الاعب يدخل<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{AR/Player functions}}<br />
<br />
<br />
<br />
<br />
[[en:setPlayerNametagShowing]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setPlayerNametagShowing&diff=46981AR/setPlayerNametagShowing2016-03-24T14:11:49Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}}<br />
<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
<br />
===شرح الارقمنتات=== <br />
*'''thePlayer:''' الاعب الذي تريد اظهار\اخفاء اسمه<br />
*'''showing:''' استخدم true\false حتى تخفي\تظهر الاسم<br />
<br />
''true'' = اظهار الاسم , ''false'' = اظفار الاسم .<br />
<br />
==Example== <br />
هذه الامثلة تخفي اسم الاعب<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) <br />
for key, player in ipairs ( players ) do -- لوب لكل الاعبين<br />
setPlayerNametagShowing ( player, false ) -- اخفاء اسمائهم (false)<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
--مثال اخر<br />
<br />
function onPlayerJoin ( )<br />
setPlayerNametagShowing ( source, false ) --افخاء اسمه (false<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin ) --حدث عندما الاعب يدخل<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{AR/Player functions}}<br />
<br />
<br />
<br />
<br />
[[en:createMarker]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setPlayerNametagShowing&diff=46980AR/setPlayerNametagShowing2016-03-24T14:06:35Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}}<br />
<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
<br />
===شرح الارقمنتات=== <br />
*'''thePlayer:''' الاعب الذي تريد اظهار\اخفاء اسمه<br />
*'''showing:''' استخدم true\false حتى تخفي\تظهر الاسم<br />
<br />
''true'' = اظهار الاسم , ''false'' = اظفار الاسم .<br />
<br />
==Example== <br />
هذه الامثلة تخفي اسم الاعب<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) <br />
for key, player in ipairs ( players ) do -- لوب لكل الاعبين<br />
setPlayerNametagShowing ( player, false ) -- اخفاء اسمائهم (false)<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
--مثال اخر<br />
<br />
function onPlayerJoin ( )<br />
setPlayerNametagShowing ( source, false ) --افخاء اسمه (false<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin ) --حدث عندما الاعب يدخل<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{AR/Player functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setPlayerNametagShowing&diff=46979AR/setPlayerNametagShowing2016-03-24T14:05:46Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}}<br />
<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
<br />
===شرح الارقمنتات=== <br />
*'''thePlayer:''' الاعب الذي تريد اظهار\اخفاء اسمه<br />
*'''showing:''' استخدم true\false حتى تخفي\تظهر الاسم<br />
<br />
''true'' = اظهار الاسم , ''false'' = اظفار الاسم .<br />
<br />
==Example== <br />
This script will turn off player tags for everyone<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) <br />
for key, player in ipairs ( players ) do -- لوب لكل الاعبين<br />
setPlayerNametagShowing ( player, false ) -- اخفاء اسمائهم (false)<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
--مثال اخر<br />
<br />
function onPlayerJoin ( )<br />
setPlayerNametagShowing ( source, false ) --افخاء اسمه (false<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin ) --حدث عندما الاعب يدخل<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{AR/Player functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setPlayerNametagShowing&diff=46978AR/setPlayerNametagShowing2016-03-24T13:53:19Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}}<br />
<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
<br />
<br />
===Returns===<br />
Returns ''true'' if successful, ''false'' otherwise<br />
<br />
==Example== <br />
This script will turn off player tags for everyone<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) -- Store all the players in the server into a table<br />
for key, player in ipairs ( players ) do -- for all the players in the table<br />
setPlayerNametagShowing ( player, false ) -- turn off their nametag<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
function onPlayerJoin ( )<br />
-- Whoever joins the server should also have their nametags deactivated<br />
setPlayerNametagShowing ( source, false )<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin )<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{Player functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setPlayerNametagShowing&diff=46977AR/setPlayerNametagShowing2016-03-24T13:53:04Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}}<br />
<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
{{OOP||[[player]]:setNametagShowing|nametagShowing|isPlayerNametagShowing}}<br />
<br />
===Returns===<br />
Returns ''true'' if successful, ''false'' otherwise<br />
<br />
==Example== <br />
This script will turn off player tags for everyone<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) -- Store all the players in the server into a table<br />
for key, player in ipairs ( players ) do -- for all the players in the table<br />
setPlayerNametagShowing ( player, false ) -- turn off their nametag<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
function onPlayerJoin ( )<br />
-- Whoever joins the server should also have their nametags deactivated<br />
setPlayerNametagShowing ( source, false )<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin )<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{Player functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setPlayerNametagShowing&diff=46976AR/setPlayerNametagShowing2016-03-24T13:52:44Z<p>Jaber: Created page with "__NOTOC__ {{Server client function}} {{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}} ==Syntax== ..."</p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
{{New feature|3|1.0|هذه الوظيفة تستخدم لحذف واظهار اسم الاعب الذي يكون عليه}}<br />
<br />
<br />
==Syntax== <br />
<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd --><br />
<syntaxhighlight lang="lua"><br />
bool setPlayerNametagShowing ( player thePlayer, bool showing )<br />
</syntaxhighlight> <br />
{{OOP||[[player]]:setNametagShowing|nametagShowing|isPlayerNametagShowing}}<br />
===Required Arguments=== <br />
*'''thePlayer:''' Define the player whos tag visiblity status you want to change<br />
*'''showing:''' Use true or false to show/hide the tag<br />
<br />
===Returns===<br />
Returns ''true'' if successful, ''false'' otherwise<br />
<br />
==Example== <br />
This script will turn off player tags for everyone<br />
<syntaxhighlight lang="lua"><br />
function onResourceStart ( )<br />
local players = getElementsByType ( "player" ) -- Store all the players in the server into a table<br />
for key, player in ipairs ( players ) do -- for all the players in the table<br />
setPlayerNametagShowing ( player, false ) -- turn off their nametag<br />
end<br />
end<br />
addEventHandler ( "onResourceStart", resourceRoot, onResourceStart )<br />
<br />
function onPlayerJoin ( )<br />
-- Whoever joins the server should also have their nametags deactivated<br />
setPlayerNametagShowing ( source, false )<br />
end<br />
addEventHandler ( "onPlayerJoin", root, onPlayerJoin )<br />
<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{Player functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/createMarker&diff=46703AR/createMarker2016-02-19T16:42:48Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لصنع ماركر .<br />
<br />
==Syntax==<br />
<section name="Server" class="server" show="true"><br />
<syntaxhighlight lang="lua"><br />
marker createMarker ( float x, float y, float z [, string theType = "checkpoint", float size = 4.0, int r = 0, int g = 0, int b = 255, int a = 255, visibleTo = getRootElement( ) ] )<br />
</syntaxhighlight><br />
{{OOP||Marker}}<br />
===Required Arguments===<br />
* '''x''': احداثيات الماركر x.<br />
* '''y''': احداثيات الماركر y.<br />
* '''z''': احداثيات ارتفاع الماركر z.<br />
<br />
===Optional arguments===<br />
{{OptionalArg}}<br />
* '''theType''': نوع الماركر,شكل الماركر:<br />
* '''size''': حجم الماركر الذي تريد صنعه.<br />
* '''r''': (0 - 255)نسبة اللون الاحمر بالماركر بين.<br />
* '''g''': (0 - 255)نسبة اللون الاخضر بالماركر بين.<br />
* '''b''': (0 - 255)نسبة اللون الازرق بالماركر بين.<br />
* '''a''': (0 - 255)نسبة ظهور الماركر 0 = مخفي ,وبعدها يبدأ يظهر<br />
* '''visibleTo''': الالمنت الذي يستطيع رؤية الماركر [[visibility]].<br />
</section><br />
<section name="Client" class="client" show="true"><br />
<syntaxhighlight lang="lua"><br />
marker createMarker ( float x, float y, float z [, string theType = "checkpoint", float size = 4.0, int r = 0, int g = 0, int b = 255, int a = 255 ] )<br />
</syntaxhighlight><br />
{{OOP||Marker}}<br />
===Required Arguments===<br />
* '''x''': احداثيات الماركر x.<br />
* '''y''': احداثيات الماركر y.<br />
* '''z''': احداثيات ارتفاع الماركر z.<br />
<br />
===Optional arguments===<br />
{{OptionalArg}}<br />
* '''theType''': نوع الماركر,شكل الماركر<br />
* '''size''': حجم الماركر الذي تريد صنعه.<br />
* '''r''': (0 - 255)نسبة اللون الاحمر بالماركر بين.<br />
* '''g''': (0 - 255)نسبة اللون الاخضر بالماركر بين.<br />
* '''b''': (0 - 255)نسبة اللون الازرق بالماركر بين.<br />
* '''a''': (0 - 255)نسبة ظهور الماركر 0 = مخفي ,وبعدها يبدأ يظهر .<br />
</section><br />
<br />
==Example==<br />
<section name="Example 1" class="server" show="true"><br />
هذا المثال يصنع ماركر بجانب الاعب:<br />
<syntaxhighlight lang="lua"><br />
function consoleCreateMarker ( thePlayer, commandName )<br />
if ( thePlayer ) then<br />
local x, y, z = getElementPosition ( thePlayer ) --يجيب احداثيات الاعب<br />
-- صنع ماركر بجانب الاعب:<br />
local theMarker = createMarker ( x + 2, y + 2, z, "cylinder", 1.5, 255, 255, 0, 170 )<br />
if ( theMarker ) then <br />
outputConsole ( "تم صنع الماركر بنجاح", thePlayer )<br />
else<br />
outputConsole ( "خطأ في صنع الماركر", thePlayer )<br />
end<br />
end<br />
end<br />
addCommandHandler ( "createmarker", consoleCreateMarker )<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Marker functions}}<br />
[[ru:createMarker]]<br />
[[en:createMarker]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=RU/createMarker&diff=46702RU/createMarker2016-02-19T16:42:27Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{RU/Server client function}}<br />
Эта функция создает маркер. Маркер - это 3D-модель в игровом мире, которая может обозначить какую-либо точку или область, и часто используется, чтобы давать игрокам указания, где именно можно выполнять определенные действия, например, заходить в здание.<br />
<br />
Есть ограничения на максимальное число одновременно видимых маркеров, а именно:<br />
* Короны: 32<br />
* Чекпоинты, кольца, цилиндры и стрелки все в сумме: 32<br />
<br />
Создавать можно практически неограниченное число маркеров (при условии, что хватает памяти и ограничения по числу элементов), однако игрок сможет увидеть только ближайшие из них, и не более указанных ограничений.<br />
<br />
==Синтаксис==<br />
<section name="Server" class="server" show="true"><br />
<syntaxhighlight lang="lua"><br />
marker createMarker ( float x, float y, float z, [string theType, float size, int r, int g, int b, int a, visibleTo = getRootElement()] )<br />
</syntaxhighlight><br />
<br />
===Обязательные аргументы===<br />
* '''x''': Вещественное число - координата X на карте.<br />
* '''y''': Вещественное число - координата Y на карте.<br />
* '''z''': Вещественное число - координата Z на карте.<br />
<br />
===Дополнительные аргументы===<br />
{{RU/OptionalArg}}<br />
* '''theType''': Внешний вид маркера. Доступны следующие типы:<br />
{{RU/Marker_types}}<br />
* '''size''': Диаметр маркера в метрах.<br />
* '''r''': Целое число - количество красного компонента в цвете маркера (0 - 255).<br />
* '''g''': Целое число - количество красного компонента в цвете маркера (0 - 255).<br />
* '''b''': Целое число - количество красного компонента в цвете маркера (0 - 255).<br />
* '''a''': Целое число - прозрачность маркера (0 - 255 где 0 - полностью прозрачный, а 255 - полностью непрозрачный).<br />
* '''visibleTo''': Только этот элемент и его потомки смогут увидеть маркер. См.[[visibility]].<br />
</section><br />
<section name="Client" class="client" show="true"><br />
<syntaxhighlight lang="lua"><br />
marker createMarker ( float x, float y, float z, [string theType, float size, int r, int g, int b, int a] )<br />
</syntaxhighlight><br />
<br />
===Обязательные аргументы===<br />
* '''x''': Вещественное число - координата X на карте.<br />
* '''y''': Вещественное число - координата Y на карте.<br />
* '''z''': Вещественное число - координата Z на карте.<br />
<br />
===Дополнительные аргументы===<br />
{{RU/OptionalArg}}<br />
* '''theType''': Внешний вид маркера. Доступны следующие типы:<br />
{{RU/Marker_types}}<br />
* '''size''': Диаметр маркера в метрах.<br />
* '''r''': Целое число - количество красного компонента в цвете маркера (0 - 255).<br />
* '''g''': Целое число - количество красного компонента в цвете маркера (0 - 255).<br />
* '''b''': Целое число - количество красного компонента в цвете маркера (0 - 255).<br />
* '''a''': Целое число - прозрачность маркера (0 - 255 где 0 - полностью прозрачный, а 255 - полностью непрозрачный).<br />
</section><br />
<br />
===Вывод===<br />
Возвращает созданный [[marker|маркер]] , или ''false'' если были переданы некорректные аргументы.<br />
<br />
==Пример==<br />
<section name="Пример 1" class="server" show="true"><br />
Создает рядом с игроком маркер, когда он вводит команду 'createmarker':<br />
<syntaxhighlight lang="lua"><br />
-- эта функция вызывается при вводе 'createmarker':<br />
function consoleCreateMarker ( thePlayer, commandName )<br />
if ( thePlayer ) then<br />
local x, y, z = getElementPosition ( thePlayer ) -- get the player's position<br />
-- создаем цилиндрический маркер рядом с игроком<br />
local theMarker = createMarker ( x + 2, y + 2, z, "cylinder", 1.5, 255, 255, 0, 170 )<br />
if ( theMarker ) then -- проверяем, что успешно создали маркер<br />
outputConsole ( "Marker created successfully", thePlayer )<br />
else<br />
outputConsole ( "Failed to create marker", thePlayer )<br />
end<br />
end<br />
end<br />
addCommandHandler ( "createmarker", consoleCreateMarker )<br />
</syntaxhighlight><br />
</section><br />
<br />
<section name="Пример 2" class="both" show="true"><br />
Создает маркер в точке 0, 0, 20:<br />
<syntaxhighlight lang="lua"><br />
createMarker ( 0, 0, 20 )<br />
</syntaxhighlight><br />
</section><br />
<br />
==Смотрите также==<br />
{{RU/Marker functions}}<br />
[[en:createMarker]]<br />
[[ar:createMarker]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=CreateMarker&diff=46701CreateMarker2016-02-19T16:39:18Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
This function creates a marker. A marker is a 3D model in the world that can highlight a particular point or area, often used to instruct players where to go to perform actions such as entering buildings.<br />
<br />
There are various limits that govern the maximum number of each type that can be visible at once. These are:<br />
* Coronas: 32<br />
* Checkpoints, Rings, Cylinders and Arrows combined: 32<br />
<br />
You are able to create as many markers as you wish (memory and element limit permitting), but the player will only be able to see the nearest ones up to the limit.<br />
<br />
==Syntax==<br />
<section name="Server" class="server" show="true"><br />
<syntaxhighlight lang="lua"><br />
marker createMarker ( float x, float y, float z [, string theType = "checkpoint", float size = 4.0, int r = 0, int g = 0, int b = 255, int a = 255, visibleTo = getRootElement( ) ] )<br />
</syntaxhighlight><br />
{{OOP||Marker}}<br />
===Required Arguments===<br />
* '''x''': A floating point number representing the X coordinate on the map.<br />
* '''y''': A floating point number representing the Y coordinate on the map.<br />
* '''z''': A floating point number representing the Z coordinate on the map.<br />
<br />
===Optional arguments===<br />
{{OptionalArg}}<br />
* '''theType''': The visual type of the marker to be created. Possible values:<br />
{{Marker_types}}<br />
* '''size''': The diameter of the marker to be created, in meters.<br />
* '''r''': An integer number representing the amount of red to use in the colouring of the marker (0 - 255).<br />
* '''g''': An integer number representing the amount of green to use in the colouring of the marker (0 - 255).<br />
* '''b''': An integer number representing the amount of blue to use in the colouring of the marker (0 - 255).<br />
* '''a''': An integer number representing the amount of alpha to use in the colouring of the marker (0 - 255 where 0 is transparent and 255 is opaque).<br />
* '''visibleTo''': This defines which elements can see the marker. Defaults to visible to everyone. See [[visibility]].<br />
</section><br />
<section name="Client" class="client" show="true"><br />
<syntaxhighlight lang="lua"><br />
marker createMarker ( float x, float y, float z [, string theType = "checkpoint", float size = 4.0, int r = 0, int g = 0, int b = 255, int a = 255 ] )<br />
</syntaxhighlight><br />
{{OOP||Marker}}<br />
===Required Arguments===<br />
* '''x''': A floating point number representing the X coordinate on the map.<br />
* '''y''': A floating point number representing the Y coordinate on the map.<br />
* '''z''': A floating point number representing the Z coordinate on the map.<br />
<br />
===Optional arguments===<br />
{{OptionalArg}}<br />
* '''theType''': The visual type of the marker to be created. Possible values:<br />
{{Marker_types}}<br />
* '''size''': The diameter of the marker to be created, in meters.<br />
* '''r''': An integer number representing the amount of red to use in the colouring of the marker (0 - 255).<br />
* '''g''': An integer number representing the amount of green to use in the colouring of the marker (0 - 255).<br />
* '''b''': An integer number representing the amount of blue to use in the colouring of the marker (0 - 255).<br />
* '''a''': An integer number representing the amount of alpha to use in the colouring of the marker (0 - 255 where 0 is transparent and 255 is opaque).<br />
</section><br />
<br />
===Returns===<br />
Returns the [[marker]] element that was created, or ''false'' if the arguments are incorrect.<br />
<br />
==Example==<br />
<section name="Example 1" class="server" show="true"><br />
This example creates a marker next to the player when they type 'createmarker':<br />
<syntaxhighlight lang="lua"><br />
-- this function is called whenever someone types 'createmarker' in the console:<br />
function consoleCreateMarker ( thePlayer, commandName )<br />
if ( thePlayer ) then<br />
local x, y, z = getElementPosition ( thePlayer ) -- get the player's position<br />
-- create a cylindrical marker next to the player:<br />
local theMarker = createMarker ( x + 2, y + 2, z, "cylinder", 1.5, 255, 255, 0, 170 )<br />
if ( theMarker ) then -- check if the marker was created successfully<br />
outputConsole ( "Marker created successfully", thePlayer )<br />
else<br />
outputConsole ( "Failed to create marker", thePlayer )<br />
end<br />
end<br />
end<br />
addCommandHandler ( "createmarker", consoleCreateMarker )<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Marker functions}}<br />
[[ru:createMarker]]<br />
[[ar:createMarker]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/createMarker&diff=46700AR/createMarker2016-02-19T16:38:25Z<p>Jaber: </p>
<hr />
<div>__NOTOC__<br />
{{Server client function}}<br />
هذه الوظيفة تستخدم لصنع ماركر .<br />
<br />
==Syntax==<br />
<section name="Server" class="server" show="true"><br />
<syntaxhighlight lang="lua"><br />
marker createMarker ( float x, float y, float z [, string theType = "checkpoint", float size = 4.0, int r = 0, int g = 0, int b = 255, int a = 255, visibleTo = getRootElement( ) ] )<br />
</syntaxhighlight><br />
{{OOP||Marker}}<br />
===Required Arguments===<br />
* '''x''': احداثيات الماركر x.<br />
* '''y''': احداثيات الماركر y.<br />
* '''z''': احداثيات ارتفاع الماركر z.<br />
<br />
===Optional arguments===<br />
{{OptionalArg}}<br />
* '''theType''': نوع الماركر,شكل الماركر:<br />
* '''size''': حجم الماركر الذي تريد صنعه.<br />
* '''r''': (0 - 255)نسبة اللون الاحمر بالماركر بين.<br />
* '''g''': (0 - 255)نسبة اللون الاخضر بالماركر بين.<br />
* '''b''': (0 - 255)نسبة اللون الازرق بالماركر بين.<br />
* '''a''': (0 - 255)نسبة ظهور الماركر 0 = مخفي ,وبعدها يبدأ يظهر<br />
* '''visibleTo''': الالمنت الذي يستطيع رؤية الماركر [[visibility]].<br />
</section><br />
<section name="Client" class="client" show="true"><br />
<syntaxhighlight lang="lua"><br />
marker createMarker ( float x, float y, float z [, string theType = "checkpoint", float size = 4.0, int r = 0, int g = 0, int b = 255, int a = 255 ] )<br />
</syntaxhighlight><br />
{{OOP||Marker}}<br />
===Required Arguments===<br />
* '''x''': احداثيات الماركر x.<br />
* '''y''': احداثيات الماركر y.<br />
* '''z''': احداثيات ارتفاع الماركر z.<br />
<br />
===Optional arguments===<br />
{{OptionalArg}}<br />
* '''theType''': نوع الماركر,شكل الماركر<br />
* '''size''': حجم الماركر الذي تريد صنعه.<br />
* '''r''': (0 - 255)نسبة اللون الاحمر بالماركر بين.<br />
* '''g''': (0 - 255)نسبة اللون الاخضر بالماركر بين.<br />
* '''b''': (0 - 255)نسبة اللون الازرق بالماركر بين.<br />
* '''a''': (0 - 255)نسبة ظهور الماركر 0 = مخفي ,وبعدها يبدأ يظهر .<br />
</section><br />
<br />
==Example==<br />
<section name="Example 1" class="server" show="true"><br />
هذا المثال يصنع ماركر بجانب الاعب:<br />
<syntaxhighlight lang="lua"><br />
function consoleCreateMarker ( thePlayer, commandName )<br />
if ( thePlayer ) then<br />
local x, y, z = getElementPosition ( thePlayer ) --يجيب احداثيات الاعب<br />
-- صنع ماركر بجانب الاعب:<br />
local theMarker = createMarker ( x + 2, y + 2, z, "cylinder", 1.5, 255, 255, 0, 170 )<br />
if ( theMarker ) then <br />
outputConsole ( "تم صنع الماركر بنجاح", thePlayer )<br />
else<br />
outputConsole ( "خطأ في صنع الماركر", thePlayer )<br />
end<br />
end<br />
end<br />
addCommandHandler ( "createmarker", consoleCreateMarker )<br />
</syntaxhighlight><br />
</section><br />
<br />
==See Also==<br />
{{Marker functions}}<br />
[[ru:createMarker]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/setMarkerTarget&diff=46691AR/setMarkerTarget2016-02-16T18:47:41Z<p>Jaber: </p>
<hr />
<div>{{Server client function}}<br />
__NOTOC__ <br />
هذه الوظيفة تقوم بوضع الماركر باحداثيات محددة.<br />
<br />
<br />
<br />
==Syntax== <br />
<syntaxhighlight lang="lua"><br />
bool setMarkerTarget ( marker theMarker, float x, float y, float z ) <br />
</syntaxhighlight> <br />
{{OOP||[[Marker]]:setTarget|getMarkerTarget}}<br />
===Required Arguments=== <br />
*'''theMarker:''' الماركر الذي تريد وضع احداثيات له<br />
*'''x:''' احداثيات الماركر x .<br />
*'''y:''' احداثيات الماركر z .<br />
*'''z:''' احداثيات ارتفاع الماركر z .<br />
<br />
<br />
<br />
==Example== <br />
Creates a marker in the center of the map and points it north.<br />
<syntaxhighlight lang="lua"><br />
local marker = createMarker(0,0,0,"ring",7,255,0,0,255) --نصنع ماركر<br />
setMarkerTarget(marker,3000,0,0) --نضع الماركر باحداثيات<br />
</syntaxhighlight><br />
<br />
==See Also==<br />
{{Marker functions}}</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/Client_Scripting_Functions&diff=46606AR/Client Scripting Functions2016-02-10T13:10:53Z<p>Jaber: </p>
<hr />
<div><pageclass class="client"></pageclass><br />
{{Adding_Pages_to_Categories_and_Templates}}<br />
This page lists all the '''client-side''' scripting functions that have been implemented and are available as native functions from the Deathmatch mod. To request a function or event, use [[Requested Functions and Events]]<br />
<br />
For more functions, check the [[Useful_Functions|useful functions page]].<br />
__TOC__<br />
<br />
==وظائف الصوت==<br />
{{AR/Audio_functions}}<br />
<br />
==وظائف علامات الخريطة==<br />
{{AR/Blip_functions}}<br />
<br />
==وظائف الكاميرا==<br />
{{AR/Camera_functions}}<br />
<br />
==وظائف الملابس==<br />
{{AR/Client_Clothes and body functions}}<br />
<br />
==Collision shape functions==<br />
{{AR/Collision_shape_functions}}<br />
<br />
==وظائف الأسهم==<br />
{{AR/Client_cursor_functions}}<br />
<br />
== وظائف الرسم==<br />
{{AR/Drawing_functions}}<br />
<br />
==وظائف التأثيرات==<br />
{{AR/Client_Effects_functions}}<br />
<br />
==وظائف العناصر==<br />
{{AR/Client_Element_functions}}<br />
<br />
==وظائف المحرك==<br />
{{AR/Engine_functions}}<br />
<br />
==وظائف الحدث==<br />
{{AR/Client_event_functions}}<br />
<br />
==وظائف الانفجارات==<br />
{{AR/Client_explosion_functions}}<br />
<br />
==وظائف الملف==<br />
{{AR/Client file functions}}<br />
<br />
==وظائف الحريق==<br />
{{AR/Client fire functions}}<br />
<br />
==وظائف واجهة المستخدم الرسومية==<br />
{{AR/GUI_functions}}<br />
<br />
==وظائف مدخلات==<br />
{{AR/Client_input_functions}}<br />
<br />
==وظيفة العلامات==<br />
{{AR/Client_marker_functions}}<br />
<br />
==وظائف لهدف معين==<br />
{{AR/Client_object_functions}}<br />
<br />
==وظائف الإخراج==<br />
{{AR/Client_output_functions}}<br />
<br />
<br />
<br />
==وظائف الدعم==<br />
{{AR/Client_pickup_functions}}<br />
<br />
==وظائف الاعب==<br />
{{AR/Client_player_functions}}<br />
<br />
==Projectile functions==<br />
{{AR/Client_projectile_functions}}<br />
<br />
==Radar-area functions==<br />
{{AR/Client_radar-area_functions}}<br />
<br />
==وظائف الموارد==<br />
{{AR/Client_resource_functions}}<br />
<br />
==وظائف فريق==<br />
{{AR/Client_team_functions}}<br />
<br />
==Utility functions==<br />
{{AR/Client_utility_functions}}<br />
<br />
==وظائف السيارة==<br />
{{AR/Client_vehicle_functions}}<br />
<br />
==وظائف المياه==<br />
{{AR/Client_water_functions}}<br />
<br />
==وظائف سلاح==<br />
{{AR/Client_weapon_functions}}<br />
<br />
==Weapon Creation functions==<br />
Documentation can be found [http://code.google.com/p/mtasa-blue/source/detail?r=4555 here] and [http://code.google.com/p/mtasa-blue/source/detail?r=4557 here]<br />
{{AR/Client_weapon_creation_functions}}<br />
<br />
==وظائف العالم==<br />
{{AR/Client_world_functions}}<br />
<br />
==XML functions==<br />
{{AR/Client XML functions}}<br />
<br />
[[ar:Client Scripting Functions]]<br />
[[en:Client Scripting Functions]]<br />
[[pl:Funkcje po stronie klienta]]<br />
[[it:Funzioni Client-side]]<br />
[[ru:Client Scripting Functions]]<br />
[[de:Clientseitige_Funktionen]]<br />
[[tr:Client Taraflı Fonksiyonlar]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/Client_Scripting_Functions&diff=46605AR/Client Scripting Functions2016-02-10T13:10:38Z<p>Jaber: </p>
<hr />
<div><pageclass class="client"></pageclass><br />
{{Adding_Pages_to_Categories_and_Templates}}<br />
This page lists all the '''client-side''' scripting functions that have been implemented and are available as native functions from the Deathmatch mod. To request a function or event, use [[Requested Functions and Events]]<br />
<br />
For more functions, check the [[Useful_Functions|useful functions page]].<br />
__TOC__<br />
<br />
==وظائف الصوت==<br />
{{AR/Audio_functions}}<br />
<br />
==وظائف علامات الخريطة==<br />
{{AR/Blip_functions}}<br />
<br />
==وظائف الكاميرا==<br />
{{AR/Camera_functions}}<br />
<br />
==وظائف الملابس==<br />
{{AR/Client_Clothes and body functions}}<br />
<br />
==Collision shape functions==<br />
{{AR/Collision_shape_functions}}<br />
<br />
==وظائف الأسهم==<br />
{{AR/Client_cursor_functions}}<br />
<br />
== وظائف الرسم==<br />
{{AR/Drawing_functions}}<br />
<br />
==وظائف التأثيرات==<br />
{{AR/Client_Effects_functions}}<br />
<br />
==وظائف العناصر==<br />
{{AR/Client_Element_functions}}<br />
<br />
==وظائف المحرك==<br />
{{AR/Engine_functions}}<br />
<br />
==وظائف الحدث==<br />
{{AR/Client_event_functions}}<br />
<br />
==وظائف الانفجارات==<br />
{{AR/Client_explosion_functions}}<br />
<br />
==وظائف الملف==<br />
{{AR/Client file functions}}<br />
<br />
==وظائف الحريق==<br />
{{AR/Client fire functions}}<br />
<br />
==وظائف واجهة المستخدم الرسومية==<br />
{{AR/GUI_functions}}<br />
<br />
==وظائف مدخلات==<br />
{{AR/Client_input_functions}}<br />
<br />
==وظيفة العلامات==<br />
{{AR/Client_marker_functions}}<br />
<br />
==وظائف لهدف معين==<br />
{{AR/Client_object_functions}}<br />
<br />
==وظائف الإخراج==<br />
{{AR/Client_output_functions}}<br />
<br />
==وظائف الجسم==<br />
{{AR/Client_ped_functions}}<br />
<br />
==وظائف الدعم==<br />
{{AR/Client_pickup_functions}}<br />
<br />
==وظائف الاعب==<br />
{{AR/Client_player_functions}}<br />
<br />
==Projectile functions==<br />
{{AR/Client_projectile_functions}}<br />
<br />
==Radar-area functions==<br />
{{AR/Client_radar-area_functions}}<br />
<br />
==وظائف الموارد==<br />
{{AR/Client_resource_functions}}<br />
<br />
==وظائف فريق==<br />
{{AR/Client_team_functions}}<br />
<br />
==Utility functions==<br />
{{AR/Client_utility_functions}}<br />
<br />
==وظائف السيارة==<br />
{{AR/Client_vehicle_functions}}<br />
<br />
==وظائف المياه==<br />
{{AR/Client_water_functions}}<br />
<br />
==وظائف سلاح==<br />
{{AR/Client_weapon_functions}}<br />
<br />
==Weapon Creation functions==<br />
Documentation can be found [http://code.google.com/p/mtasa-blue/source/detail?r=4555 here] and [http://code.google.com/p/mtasa-blue/source/detail?r=4557 here]<br />
{{AR/Client_weapon_creation_functions}}<br />
<br />
==وظائف العالم==<br />
{{AR/Client_world_functions}}<br />
<br />
==XML functions==<br />
{{AR/Client XML functions}}<br />
<br />
[[ar:Client Scripting Functions]]<br />
[[en:Client Scripting Functions]]<br />
[[pl:Funkcje po stronie klienta]]<br />
[[it:Funzioni Client-side]]<br />
[[ru:Client Scripting Functions]]<br />
[[de:Clientseitige_Funktionen]]<br />
[[tr:Client Taraflı Fonksiyonlar]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/Client_Scripting_Functions&diff=46604AR/Client Scripting Functions2016-02-10T13:09:58Z<p>Jaber: </p>
<hr />
<div><pageclass class="client"></pageclass><br />
{{Adding_Pages_to_Categories_and_Templates}}<br />
This page lists all the '''client-side''' scripting functions that have been implemented and are available as native functions from the Deathmatch mod. To request a function or event, use [[Requested Functions and Events]]<br />
<br />
For more functions, check the [[Useful_Functions|useful functions page]].<br />
__TOC__<br />
<br />
==وظائف الصوت==<br />
{{AR/Audio_functions}}<br />
<br />
==وظائف علامات الخريطة==<br />
{{AR/Blip_functions}}<br />
<br />
==وظائف الكاميرا==<br />
{{AR/Camera_functions}}<br />
<br />
==وظائف الملابس==<br />
{{AR/Client_Clothes and body functions}}<br />
<br />
==Collision shape functions==<br />
{{AR/Collision_shape_functions}}<br />
<br />
==وظائف الأسهم==<br />
{{AR/Client_cursor_functions}}<br />
<br />
== وظائف الرسم==<br />
{{AR/Drawing_functions}}<br />
<br />
==وظائف التأثيرات==<br />
{{AR/Client_Effects_functions}}<br />
<br />
==وظائف العناصر==<br />
{{AR/Client_Element_functions}}<br />
<br />
==وظائف المحرك==<br />
{{AR/Engine_functions}}<br />
<br />
==وظائف الحدث==<br />
{{AR/Client_event_functions}}<br />
<br />
==وظائف الانفجارات==<br />
{{AR/Client_explosion_functions}}<br />
<br />
==وظائف الملف==<br />
{{AR/Client file functions}}<br />
<br />
==وظائف الحريق==<br />
{{AR/Client fire functions}}<br />
<br />
==وظائف واجهة المستخدم الرسومية==<br />
{{AR/GUI_functions}}<br />
<br />
==وظائف مدخلات==<br />
{{AR/Client_input_functions}}<br />
<br />
==وظيفة العلامات==<br />
{{AR/Client_marker_functions}}<br />
<br />
==وظائف لهدف معين==<br />
{{AR/Client_object_functions}}<br />
<br />
==وظائف الإخراج==<br />
{{AR/Client_output_functions}}<br />
<br />
<br />
==وظائف الدعم==<br />
{{AR/Client_pickup_functions}}<br />
<br />
==وظائف الاعب==<br />
{{AR/Client_player_functions}}<br />
<br />
==Projectile functions==<br />
{{AR/Client_projectile_functions}}<br />
<br />
==Radar-area functions==<br />
{{AR/Client_radar-area_functions}}<br />
<br />
==وظائف الموارد==<br />
{{AR/Client_resource_functions}}<br />
<br />
==وظائف فريق==<br />
{{AR/Client_team_functions}}<br />
<br />
==Utility functions==<br />
{{AR/Client_utility_functions}}<br />
<br />
==وظائف السيارة==<br />
{{AR/Client_vehicle_functions}}<br />
<br />
==وظائف المياه==<br />
{{AR/Client_water_functions}}<br />
<br />
==وظائف سلاح==<br />
{{AR/Client_weapon_functions}}<br />
<br />
==Weapon Creation functions==<br />
Documentation can be found [http://code.google.com/p/mtasa-blue/source/detail?r=4555 here] and [http://code.google.com/p/mtasa-blue/source/detail?r=4557 here]<br />
{{AR/Client_weapon_creation_functions}}<br />
<br />
==وظائف العالم==<br />
{{AR/Client_world_functions}}<br />
<br />
==XML functions==<br />
{{AR/Client XML functions}}<br />
<br />
[[ar:Client Scripting Functions]]<br />
[[en:Client Scripting Functions]]<br />
[[pl:Funkcje po stronie klienta]]<br />
[[it:Funzioni Client-side]]<br />
[[ru:Client Scripting Functions]]<br />
[[de:Clientseitige_Funktionen]]<br />
[[tr:Client Taraflı Fonksiyonlar]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/Client_Scripting_Functions&diff=46603AR/Client Scripting Functions2016-02-10T13:09:15Z<p>Jaber: </p>
<hr />
<div><pageclass class="client"></pageclass><br />
{{Adding_Pages_to_Categories_and_Templates}}<br />
This page lists all the '''client-side''' scripting functions that have been implemented and are available as native functions from the Deathmatch mod. To request a function or event, use [[Requested Functions and Events]]<br />
<br />
For more functions, check the [[Useful_Functions|useful functions page]].<br />
__TOC__<br />
<br />
==وظائف الصوت==<br />
{{AR/Audio_functions}}<br />
<br />
==وظائف علامات الخريطة==<br />
{{AR/Blip_functions}}<br />
<br />
==وظائف الكاميرا==<br />
{{AR/Camera_functions}}<br />
<br />
==وظائف الملابس==<br />
{{AR/Client_Clothes and body functions}}<br />
<br />
==Collision shape functions==<br />
{{AR/Collision_shape_functions}}<br />
<br />
==وظائف الأسهم==<br />
{{AR/Client_cursor_functions}}<br />
<br />
== وظائف الرسم==<br />
{{AR/Drawing_functions}}<br />
<br />
==وظائف التأثيرات==<br />
{{AR/Client_Effects_functions}}<br />
<br />
==وظائف العناصر==<br />
{{AR/Client_Element_functions}}<br />
<br />
==وظائف المحرك==<br />
{{AR/Engine_functions}}<br />
<br />
==وظائف الحدث==<br />
{{AR/Client_event_functions}}<br />
<br />
==وظائف الانفجارات==<br />
{{AR/Client_explosion_functions}}<br />
<br />
==وظائف الملف==<br />
{{AR/Client file functions}}<br />
<br />
==وظائف الحريق==<br />
{{AR/Client fire functions}}<br />
<br />
==وظائف واجهة المستخدم الرسومية==<br />
{{AR/GUI_functions}}<br />
<br />
==وظائف مدخلات==<br />
{{AR/Client_input_functions}}<br />
<br />
==وظيفة العلامات==<br />
{{AR/Client_marker_functions}}<br />
<br />
==وظائف لهدف معين==<br />
{{AR/Client_object_functions}}<br />
<br />
==وظائف الإخراج==<br />
{{AR/Client_output_functions}}<br />
<br />
==وظائف الجسم==<br />
<br />
{{AR/Client_ped_functions}}<br />
<br />
==وظائف الدعم==<br />
{{AR/Client_pickup_functions}}<br />
<br />
==وظائف الاعب==<br />
{{AR/Client_player_functions}}<br />
<br />
==Projectile functions==<br />
{{AR/Client_projectile_functions}}<br />
<br />
==Radar-area functions==<br />
{{AR/Client_radar-area_functions}}<br />
<br />
==وظائف الموارد==<br />
{{AR/Client_resource_functions}}<br />
<br />
==وظائف فريق==<br />
{{AR/Client_team_functions}}<br />
<br />
==Utility functions==<br />
{{AR/Client_utility_functions}}<br />
<br />
==وظائف السيارة==<br />
{{AR/Client_vehicle_functions}}<br />
<br />
==وظائف المياه==<br />
{{AR/Client_water_functions}}<br />
<br />
==وظائف سلاح==<br />
{{AR/Client_weapon_functions}}<br />
<br />
==Weapon Creation functions==<br />
Documentation can be found [http://code.google.com/p/mtasa-blue/source/detail?r=4555 here] and [http://code.google.com/p/mtasa-blue/source/detail?r=4557 here]<br />
{{AR/Client_weapon_creation_functions}}<br />
<br />
==وظائف العالم==<br />
{{AR/Client_world_functions}}<br />
<br />
==XML functions==<br />
{{AR/Client XML functions}}<br />
<br />
[[ar:Client Scripting Functions]]<br />
[[en:Client Scripting Functions]]<br />
[[pl:Funkcje po stronie klienta]]<br />
[[it:Funzioni Client-side]]<br />
[[ru:Client Scripting Functions]]<br />
[[de:Clientseitige_Funktionen]]<br />
[[tr:Client Taraflı Fonksiyonlar]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=Template:AR/Client_ped_functions&diff=46602Template:AR/Client ped functions2016-02-10T13:08:31Z<p>Jaber: Blanked the page</p>
<hr />
<div></div>Jaberhttps://wiki.multitheftauto.com/index.php?title=Template:AR/Client_ped_functions&diff=46601Template:AR/Client ped functions2016-02-10T13:08:23Z<p>Jaber: /* Syntax */</p>
<hr />
<div>__NOTOC__ <br />
{{Server client function}}<br />
Creates a Ped in the GTA world.<br />
<br />
==Example== <br />
<br />
<section name="Server" class="server" show="true"><br />
This example creates an ped when the resource starts:<br />
<syntaxhighlight lang="lua"><br />
function pedLoad ( name )<br />
createPed ( 120, 5540.6654, 1020.55122, 1240.545 )<br />
end<br />
addEventHandler ( "onResourceStart", getResourceRootElement(), pedLoad )<br />
</syntaxhighlight><br />
</section><br />
<br />
<section name="Client" class="client" show="true"><br />
This example creates a ped, and makes it damage proof:<br />
<syntaxhighlight lang="lua"><br />
thePed = createPed(120, 5540.6654, 1020.55122, 1240.545) -- Creates a ped<br />
function cancelPedDamage()<br />
cancelEvent() -- Cancels the onClientPedDamage event<br />
end<br />
addEventHandler("onClientPedDamage", thePed, cancelPedDamage) -- When thePed is damaged, cancelPedDamage is called<br />
</syntaxhighlight><br />
</section><br />
<br />
==Issues==<br />
{{Issues|<br />
{{Issue|7970|Peds with weapons malfunction due to weird totalAmmo and ammoInClip values}}<br />
{{Issue|7371|Network troubled players can ruin ped sync}}<br />
{{Issue|6048|Ped weapon isn't synced on join}}<br />
{{Issue|5113|setPedControlState doesn't work on the control "enter_exit"}}<br />
{{Issue|6287|Sync distance of unoccupied vehicles and peds should match stream distance}}<br />
{{Issue|8790|Using setElementHealth on a dead ped makes it invincible}}<br />
{{Issue|5725|Ped fireing Projectiles doesn't work}}<br />
{{Issue|4921|Improve ped synchronization}}<br />
{{Issue|5840|ped position not synced to server after falling through the ground}}<br />
{{Issue|6682|Server doesnt update ped position after warping it to vehicle}}<br />
{{Issue|6506|Ped animation is only visible if it was set while player was in stream distance from source ped}}<br />
{{Issue|4596|Serverside peds have their animations not applied for joining players}}<br />
{{Issue|4504|Peds shooting incorrectly}}<br />
{{Issue|4008|Can't use giveWeapon() directly after createPed()}}<br />
}}<br />
<br />
<br />
==See Also==<br />
{{Ped functions}}<br />
[[ru:createPed]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=Template:AR/Client_ped_functions&diff=46600Template:AR/Client ped functions2016-02-10T13:07:42Z<p>Jaber: createPed</p>
<hr />
<div>__NOTOC__ <br />
{{Server client function}}<br />
Creates a Ped in the GTA world.<br />
<br />
==Syntax==<br />
<section name="Server" class="server" show="true"> <br />
<syntaxhighlight lang="lua">ped createPed ( int modelid, float x, float y, float z [, float rot = 0.0, bool synced = true ] )</syntaxhighlight> <br />
<br />
===Required Arguments=== <br />
*'''modelid:''' A whole integer specifying the [[Character_Skins|GTASA skin ID]].<br />
*'''x:''' A floating point number representing the X coordinate on the map.<br />
*'''y:''' A floating point number representing the Y coordinate on the map.<br />
*'''z:''' A floating point number representing the Z coordinate on the map.<br />
<br />
==Optional Arguments==<br />
{{OptionalArg}}<br />
*'''rot:''' A floating point number representing the rotation in degrees. <br />
*'''synced:''' A boolean value representing whether or not the ped will be synced. Disabling the sync might be useful for frozen or static peds to increase the server performance.<br />
</section><br />
<section name="Client" class="client" show="true"><br />
<syntaxhighlight lang="lua">ped createPed ( int modelid, float x, float y, float z [, float rot = 0.0 ] )</syntaxhighlight> <br />
<br />
===Required Arguments=== <br />
*'''modelid:''' A whole integer specifying the [[Character_Skins|GTASA skin ID]].<br />
*'''x:''' A floating point number representing the X coordinate on the map.<br />
*'''y:''' A floating point number representing the Y coordinate on the map.<br />
*'''z:''' A floating point number representing the Z coordinate on the map.<br />
<br />
==Optional Arguments==<br />
{{OptionalArg}}<br />
*'''rot:''' A floating point number representing the rotation in degrees. <br />
</section><br />
<br />
===Returns===<br />
Returns a ped element if it was successfully created.<br />
<br />
==Example== <br />
<br />
<section name="Server" class="server" show="true"><br />
This example creates an ped when the resource starts:<br />
<syntaxhighlight lang="lua"><br />
function pedLoad ( name )<br />
createPed ( 120, 5540.6654, 1020.55122, 1240.545 )<br />
end<br />
addEventHandler ( "onResourceStart", getResourceRootElement(), pedLoad )<br />
</syntaxhighlight><br />
</section><br />
<br />
<section name="Client" class="client" show="true"><br />
This example creates a ped, and makes it damage proof:<br />
<syntaxhighlight lang="lua"><br />
thePed = createPed(120, 5540.6654, 1020.55122, 1240.545) -- Creates a ped<br />
function cancelPedDamage()<br />
cancelEvent() -- Cancels the onClientPedDamage event<br />
end<br />
addEventHandler("onClientPedDamage", thePed, cancelPedDamage) -- When thePed is damaged, cancelPedDamage is called<br />
</syntaxhighlight><br />
</section><br />
<br />
==Issues==<br />
{{Issues|<br />
{{Issue|7970|Peds with weapons malfunction due to weird totalAmmo and ammoInClip values}}<br />
{{Issue|7371|Network troubled players can ruin ped sync}}<br />
{{Issue|6048|Ped weapon isn't synced on join}}<br />
{{Issue|5113|setPedControlState doesn't work on the control "enter_exit"}}<br />
{{Issue|6287|Sync distance of unoccupied vehicles and peds should match stream distance}}<br />
{{Issue|8790|Using setElementHealth on a dead ped makes it invincible}}<br />
{{Issue|5725|Ped fireing Projectiles doesn't work}}<br />
{{Issue|4921|Improve ped synchronization}}<br />
{{Issue|5840|ped position not synced to server after falling through the ground}}<br />
{{Issue|6682|Server doesnt update ped position after warping it to vehicle}}<br />
{{Issue|6506|Ped animation is only visible if it was set while player was in stream distance from source ped}}<br />
{{Issue|4596|Serverside peds have their animations not applied for joining players}}<br />
{{Issue|4504|Peds shooting incorrectly}}<br />
{{Issue|4008|Can't use giveWeapon() directly after createPed()}}<br />
}}<br />
<br />
<br />
==See Also==<br />
{{Ped functions}}<br />
[[ru:createPed]]</div>Jaberhttps://wiki.multitheftauto.com/index.php?title=AR/Client_Scripting_Functions&diff=46599AR/Client Scripting Functions2016-02-10T13:03:23Z<p>Jaber: </p>
<hr />
<div><pageclass class="client"></pageclass><br />
{{Adding_Pages_to_Categories_and_Templates}}<br />
This page lists all the '''client-side''' scripting functions that have been implemented and are available as native functions from the Deathmatch mod. To request a function or event, use [[Requested Functions and Events]]<br />
<br />
For more functions, check the [[Useful_Functions|useful functions page]].<br />
__TOC__<br />
<br />
==وظائف الصوت==<br />
{{AR/Audio_functions}}<br />
<br />
==وظائف علامات الخريطة==<br />
{{AR/Blip_functions}}<br />
<br />
==وظائف الكاميرا==<br />
{{AR/Camera_functions}}<br />
<br />
==وظائف الملابس==<br />
{{AR/Client_Clothes and body functions}}<br />
<br />
==Collision shape functions==<br />
{{AR/Collision_shape_functions}}<br />
<br />
==وظائف الأسهم==<br />
{{AR/Client_cursor_functions}}<br />
<br />
== وظائف الرسم==<br />
{{AR/Drawing_functions}}<br />
<br />
==وظائف التأثيرات==<br />
{{AR/Client_Effects_functions}}<br />
<br />
==وظائف العناصر==<br />
{{AR/Client_Element_functions}}<br />
<br />
==وظائف المحرك==<br />
{{AR/Engine_functions}}<br />
<br />
==وظائف الحدث==<br />
{{AR/Client_event_functions}}<br />
<br />
==وظائف الانفجارات==<br />
{{AR/Client_explosion_functions}}<br />
<br />
==وظائف الملف==<br />
{{AR/Client file functions}}<br />
<br />
==وظائف الحريق==<br />
{{AR/Client fire functions}}<br />
<br />
==وظائف واجهة المستخدم الرسومية==<br />
{{AR/GUI_functions}}<br />
<br />
==وظائف مدخلات==<br />
{{AR/Client_input_functions}}<br />
<br />
==وظيفة العلامات==<br />
{{AR/Client_marker_functions}}<br />
<br />
==وظائف لهدف معين==<br />
{{AR/Client_object_functions}}<br />
<br />
==وظائف الإخراج==<br />
{{AR/Client_output_functions}}<br />
<br />
==Ped functions==<br />
{{AR/Client_ped_functions}}<br />
<br />
==وظائف الجسم==<br />
{{AR/Client_ped_functions}}<br />
<br />
==وظائف الدعم==<br />
{{AR/Client_pickup_functions}}<br />
<br />
==وظائف الاعب==<br />
{{AR/Client_player_functions}}<br />
<br />
==Projectile functions==<br />
{{AR/Client_projectile_functions}}<br />
<br />
==Radar-area functions==<br />
{{AR/Client_radar-area_functions}}<br />
<br />
==وظائف الموارد==<br />
{{AR/Client_resource_functions}}<br />
<br />
==وظائف فريق==<br />
{{AR/Client_team_functions}}<br />
<br />
==Utility functions==<br />
{{AR/Client_utility_functions}}<br />
<br />
==وظائف السيارة==<br />
{{AR/Client_vehicle_functions}}<br />
<br />
==وظائف المياه==<br />
{{AR/Client_water_functions}}<br />
<br />
==وظائف سلاح==<br />
{{AR/Client_weapon_functions}}<br />
<br />
==Weapon Creation functions==<br />
Documentation can be found [http://code.google.com/p/mtasa-blue/source/detail?r=4555 here] and [http://code.google.com/p/mtasa-blue/source/detail?r=4557 here]<br />
{{AR/Client_weapon_creation_functions}}<br />
<br />
==وظائف العالم==<br />
{{AR/Client_world_functions}}<br />
<br />
==XML functions==<br />
{{AR/Client XML functions}}<br />
<br />
[[ar:Client Scripting Functions]]<br />
[[en:Client Scripting Functions]]<br />
[[pl:Funkcje po stronie klienta]]<br />
[[it:Funzioni Client-side]]<br />
[[ru:Client Scripting Functions]]<br />
[[de:Clientseitige_Funktionen]]<br />
[[tr:Client Taraflı Fonksiyonlar]]</div>Jaber